Farily new to Zabbix. I loved that it was pretty easy to install on multiple versions of Linux.I have zabbix server (4.2.2) & zabbix web installed on an Ubuntu 16.04.5 running on old Dell hardware; it seems to be doing fine and monitoring itself and 11 other servers. This set up has been running great for about 2 weeks.
Today I found the zabbix agent (also 4.2.2) stopped on one of the other servers - it is running CentOS 6.10 on old Dell hardware. On the agent server there was nothing in the log about any error and nothing in the system logs about anything to do with zabbix. Using 'service zabbix_agent restart' failed the stop and then the start was OK. Doing another restart both the stop and start were OK. The monitored system is again reporting correctly with the server.
This is the second or third time this has happened in this first couple weeks with Zabbix. I cannot recall if it was always the same monitored system of even if all of the stopped agents were on CentOS - but I "think" it was different systems and different OS's. Since I cannot find any reason for the agent to be stopped it got me searching online for a reason and I have not been able to find anyone reporting that the zabbix agent just stops like this.
The fix is easy but I really don't want to get woken up at 3am again just to manually restart the agent and besides it is bugging me and makes me think that there is something else wrong.
So, I guess now I am asking for help. Anyone got any ideas on where I should be looking?
Thanks
Today I found the zabbix agent (also 4.2.2) stopped on one of the other servers - it is running CentOS 6.10 on old Dell hardware. On the agent server there was nothing in the log about any error and nothing in the system logs about anything to do with zabbix. Using 'service zabbix_agent restart' failed the stop and then the start was OK. Doing another restart both the stop and start were OK. The monitored system is again reporting correctly with the server.
This is the second or third time this has happened in this first couple weeks with Zabbix. I cannot recall if it was always the same monitored system of even if all of the stopped agents were on CentOS - but I "think" it was different systems and different OS's. Since I cannot find any reason for the agent to be stopped it got me searching online for a reason and I have not been able to find anyone reporting that the zabbix agent just stops like this.
The fix is easy but I really don't want to get woken up at 3am again just to manually restart the agent and besides it is bugging me and makes me think that there is something else wrong.
So, I guess now I am asking for help. Anyone got any ideas on where I should be looking?
Thanks
Comment