Error with Zabbix agent and proxy que
Hello forums.
I am posting here in hopes of finding some insight on a few problems I have, that I haven't been able to tackle.
So I am running Zabbix-server version 7.0.13 on one server and 2x proxies running proxy and agent with same version 7.0.13.
I am having some problems with using active monitoring. I have configured 127.0.0.1 as ServerActive and hostname Zabbix proxy 1 and Zabbix proxy 2 on their respective servers.
In the Zabbix UI I added proxies as active mode and these are both showing as active and sending data. Proxies are also added under Hosts with their respective names Zabbix proxy 1 and 2 and set them for monitoring via proxy again with respective proxies 1 by 1 and 2 by 2. They both have Agent interfaces with 127.0.0.1 IP and default ports running.
For the problem; if my server reboots the connections to the agents is lost and I stop receiving active agent data from Linux and Zabbix proxy health templates. In the logs I get error messages cannot send list of active checks to "127.0.0.1": host [Zabbix proxy 1] not found and same error but Zabbix proxy 2 not found. I need to change the proxy host to be monitored by the server itself and then re-apply proxies to be monitored by themselves for active monitoring to start working again. Has anyone else run into this same issue and maybe have some insight on how to fix this? Or is this possibly some kind of bug I have run into?
Other thing is my server rebooted over the weekend and due to configuration error my proxies lost connectivity to the server for a day or so. After fixing the connections my queue for More than 10minutes is at 7844 and it seems like this number is simply not going down. Does it just take very long time for the que to work on itself or how long should I expect to wait for the que to go back to normal in an environment with "Number of items (enabled/disabled/not supported) 22065 22018 / 16 / 31"
The que is also all in other proxy (proxy 2) and proxy 1 is showing 0 que items. Hosts monitored by proxy 1 are showing all their data correctly, but hosts monitored by proxy 2 are stuck and don't show data.
I am posting here in hopes of finding some insight on a few problems I have, that I haven't been able to tackle.
So I am running Zabbix-server version 7.0.13 on one server and 2x proxies running proxy and agent with same version 7.0.13.
I am having some problems with using active monitoring. I have configured 127.0.0.1 as ServerActive and hostname Zabbix proxy 1 and Zabbix proxy 2 on their respective servers.
In the Zabbix UI I added proxies as active mode and these are both showing as active and sending data. Proxies are also added under Hosts with their respective names Zabbix proxy 1 and 2 and set them for monitoring via proxy again with respective proxies 1 by 1 and 2 by 2. They both have Agent interfaces with 127.0.0.1 IP and default ports running.
For the problem; if my server reboots the connections to the agents is lost and I stop receiving active agent data from Linux and Zabbix proxy health templates. In the logs I get error messages cannot send list of active checks to "127.0.0.1": host [Zabbix proxy 1] not found and same error but Zabbix proxy 2 not found. I need to change the proxy host to be monitored by the server itself and then re-apply proxies to be monitored by themselves for active monitoring to start working again. Has anyone else run into this same issue and maybe have some insight on how to fix this? Or is this possibly some kind of bug I have run into?
Other thing is my server rebooted over the weekend and due to configuration error my proxies lost connectivity to the server for a day or so. After fixing the connections my queue for More than 10minutes is at 7844 and it seems like this number is simply not going down. Does it just take very long time for the que to work on itself or how long should I expect to wait for the que to go back to normal in an environment with "Number of items (enabled/disabled/not supported) 22065 22018 / 16 / 31"
The que is also all in other proxy (proxy 2) and proxy 1 is showing 0 que items. Hosts monitored by proxy 1 are showing all their data correctly, but hosts monitored by proxy 2 are stuck and don't show data.