One particularly frustrating error that administrators face is: If you have landed on this page, you have likely seen this message flooding your Zabbix server logs ( /var/log/zabbix/zabbix_server.log ) or agent logs. The error often appears in clusters, leading to lost metrics, unresponsive items, and general instability.
By systematically increasing cache sizes, tuning process counts, fixing database performance, and ensuring proper OS limits, you can eliminate this error entirely. Remember: Zabbix is a distributed system even on a single server—treat its internal processes with the same respect you give external servers. zabbix cannot write to ipc socket broken pipe upd
Implement these changes, and your Zabbix monitoring will return to a stable, reliable state—without a single broken pipe in sight. Remember: Zabbix is a distributed system even on
Edit /etc/security/limits.conf :
Check your version: zabbix_server -V . If older than 5.0 LTS, plan an upgrade. If the error persists and you are certain configs are correct, manually clear stale IPC resources. If older than 5
Increase values gradually (e.g., double each). Restart Zabbix server: systemctl restart zabbix-server . Solution 2: Adjust Process Timeouts The Timeout parameter controls how long Zabbix waits for internal operations.
[Service] LimitNOFILE=65536 LimitNPROC=65536 Reload: systemctl daemon-reload && systemctl restart 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.