* soft nofile 65535 * hard nofile 65535
If you’ve ever glanced at your Zabbix logs and stumbled upon an error message like “cannot write to IPC socket: Broken pipe,” you’re not alone. While the message might seem cryptic at first, it’s actually pointing to a well‑understood set of issues that can be diagnosed and resolved. This guide explains what the error means, why it occurs, and exactly how you can fix it.
If the history synchronizers or database syncers are overwhelmed, they cannot read from the IPC sockets fast enough. The buffers fill up, and the sockets eventually time out and break. zabbix cannot write to ipc socket broken pipe upd
While not a direct cause, database disconnections can trigger proxy instability. Zabbix Proxy logs sometimes show database is down: reconnecting in 10 seconds before other errors emerge. When the database backend falters, dependent internal processes may crash, resulting in broken IPC pipes.
Drawing from official Zabbix bug reports and real-world case studies, this error rarely occurs in isolation. It is typically part of a cascade of failures. * soft nofile 65535 * hard nofile 65535
Zabbix Server Unstable After Platform Migration/Upgrade to 6.0
If the cache is full, increase the cache size in /etc/zabbix/zabbix_server.conf : If the history synchronizers or database syncers are
: A sudden burst in processes (e.g., during housekeeping) can temporarily overwhelm available resources, leading to unstable socket connections.