Share your experience in the comments below – let’s build a better troubleshooting guide together. Stay tuned for more Zabbix deep dives. Subscribe to the RSS feed for updates.
This error indicates that a Zabbix process (usually the server or proxy) has lost communication with another internal process via an Inter-Process Communication (IPC) socket. In simpler terms: one part of Zabbix tried to talk to another, but the other end closed the connection.
audit2allow -a -M zabbix_ipc semodule -i zabbix_ipc.pp Proxies often log cannot write to IPC socket when the main server is unreachable, and the local proxy processes start failing internally. zabbix cannot write to ipc socket broken pipe
Start with the simplest fix – increase Timeout – and then work your way up to process tuning and filesystem checks.
setenforce 0 # If the error stops, SELinux is the culprit. Share your experience in the comments below –
TmpDirectory=/dev/shm/zabbix Create the directory and set proper permissions (chown zabbix:zabbix). While IPC sockets aren’t network sockets, SELinux policies can still block process communication.
Ensure TmpDirectory points to a local, fast filesystem (e.g., /dev/shm or /var/tmp ). This error indicates that a Zabbix process (usually
If you manage a Zabbix monitoring environment, you’ve likely encountered a moment of panic when services stop reporting. One of the more cryptic and frustrating errors you might see in your logs is:
# Increase global timeout (e.g., to 10 seconds) Timeout=10 Restart Zabbix server/proxy after changes. When Zabbix hits a bottleneck (e.g., 1000s of active checks on a proxy with low RAM), processes start dying unexpectedly.