Pipe Upd ((new)) | Zabbix Cannot Write To Ipc Socket Broken

The Zabbix server or proxy daemon crashed while receiving data.

If you see kernel: Out of memory: Kill process [PID] (zabbix_server) , your preprocessing workers are crashing due to oversized metrics. Step 2: Check Zabbix Internal Process Busy %

Increase your internal cache sizes in your zabbix_server.conf file:

If you still see the “broken pipe” message, it’s time to review your script’s stability under real‑world conditions – concurrency, slow execution, and unexpected inputs are the usual suspects. zabbix cannot write to ipc socket broken pipe upd

This happens specifically for UDP checks (e.g., SNMP traps, custom UDP data collection). TCP items seem unaffected.

Note the exact timestamp of the "broken pipe" error.

If the database cannot keep up with history synchers writing data, the IPC pipes between pollers and synchers will time out. The Zabbix server or proxy daemon crashed while

Increase the history cache size in zabbix_server.conf to buffer more data during DB spikes:

# zabbix_server.conf StartAgents=0 ListenPort=10051

Run the following command to check for kernel-level terminations: This happens specifically for UDP checks (e

Zabbix Server Unstable After Platform Migration/Upgrade to 6.0

crashes, subsequent attempts to communicate with them result in a broken pipe Upgrade Issues: