The error "cannot write to IPC socket: Broken pipe" in Zabbix typically indicates that a Zabbix process (like the server or proxy) tried to communicate with a child service (like the preprocessing service) but found that the receiving end of the socket was already closed. Primary Cause: Too Many Open Files
Zabbix Server Unstable After Platform Migration/Upgrade to 6.0 zabbix cannot write to ipc socket broken pipe upd
Ensure the Zabbix user has the necessary rights to create and write to sockets in its temporary directory (usually /tmp or /var/run/zabbix/). If you recently moved these directories or changed permissions, the IPC communication may fail. The error "cannot write to IPC socket: Broken
Modify the Systemd Service File:The most reliable way to apply this is through the service unit file. Create or edit an override for the Zabbix server: sudo systemctl edit zabbix-server Use code with caution. Copied to clipboard ls -l /proc/ /fd | wc -l; ss -s to inspect socket stats
"cannot write to IPC socket: Broken pipe" typically indicates that a Zabbix process (like a poller or trapper) tried to communicate with an internal service—often the preprocessing service availability manager —that has already closed its end of the connection Primary Causes and Solutions Exhausted File Descriptors ("Too many open files"):