Actions
action #135152
closedZabbix agent is not available
Start date:
2023-07-07
Due date:
% Done:
0%
Estimated time:
Description
Observation¶
Problem started at 11:47:08 on 2023.09.03
Problem name: Zabbix agent is not available (or nodata for 30m)
Host: ariel.suse-dmz.opensuse.org
and another version
Problem started at 11:46:51 on 2023.09.03
Problem name: Zabbix agent is not available (or nodata for 30m)
Host: ariel.dmz-prg2.suse.org (over old-ariel)
and also
Problem started at 10:36:51 on 2023.08.26
Problem name: Zabbix agent is not available (or nodata for 30m)
Host: ariel.dmz-prg2.suse.org (over old-ariel)
sudo journalctl -u zabbix_agentd only reveals logs from August 17 and there's no indication it stopped running.
Acceptance criteria¶
- AC1: It is understand what was causing Zabbix agent unavailable alerts
Suggestions¶
- Confirm what was causing the Zabbix agent to appear unavailable
- Consider moving /var/log/zabbix/zabbix_agentd.log into the journal for better discoverability
Out of scope¶
- Monitor proxy availability
Updated by livdywan 8 months ago
- Copied from action #135029: Many unhandled alert messages while users report problems added
Updated by tinita 8 months ago
jbaier_cz wrote in #note-2:
Logs are present in
/var/log/zabbix/zabbix_agentd.log. We can consider changing that to log into journal (settingLogType=consoleshould do the trick)
ah!
maybe this is related then:
1704:20230826:080711.330 active check data upload to [zabbix-proxy-opensuse:10051] started to fail ([connect] cannot connect to [[zabbix-proxy-opensuse]:10051]: [4] Interrupted system call)
1704:20230826:080739.331 active check configuration update from [zabbix-proxy-opensuse:10051] started to fail (cannot connect to [[zabbix-proxy-opensuse]:10051]: [4] Interrupted system call)
The email was sent 08:36 UTC
Actions