Hello everyone!
I am using Zabbis since last year to monitor computers and a lot of network devices for my customers and it's such a great tool. Recently I wasn't being able to update my server from 4.2 to 4.4 so I decided to move it to a dockerized install, so I can upgrade it more easily in the future, just changing the docker and using a external DB.
I've had to drop a few tables while converting from 4.2 to 4.4 (config_autoreg_tls, item_rtdata, media_type), but they have been recreated and the upgrad went smoothly. I have a container for the server and another for the frontend, the data from the server is being collected, but the frontend sitll says the server is down.
I've also tried to follow some suggestions that I've found to increase several cache parameters, but it didn't made any difference. By the end, I also tried to use dockers from v5 alpha but it also stayed the same.
Is there any other suggestion to achieve a more polished instlal? The data from my hosts are being correctly grabbed, but I don't want keep this error showing up. There's no error on the logs, only this one at the frontend (saying the server is not running).
Here are a few screenshots.
--,
Thank you,
Carlos Marchi
I am using Zabbis since last year to monitor computers and a lot of network devices for my customers and it's such a great tool. Recently I wasn't being able to update my server from 4.2 to 4.4 so I decided to move it to a dockerized install, so I can upgrade it more easily in the future, just changing the docker and using a external DB.
I've had to drop a few tables while converting from 4.2 to 4.4 (config_autoreg_tls, item_rtdata, media_type), but they have been recreated and the upgrad went smoothly. I have a container for the server and another for the frontend, the data from the server is being collected, but the frontend sitll says the server is down.
I've also tried to follow some suggestions that I've found to increase several cache parameters, but it didn't made any difference. By the end, I also tried to use dockers from v5 alpha but it also stayed the same.
Is there any other suggestion to achieve a more polished instlal? The data from my hosts are being correctly grabbed, but I don't want keep this error showing up. There's no error on the logs, only this one at the frontend (saying the server is not running).
Here are a few screenshots.
--,
Thank you,
Carlos Marchi