Edit /etc/security/limits.conf :
Troubleshooting Zabbix Error: "Cannot Write to IPC Socket: Broken Pipe"
If the preprocessing service stops (due to memory leaks or bugs in specific versions like 6.0 or 7.0), other processes trying to send data to it will fail with this error.
If a specific service (e.g., zabbix_preprocessing ) crashes or is killed by the OS (such as by the OOM killer), other processes trying to send it data will receive a "Broken pipe" error.
for internal cache settings. If your "Configuration Cache" or "History Cache" is full, the server may stall. You can view these stats via the Zabbix dashboard (System Information widget). Increase Timeout : Slightly increase the
The error occurs in Zabbix when an internal Zabbix process tries to communicate with another local service component—most frequently the preprocessing service —but finds that the receiving end of the communication channel (the Unix socket) has closed unexpectedly. This issue often causes the Zabbix server daemon to crash, freeze, or become unresponsive shortly after a system restart, platform migration, or major version upgrade. Understanding Inter-Process Communication (IPC) in Zabbix
Examples of log patterns and interpretation
Key causes
If this error appears alongside references to preprocessing manager or workers, a specific item value is likely crashing the worker process. This often happens with poorly formatted JavaScript, massive regular expressions, or huge dependent item payloads.
: Increase the LimitNOFILE setting for the Zabbix service.
Increase the limit for the Zabbix user (e.g., to 4096 or higher) in /etc/security/limits.conf .
The error in Zabbix typically indicates that a Zabbix process (like the server or proxy) attempted to communicate with a internal service (like the preprocessing manager) that had already closed its connection. Core Causes