A Zabbix daemon process (like zabbix_server or zabbix_proxy ) was killed mid-communication, usually by the Linux kernel Out-Of-Memory (OOM) killer.
systemctl start zabbix-server
The system ran out of memory or file descriptors, forcing the socket to close. Troubleshooting Steps 1. Check Service Status zabbix cannot write to ipc socket broken pipe upd
HistoryCacheSize=128M # Scale up based on NVPS (New Values Per Second) HistoryIndexCacheSize=32M Use code with caution. 4. System Resource Limits (OS Level) A Zabbix daemon process (like zabbix_server or zabbix_proxy
When to escalate
This error typically appears during a restart of the Zabbix server/proxy, during a version update, or during sudden spikes in data volume. It indicates a failure in the internal communication line between Zabbix processes. during a version update