Hi All,
Our current Zabbix setup is running the frontend in a different server from the backend (MySQL 5.5), after upgrading Zabbix 1.8.14 to 2.0.3 we are experiencing some serious issues with the new version :
Usually once every 10 days at a ramdom time Zabbix starts sending alerts that all Agents are unreachable for more than 5 minutes which is not true.
The trigger is fired and cleared right away on most of the cases but there are some times the alerts is ON for a couple of minutes. We can also see some degraded performance regarding the rendering of the Zabbix Screen in comparison to the old version...
Setting the notification with 1 minute delay didn't seem to help..
I have attached graphs from the Zabbix server internals which indicates some performance issues during the problem period but I have no clue what the problem is,,
Is anyone having the same experience that could help ?
Regards,
NicolasG.
Our current Zabbix setup is running the frontend in a different server from the backend (MySQL 5.5), after upgrading Zabbix 1.8.14 to 2.0.3 we are experiencing some serious issues with the new version :
Usually once every 10 days at a ramdom time Zabbix starts sending alerts that all Agents are unreachable for more than 5 minutes which is not true.
The trigger is fired and cleared right away on most of the cases but there are some times the alerts is ON for a couple of minutes. We can also see some degraded performance regarding the rendering of the Zabbix Screen in comparison to the old version...
Setting the notification with 1 minute delay didn't seem to help..
I have attached graphs from the Zabbix server internals which indicates some performance issues during the problem period but I have no clue what the problem is,,
Is anyone having the same experience that could help ?
Regards,
NicolasG.
Comment