zabbix_server -R log_level_increase="preprocessing manager" zabbix_server -R log_level_increase="preprocessing worker" Use code with caution.
:In the editor, add the following lines to increase the limit to at least 4096 (or higher for large environments): [Service] LimitNOFILE=4096 Use code with caution. Copied to clipboard Reload and Restart :
Increase values gradually (e.g., double each). Restart Zabbix server: systemctl restart zabbix-server .
If after all these steps the error still appears, check the official Zabbix bug tracker for your specific version and consider enabling debug logging ( DebugLevel=4 temporarily) to capture the exact process IDs involved. zabbix cannot write to ipc socket broken pipe upd
If you are still seeing this error after tuning, please share your current , your CacheSize settings , and the 10 lines of logs preceding the error so we can pinpoint the exact process breakdown. Share public link
The “” part of the error occurs when one side of the communication channel attempts to write data to a socket that has already been closed by the other side. In practice, this usually means that the receiving process (e.g., the preprocessing manager) has died, crashed, or been terminated while the sending process (e.g., a poller) was still trying to send data.
The recommended first step, , will prevent a whole class of IPC‑related crashes. Together with appropriate system tuning and regular updates, you can keep your monitoring infrastructure stable and your logs free from broken pipe messages. Restart Zabbix server: systemctl restart zabbix-server
If processes aren't crashing, they might simply be overwhelmed. Zabbix relies heavily on memory caches. Log into your Zabbix Web Frontend. Navigate to .
If the error appears on a Zabbix proxy:
Troubleshooting Zabbix: "Cannot Write to IPC Socket: Broken Pipe" (UDP) Share public link The “” part of the
Increase your internal cache sizes in your zabbix_server.conf file:
During Zabbix 6.0+ Native HA transitions, the active/standby nodes might trigger this error while the system attempts to re-elect a new master, specifically if the history syncer isn't updating correctly.
If your database cannot keep up, history syncers will lock up the IPC sockets.
There are several reasons why the "cannot write to IPC socket: Broken pipe" error may occur in Zabbix when using UDP: