Save the file, then reload systemd and restart the service to apply the change:
IPC sockets need disk space and inodes.
Zabbix is only as fast as its backend database (MySQL, PostgreSQL, or Oracle). If your database undergoes table locks, slow queries, or runs out of connections, the History Syncer process will stall. When the History Syncer stalls, the IPC queues fill up, leading to crashes and broken pipes. 4. UDP/IPC Timeout Issues zabbix cannot write to ipc socket broken pipe upd
If after all these steps the error still appears, check the official Zabbix bug tracker for your specific version and consider enabling debug logging ( DebugLevel=4 temporarily) to capture the exact process IDs involved. Save the file, then reload systemd and restart
A: The error can occur on both Zabbix Server and Zabbix Proxy. When it appears on a proxy, it usually indicates that the proxy's internal processes are failing, often due to file descriptor limits or database connectivity issues. When the History Syncer stalls, the IPC queues
Investigate the specific service mentioned in the logs immediately following the broken pipe message (e.g., "cannot connect to preprocessing service"). cannot write to IPC socket: Broken pipe - ZABBIX Forums
If this error appeared immediately after a yum update , apt upgrade , or manual binary replacement: