Zabbix Server Unstable After Platform Migration/Upgrade to 6.0
When Zabbix cannot process incoming data fast enough, the history cache fills up. The history syncer process may fail or become overwhelmed, closing the IPC pipe.
: Often seen during high load or network instability; ensure the Zabbix database is not locking up, causing a backlog. 3. Kernel Parameter Tuning zabbix cannot write to ipc socket broken pipe upd
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
Check your zabbix_server.log for earlier messages like cannot connect to preprocessing service or Connection refused . Zabbix Server Unstable After Platform Migration/Upgrade to 6
ps aux | grep zabbix_server
Older Zabbix versions (3.x, 4.x) had known bugs in IPC handling under load, especially with the upd (update) process. Zabbix 6.2+ and 7.0+ have substantially improved IPC resilience. If you share with third parties, their policies apply
Zabbix provides runtime control commands that can help diagnose issues without full restarts:
If the underlying server suffers from CPU throttling, disk I/O bottlenecks, or RAM exhaustion, the Zabbix manager processes may fail to process incoming IPC queues fast enough. Sockets time out and close automatically. 3. Kernel and OS Limitations ( sysctl Bottlenecks)