Zabbix processes rely heavily on pre-allocated shared memory segments ( CacheSize , HistoryCacheSize , HistoryIndexCacheSize ) to store configuration and metrics data before database ingestion. cannot write to IPC socket: Broken pipe - ZABBIX Forums
If the process receiving the data (e.g., the Zabbix History Syncer or Zabbix Proxy Poller) experiences a segmentation fault (segfault) and crashes, the sending process will instantly get a broken pipe error when it attempts to write data to the socket they were sharing. 2. Resource Exhaustion zabbix cannot write to ipc socket broken pipe upd
Examples of log patterns and interpretation Zabbix processes rely heavily on pre-allocated shared memory
: Run tail -n 100 /var/log/zabbix/zabbix_server.log to check for "connection refused" or "cannot connect to preprocessing service" errors. zabbix cannot write to ipc socket broken pipe upd
Then: