, add these lines to /etc/security/limits.conf :
Zabbix administrators often encounter the "cannot write to IPC socket: Broken pipe" error, usually appearing in log files or as an "Update Failed" alert in the web frontend. This error indicates a communication failure between Zabbix processes (like the server, proxy, or agent) or between the PHP frontend and the Zabbix server daemon.
After making changes, verify that the limits have taken effect:
The error is a clear symptom of internal communication failure under load. It is not a bug in your items or templates but a reflection of resource exhaustion, misconfiguration, or backpressure. zabbix cannot write to ipc socket broken pipe upd
Inter-Process Communication (IPC) sockets are a high-speed data exchange mechanism used by Zabbix components to communicate on the same machine. For example, a discovery worker process uses an IPC socket to send data to the history syncer process. A "Broken pipe" error occurs when a write operation is attempted on a socket whose connection has already been closed by the receiving process, making it a symptom of larger instability.
Troubleshooting Zabbix: "Cannot Write to IPC Socket: Broken Pipe" (UDP)
In zabbix_server.conf (or zabbix_proxy.conf ): , add these lines to /etc/security/limits
When the backend database backend (MySQL/PostgreSQL) stalls, Zabbix history syncers cannot flush data fast enough. The internal queues fill up, causing timeouts. Processes waiting on data drop their connections, leaving other workers stranded with a broken pipe. 3. Insufficient Cache Sizes
If your logs also show "Too many open files," you must increase the limit for the Zabbix user Check current limits: su - zabbix -c 'ulimit -n' Increase the limit in /etc/security/limits.conf zabbix soft nofile 10000 zabbix hard nofile 10000 Use code with caution. Copied to clipboard
The of your environment (New Values Per Second / NVPS) It is not a bug in your items
PID in your logs. If you see it restarting frequently, it may be crashing due to a specific malformed item or excessive load Increase the for the specific service to get more detail: zabbix_server -R log_level_increase="preprocessing manager" 4. Verification & Clean Restart
Open your main server configuration file, usually located at /etc/zabbix/zabbix_server.conf , and locate the cache parameters. Scale them up depending on your hardware limits:
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.
The "cannot write to IPC socket: broken pipe" error in Zabbix is essentially a symptom of a process unable to hand off its workload to the next step in the monitoring pipeline. It often points to a chain reaction: To effectively resolve this:
If running Zabbix as a systemd service, you may also need to add LimitNOFILE=4096 to your service unit file (e.g., zabbix-server.service ) to ensure the limit is applied at startup.