Proxy with date 1970-01-01 and Zabbix Server 5.0.31 goes down.
Hello.
I use Zabbix from 3.2 version.
A few days ago I upgraded my zabbix server version from 5.0.19 to 5.0.31. Since then a strange thing has happened to me that has never happened before.
I have some active mode proxies installed on raspberry, which mount different 5 versions, mainly 5.0.19 but also earlier ones (always 5 anyway).
If one of these proxies is restarted, it will lose the date (there is no backup battery on the raspberries) which will be 1970-01-01, as soon as it starts transmitting data to the zabbix server it goes to 100% CPU, MySQL goes from a few hundred of queries per second to over 10K (saturating the CPU).
In the meantime the proxy will acquire the correct date with ntpclient, but now the damage is done: the server is blocked and unresponsive. In this situation I have to brutally shut down the Zabbix server VM (the service doesn't go down, not in a short time anyway).
This thing has never happened in several years of use it only happened after the update to 5.0.31.
I haven't updated all proxies to 5.0.31 yet (I can try) and I might even start the proxy service late, after the date syncs.
Do you have any advice/suggestions? Does it only happen to me? Are there any best practices for this?
I use Zabbix from 3.2 version.
A few days ago I upgraded my zabbix server version from 5.0.19 to 5.0.31. Since then a strange thing has happened to me that has never happened before.
I have some active mode proxies installed on raspberry, which mount different 5 versions, mainly 5.0.19 but also earlier ones (always 5 anyway).
If one of these proxies is restarted, it will lose the date (there is no backup battery on the raspberries) which will be 1970-01-01, as soon as it starts transmitting data to the zabbix server it goes to 100% CPU, MySQL goes from a few hundred of queries per second to over 10K (saturating the CPU).
In the meantime the proxy will acquire the correct date with ntpclient, but now the damage is done: the server is blocked and unresponsive. In this situation I have to brutally shut down the Zabbix server VM (the service doesn't go down, not in a short time anyway).
This thing has never happened in several years of use it only happened after the update to 5.0.31.
I haven't updated all proxies to 5.0.31 yet (I can try) and I might even start the proxy service late, after the date syncs.
Do you have any advice/suggestions? Does it only happen to me? Are there any best practices for this?
Comment