If these common issues are ruled out, a deeper investigation into your specific Zabbix version, workload patterns, and HA configuration will be required. As always, detailed logs are your best friend—the Zabbix support team repeatedly emphasizes that "Without log file it is impossible to investigate reasons of the issue".
Verify the limit has changed for the running process: cat /proc/$(pidof zabbix_server)/limits | grep open . Other Potential Issues
A: This is only recommended as a temporary diagnostic measure or emergency workaround. Running a single preprocessor will severely limit the throughput of items requiring preprocessing and can create significant data processing backlogs. zabbix cannot write to ipc socket broken pipe upd
IPC sockets utilize system memory buffers. If your Zabbix server is processing a massive influx of data (e.g., a network storm or mass agent autodiscovery), the IPC buffer may fill up.
The Zabbix error "cannot write to IPC socket: Broken pipe" typically indicates that a communication channel between internal Zabbix processes (like the server and its preprocessing manager) has been severed. This often occurs when the receiving end of a socket closes unexpectedly while another process is still trying to send data, frequently due to high system load or configuration limits. Common Causes of Broken Pipe Errors If these common issues are ruled out, a
You mentioned this occurring during an "upd" (update). This is the most common cause and is often a timing issue rather than a critical failure.
If you find segmentation faults, it is highly recommended to upgrade your Zabbix Server/Proxy to the latest patch version, as segfaults are usually bugs that the Zabbix team has identified and patched. If the issue persists, collect a core dump and reach out to the Zabbix Support team. Step 2: Review Cache and Queue Metrics Other Potential Issues A: This is only recommended
If you manage Zabbix via systemd, you must also apply this change inside the service override file. Run sudo systemctl edit zabbix-server and add: [Service] LimitNOFILE=65535 Use code with caution.
: Execute the actual data processing tasks assigned by the manager.
Edit your zabbix_proxy.conf and zabbix_server.conf to increase the timeout: Timeout=10 Use code with caution.