Mismatched timeouts are the #1 reason for broken pipes on active checks.
When to escalate
This is the most common reason the internal socket "breaks." When Zabbix hits its operating system limit for open files, it can no longer maintain IPC (Inter-Process Communication) channels. Increase the for the Zabbix user. Check current limits with cat /proc/ /limits | grep open and adjust them in /etc/security/limits.conf (e.g., set to 4096 or higher). Service Crashes or Timeout: If a core service like the preprocessing service zabbix cannot write to ipc socket broken pipe upd
Access Zabbix frontend → → Queue . If you see thousands of items waiting for more than a few seconds, your server is overloaded. Mismatched timeouts are the #1 reason for broken
crashes or is killed due to high load, any other process trying to send data to it will receive a "Broken pipe" error. zabbix_server.log Check current limits with cat /proc/ /limits |