Navigate to your Zabbix Frontend: (or use the Template App Zabbix Server/Proxy internal metrics). Look for:
What (MySQL, PostgreSQL, etc.) are you using?
If the preprocessing service stops (due to memory leaks or bugs in specific versions like 6.0 or 7.0), other processes trying to send data to it will fail with this error. zabbix cannot write to ipc socket broken pipe upd
If the underlying server suffers from CPU throttling, disk I/O bottlenecks, or RAM exhaustion, the Zabbix manager processes may fail to process incoming IPC queues fast enough. Sockets time out and close automatically. 3. Kernel and OS Limitations ( sysctl Bottlenecks)
When Zabbix processes heavy scripts, complex regular expressions, or large volumes of JSON/dependent items, the preprocessing workers can experience severe bottlenecks. Navigate to your Zabbix Frontend: (or use the
The most common cause of an IPC broken pipe is the Zabbix server running out of allowed file descriptors. In Linux, every network connection, open log file, database connection, and internal IPC socket counts as an open file descriptor.
zabbix_get -s 127.0.0.1 -k your.custom.key If the underlying server suffers from CPU throttling,
[Service] LimitNOFILE=65536 LimitNPROC=65536
A Zabbix daemon process (like zabbix_server or zabbix_proxy ) was killed mid-communication, usually by the Linux kernel Out-Of-Memory (OOM) killer.