After making changes, perform a clean restart of the Zabbix server. In some cases, orphaned processes can hold onto sockets even after the main service is stopped systemctl stop zabbix-server Verify no zabbix processes remain: ps aux | grep zabbix systemctl start zabbix-server Key Log Indicators Log Message Likely Root Cause cannot write to IPC socket: Broken pipe Peer service closed the connection unexpectedly [24] Too many open files for the Zabbix user is too low cannot send data to preprocessing service Preprocessing manager has crashed or is overwhelmed Connection refused [111] The target service is not running at all Are you seeing these errors on a Zabbix Server
Using encrypted TLS connections with misconfigured certificates or network-side NAT/load balancers can lead to unexpected connection closures that manifest as broken pipes. zabbix cannot write to ipc socket broken pipe upd
Reload: systemctl daemon-reload && systemctl restart zabbix-server . After making changes, perform a clean restart of
Lack of permissions for the Zabbix user to write to its own PID or log files can disrupt process communication. Lack of permissions for the Zabbix user to
| Symptom | Likely fix | |---------|-------------| | Error after Zabbix restart | Remove stale IPC sockets | | Error on high load | Increase StartTrappers , StartPollers , check LimitNOFILE | | Error on specific host | Increase Timeout on that agent | | Error only with active checks | Match server/agent Timeout , check network stability | | Error + disk full | Clean /tmp or /var/run |
Are you using a , or is this a direct server setup?