Short-term mitigations

with the actual Zabbix Server process ID) to see the current effective limit. Monitor Resources Zabbix documentation on Internal Checks to monitor "busy" percentages for various processes (e.g., zabbix[process,preprocessing manager,avg,busy] Are you seeing this error specifically after an upgrade heavy monitoring load cannot write to IPC socket: Broken pipe - ZABBIX Forums 24 Jan 2023 —

Often, the broken pipe error follows more specific errors like:

Increase the value in your configuration to handle higher loads.

Ensure the database schema was fully updated and that all Zabbix components (server, agents, proxies) are compatible.

grep -i "broken pipe" /var/log/zabbix/zabbix_agentd.log

The Zabbix error message cannot write to ipc socket: broken pipe indicates a critical breakdown in internal communication. It means one Zabbix process tried to send data to another Zabbix process, but the receiving end unexpectedly closed the connection. This guide breaks down why this happens and how to resolve it. Understanding IPC and the "Broken Pipe"