Zabbix uses shared memory for its configuration, history, and trend caches. If these fill up, processes may become unresponsive. Increase CacheSize in your configuration file.
Temporarily set SELinux to permissive mode to test if the error disappears. If it does, you will need to create a custom policy module. 🛠️ Key Takeaway
The Zabbix server or proxy daemon crashed while receiving data. zabbix cannot write to ipc socket broken pipe upd
Look for "Out of memory," "Connection refused," or "Slow query" messages immediately preceding the IPC error. 3. Review Database Performance
Security modules can sometimes block Zabbix processes from writing to sockets in /tmp or /var/run/zabbix . Zabbix uses shared memory for its configuration, history,
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
What is the of your environment (New Values Per Second)? Temporarily set SELinux to permissive mode to test
The communication took too long, and the system or Zabbix killed the connection.