Before jumping into configuration changes, you need to identify why the socket communication is failing. Broken pipe errors are rarely the fault of the socket itself; rather, they are a symptom of a bottleneck or crash elsewhere in the system. 1. Process Crashes (Segfaults)
Zabbix Server Unstable After Platform Migration/Upgrade to 6.0 zabbix cannot write to ipc socket broken pipe upd
If a process takes too long to respond to an IPC request, the master process may drop the connection, causing a broken pipe for the worker. Before jumping into configuration changes, you need to
If the error persists and you are certain configs are correct, manually clear stale IPC resources. Before jumping into configuration changes
HistoryCacheSize=128M # Scale up based on NVPS (New Values Per Second) HistoryIndexCacheSize=32M Use code with caution. 4. System Resource Limits (OS Level)
Does this happen during a (like saving a template)?
Increase the number of preprocessing workers in zabbix_server.conf :