Zabbix agent repeatedly unreachable for 1 minute
Hello everyone!
I'm having issues with one of my Zabbix agents on an Ubuntu host. The server has a proxy and an agent installed and I get the following messages every minute:
The trigger is the default one from the Linux OS Template and is constantly active albeit the host being available and the agent process is running. There's nothing in the agent, proxy or server logs that is relevant.
Also note that 3 more agents are in this state sometimes and one of those is connected to a different proxy. I've tried the following methods to no success:
- Increase the number of forked agents (agent)
- Increase the number of pollers (server, proxy)
- Rewrite IP/DNS (agent)
- Increase timeout (server, agent, proxy)
- Try accessing the agent through a dedicated proxy server
- Reinstalling the agent, proxy and the whole server
- Increase update interval of the agent.ping item
- Changing the default trigger from {Template OS Linux:agent.ping.nodata(1m)}=1 to {Template OS Linux:agent.ping.nodata(60)}=1
- Various other simple tweaks that didn't work
All Zabbix versions are 3.2.3.
Agent config:
Proxy config:
(Note: values in [] are real values in the original config ofc 
)
Does anyone have any idea why this agent is spamming the email inbox so hard? Could this be a Zabbix bug or is there something wrong/missing in the configs that I'm not aware of?
I'm having issues with one of my Zabbix agents on an Ubuntu host. The server has a proxy and an agent installed and I get the following messages every minute:
Code:
Trigger: Zabbix agent on [hostname] is unreachable for 1 minutes Trigger status: OK Trigger severity: Average Trigger URL: Item values: 1. Agent ping ([hostname]:agent.ping): Up (1) 2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN* 3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
Also note that 3 more agents are in this state sometimes and one of those is connected to a different proxy. I've tried the following methods to no success:
- Increase the number of forked agents (agent)
- Increase the number of pollers (server, proxy)
- Rewrite IP/DNS (agent)
- Increase timeout (server, agent, proxy)
- Try accessing the agent through a dedicated proxy server
- Reinstalling the agent, proxy and the whole server
- Increase update interval of the agent.ping item
- Changing the default trigger from {Template OS Linux:agent.ping.nodata(1m)}=1 to {Template OS Linux:agent.ping.nodata(60)}=1
- Various other simple tweaks that didn't work
All Zabbix versions are 3.2.3.
Agent config:
Code:
PidFile=/var/run/zabbix/zabbix_agentd.pid LogType=file LogFile=/var/log/zabbix/zabbix_agentd.log LogFileSize=10 DebugLevel=3 EnableRemoteCommands=1 LogRemoteCommands=1 Server=control1 ListenPort=10050 ListenIP=[ip] ServerActive=control1 Hostname=[hostname] RefreshActiveChecks=120 BufferSend=5 BufferSize=100 MaxLinesPerSecond=20 Timeout=3 AllowRoot=0 Include=/etc/zabbix/zabbix_agentd.d/
Code:
ProxyMode=0 Server=[dns of the zabbix server] Hostname=proxy-al ListenPort=10051 LogFile=/var/log/zabbix/zabbix_proxy.log LogFileSize=0 DebugLevel=3 PidFile=/var/run/zabbix/zabbix_proxy.pid DBName=zabbix_proxy DBUser=zabbix DBPassword=[password] StartPollers=5 Timeout=10 ExternalScripts=/usr/lib/zabbix/externalscripts FpingLocation=/usr/bin/fping Fping6Location=/usr/bin/fping6 LogSlowQueries=3000
)Does anyone have any idea why this agent is spamming the email inbox so hard? Could this be a Zabbix bug or is there something wrong/missing in the configs that I'm not aware of?
Comment