Zabbix Server Unstable After Platform Migration/Upgrade to 6.0
If connections are failing, check database credentials in /etc/zabbix/zabbix_proxy.conf and ensure the database service is running.
A single "Broken pipe" message is insufficient for diagnosis. Look at surrounding log entries for additional context: zabbix cannot write to ipc socket broken pipe upd
Look for preceding warnings like slow query , connection to database lost , or resuming Zabbix server processes .
If the process receiving the data (e.g., the Zabbix History Syncer or Zabbix Proxy Poller) experiences a segmentation fault (segfault) and crashes, the sending process will instantly get a broken pipe error when it attempts to write data to the socket they were sharing. 2. Resource Exhaustion Zabbix Server Unstable After Platform Migration/Upgrade to 6
If the error persists and you are certain configs are correct, manually clear stale IPC resources.
Short-term mitigations
The error in Zabbix typically occurs when the Zabbix server or proxy process hits the operating system's limit for open file descriptors . This prevents internal processes (like the preprocessing worker) from communicating, causing the "Broken pipe" signal when one end of the communication channel closes unexpectedly. Step 1: Increase File Descriptor Limits
crashes, subsequent attempts to communicate with them result in a broken pipe Upgrade Issues: If the process receiving the data (e
Caution: Do not set this number astronomically high, as it can consume all available system memory and CPU, thereby making the problem worse. Monitor your system load average after making adjustments. Step 5: Network and Timeout Considerations
In the [Service] section, add:
