The "Broken Pipe" error is rarely a bug in the code; it is almost always a symptom of a or a timeout . Focus your efforts on the health of the zabbix-server process and its ability to talk to the database. If you'd like to dive deeper, let me know:

Does this happen during a (like saving a template)?

Temporarily set SELinux to permissive mode to test if the error disappears. If it does, you will need to create a custom policy module. 🛠️ Key Takeaway

If you see this error when performing bulk updates or linking large templates, increase the communication timeout in both zabbix_server.conf and zabbix_php.ini . Set Timeout=30 (maximum).

Are you using a , or is this a direct server setup?

If the Zabbix database is locked or slow, the server process might hang. When the frontend waits too long for the server to process a request, the socket connection times out and "breaks." Check for long-running SQL queries. Ensure the database has enough connections available. Common Fixes Increase Timeout Settings

Ensure max_execution_time is sufficient. Adjust Shared Memory

Check your web server error logs (e.g., /var/log/apache2/error.log or /var/log/nginx/error.log )