If your logs also show "Too many open files," you must increase the limit for the Zabbix user Check current limits: su - zabbix -c 'ulimit -n' Increase the limit in /etc/security/limits.conf zabbix soft nofile 10000 zabbix hard nofile 10000 Use code with caution. Copied to clipboard
The operating system might be cutting off connections due to strict security profiles or resource exhaustion. zabbix cannot write to ipc socket broken pipe upd
The broken pipe often results from the or Configuration Syncer failing due to cache exhaustion. If your logs also show "Too many open
Use the built-in "Zabbix server" health dashboard or use zabbix_server -R config_cache_reload to see how the system reacts. Look closely at: Data gathering process busy percentage. History syncer process busy percentage. How to Fix the Error 1. Adjust Zabbix Server Configuration Use the built-in "Zabbix server" health dashboard or
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.
Reload: systemctl daemon-reload && systemctl restart zabbix-server .
Increase your internal cache sizes in your zabbix_server.conf file: