# Increase global timeout (e.g., to 10 seconds) Timeout=10 Restart Zabbix server/proxy after changes. When Zabbix hits a bottleneck (e.g., 1000s of active checks on a proxy with low RAM), processes start dying unexpectedly.
audit2allow -a -M zabbix_ipc semodule -i zabbix_ipc.pp Proxies often log cannot write to IPC socket when the main server is unreachable, and the local proxy processes start failing internally. zabbix cannot write to ipc socket broken pipe
Ensure TmpDirectory points to a local, fast filesystem (e.g., /dev/shm or /var/tmp ). # Increase global timeout (e
Start with the simplest fix – increase Timeout – and then work your way up to process tuning and filesystem checks. Ensure TmpDirectory points to a local, fast filesystem (e
If you manage a Zabbix monitoring environment, you’ve likely encountered a moment of panic when services stop reporting. One of the more cryptic and frustrating errors you might see in your logs is:
setenforce 0 # If the error stops, SELinux is the culprit.