temporarily) in your config to see exactly which process ID is failing. Look for "connection lost" or "slow query" messages immediately preceding the broken pipe. CLI commands to check your current cache usage and system limits?
Look for processes in a zombie state ( Z ) or many processes in D (uninterruptible sleep). Count your pollers, trappers, and syncers. Ensure the numbers match zabbix_server.conf . zabbix cannot write to ipc socket broken pipe upd
✔ HistoryCacheSize ≥ 64M ✔ StartHistorySyncers ≥ 5 ✔ Timeout ≥ 15 seconds ✔ Database not saturated ✔ No stale IPC objects ✔ Zabbix version ≥ 5.0 LTS temporarily) in your config to see exactly which
The Inter-Process Communication (IPC) socket is a critical component of Zabbix's internal architecture. Zabbix uses IPC sockets as a high-speed communication mechanism between its various internal processes—for example, between the discovery manager, history syncers, preprocessors, and other services. When a process attempts to write data to an IPC socket and the connection on the other end is unexpectedly terminated, the "Broken pipe" error is triggered. Look for processes in a zombie state (
Add or modify the [Service] section:
dmesg -T | grep -i oom or grep -i kill /var/log/messages