Stray processes from the old binary version often hold onto IPC sockets, causing "Broken pipe" errors for the new binary.
sudo setenforce 0
I’m encountering an intermittent error in my Zabbix setup when monitoring certain : zabbix cannot write to ipc socket broken pipe upd
: This is the most frequent cause. Zabbix processes may hit the maximum number of open files allowed by the OS. : Increase the for the Zabbix user. You can do this by adding LimitNOFILE=10000 (or higher) to your Zabbix systemd unit file or modifying /etc/security/limits.conf Preprocessing Service Failure Stray processes from the old binary version often
Example (on Ubuntu-based systems):
), but that service had already closed the connection or crashed Common Causes System File Limits (ulimit): zabbix cannot write to ipc socket broken pipe upd