It is the computing equivalent of talking into a phone after the person on the other end has already hung up.
If SELinux is preventing Zabbix from accessing the IPC socket directory, you can create a custom policy or set the correct context. A quick test is to temporarily put SELinux into permissive mode:
signal, as some processes try to sync data while others have already exited. zabbix cannot write to ipc socket broken pipe upd
If the value is low (e.g., 1024), increase it by modifying the systemd service override. Create or edit the override configuration file: sudo systemctl edit zabbix-server Use code with caution. Add the following lines to raise the hard and soft limits: [Service] LimitNOFILE=500000 Use code with caution.
What (MySQL, PostgreSQL, etc.) are you using? It is the computing equivalent of talking into
Note the exact timestamp of the "broken pipe" error.
Timeout=30 # must be >= agent Timeout
If connections are failing, check database credentials in /etc/zabbix/zabbix_proxy.conf and ensure the database service is running.
, add the following to your Zabbix server service file (usually /lib/systemd/system/zabbix-server.service [Service] LimitNOFILE=10000 Use code with caution. Copied to clipboard 2. Monitor and Expand History Cache If the IPC error is linked to the preprocessing service , it may be due to a full history cache Check logs: Look for "History cache is full" Increase the HistoryCacheSize zabbix_server.conf file (e.g., from or higher). 3. Check for Service Crashes Look for the preprocessing manager If the value is low (e
: Coordinates data parsing, regex matching, and custom JavaScript validation before writing to the database.
On server: