This is the most common cause. When the Zabbix server or proxy exceeds the allowed number of open file descriptors, it cannot maintain internal IPC (Inter-Process Communication) connections.
The "broken pipe" error on a Zabbix IPC (Inter-Process Communication) socket typically indicates a communication breakdown between the Zabbix server/proxy and its child processes. This usually happens when a process tries to write to a socket that the receiving end has already closed. Common Root Causes Resource Exhaustion zabbix cannot write to ipc socket broken pipe upd
sudo sed -i 's/Server=127.0.0.1/Server=your_zabbix_server_ip/g' /etc/zabbix/zabbix_agentd.conf This is the most common cause
#!/usr/bin/env python3 import requests # may not be installed print(requests.get('http://localhost/metric').text) zabbix cannot write to ipc socket broken pipe upd