Are you using a , or is this a direct server setup?
The "Broken Pipe" error is rarely a bug in the code; it is almost always a symptom of a or a timeout . Focus your efforts on the health of the zabbix-server process and its ability to talk to the database. If you'd like to dive deeper, let me know: zabbix cannot write to ipc socket broken pipe upd
Confirm the Zabbix Server or Proxy is actually running. A "Broken Pipe" often happens right after a service failure. Run: systemctl status zabbix-server Look for "Active: active (running)" 2. Inspect the Log Files The logs provide the "why" behind the broken pipe. /var/log/zabbix/zabbix_server.log Proxy: /var/log/zabbix/zabbix_proxy.log Are you using a , or is this a direct server setup
Check your web server error logs (e.g., /var/log/apache2/error.log or /var/log/nginx/error.log ) If you'd like to dive deeper, let me
The communication took too long, and the system or Zabbix killed the connection.
Example: CacheSize=256M (or higher depending on your host count). Check SELinux or AppArmor
Does this happen during a (like saving a template)?