| Symptom | Likely fix | |---------|-------------| | Error after Zabbix restart | Remove stale IPC sockets | | Error on high load | Increase StartTrappers , StartPollers , check LimitNOFILE | | Error on specific host | Increase Timeout on that agent | | Error only with active checks | Match server/agent Timeout , check network stability | | Error + disk full | Clean /tmp or /var/run |
Zabbix Server Unstable After Platform Migration/Upgrade to 6.0 zabbix cannot write to ipc socket broken pipe upd
Restart both after change.
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. | Symptom | Likely fix | |---------|-------------| |
If the error stops, you need to adjust the policy. The proper long‑term fix is to ensure that the directory specified in SocketDir has the correct SELinux context. Usually, the default paths ( /run/zabbix ) already have the right context. You can also use audit2allow to generate a policy from the audit log. If you share with third parties, their policies apply
This article dives deep into the causes of this issue and provides step-by-step troubleshooting steps. What is an IPC Socket "Broken Pipe" Error?
Does this happen during a (like saving a template)?