Ensure the Zabbix user has permission to open enough simultaneous files and sockets. Create a systemd override for the service: sudo systemctl edit zabbix-server Use code with caution.
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
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
These processes don't work in isolation; they communicate with one another and with the central Zabbix server/proxy daemon using .
The system ran out of shared memory allocated for Zabbix caches, causing internal processes to terminate. zabbix cannot write to ipc socket broken pipe upd
tail -n 500 /var/log/zabbix/zabbix_server.log | grep -B 5 -A 5 "broken pipe"
The occurs when a Zabbix process attempts to communicate with another local Zabbix process via an Inter-Process Communication (IPC) socket, but the receiving process has abruptly closed the connection.
If you are seeing this error in your zabbix_server.log following an environment change, platform migration, or major upgrade, use this exhaustive guide to diagnose and resolve the issue. Root Causes of the IPC Broken Pipe Error
If the process receiving the data (e.g., the Zabbix History Syncer or Zabbix Proxy Poller) experiences a segmentation fault (segfault) and crashes, the sending process will instantly get a broken pipe error when it attempts to write data to the socket they were sharing. 2. Resource Exhaustion Ensure the Zabbix user has permission to open
Implement these changes, and your Zabbix monitoring will return to a stable, reliable state—without a single broken pipe in sight.
In the context of Zabbix, this almost always points to a or a zombie process rather than a code bug. Common Causes 1. Excessive Poller Usage
VMwareCacheSize=64M # Increase if monitoring VMware environments CacheSize=512M # Increase configuration cache size HistoryCacheSize=128M # Increase history cache size HistoryIndexCacheSize=32M TrendCacheSize=64M ValueCacheSize=128M # Crucial for trigger evaluation stability Use code with caution.
Adjust zabbix_server.conf to ensure enough pollers are available immediately: This link or copies made by others cannot be deleted
IPC sockets utilize system memory buffers. If your Zabbix server is processing a massive influx of data (e.g., a network storm or mass agent autodiscovery), the IPC buffer may fill up.
If the server is crashing repeatedly, set StartPreprocessors=1 . This is not ideal for production performance but can help stabilize the system while you investigate other issues.
Ensure your database configuration ( max_connections ) is significantly higher than the total number of start pollers configured in Zabbix. 5. Check IPC Kernel Limits
Save the file and run systemctl daemon-reload && systemctl restart zabbix-server . 3. Resolve Database Sluggishness