I've replaced my mainboard in my debian11 server, and thought it would be a nice idea to also upgrade zabbix-server 5.4.9 to 6.0.0.
Upgrade worked fine (check the logfile, it upgraded my psql database without problems).
All local checks, and simple ICMP ping checks work fine.
But ALL network related hosts are "unreachable".
e.g. my Mikrotik Switch is monitored with SNMP, zabbix says:
yet i can ping the switch, and snmpwalk -c public -v2c shows all snmp values.
Same with my home-assistant debian vm.
Zabbix shows it cannot resolve the hostname.
Which is clearly a lie, because when i ping that machine in the zabbix web frontend, it works!
Here it stays "unreachable" for hours, even though it is clearly reachable.
# nc -zv home-assistant.hellgate.at 10050 Connection to home-assistant.hellgate.at (192.168.123.17) 10050 port [tcp/zabbix-agent] succeeded!
What is happening here?
I've ran zabbix servers and agents since zabbix 1.4, yet i have never had such a problem. Normally those "not reachable" hosts will recover after some minutes, when they are available again.
After the first reboot with the new Mainboard, the network config was wrong. The new network card had a new name.
Therefor those machines really were not reachable. But i fixed the network config, rebooted again.
And the Server now has the same IP as before, and all connections work. Yet Zabbix doesn't recover .... (waited 4+ hours already)
Also the zabbix server log file does not display any related errors, on Error Level 3.
Upgrade worked fine (check the logfile, it upgraded my psql database without problems).
All local checks, and simple ICMP ping checks work fine.
But ALL network related hosts are "unreachable".
e.g. my Mikrotik Switch is monitored with SNMP, zabbix says:
yet i can ping the switch, and snmpwalk -c public -v2c shows all snmp values.
Same with my home-assistant debian vm.
Zabbix shows it cannot resolve the hostname.
Which is clearly a lie, because when i ping that machine in the zabbix web frontend, it works!
Here it stays "unreachable" for hours, even though it is clearly reachable.
# nc -zv home-assistant.hellgate.at 10050 Connection to home-assistant.hellgate.at (192.168.123.17) 10050 port [tcp/zabbix-agent] succeeded!
What is happening here?
I've ran zabbix servers and agents since zabbix 1.4, yet i have never had such a problem. Normally those "not reachable" hosts will recover after some minutes, when they are available again.
After the first reboot with the new Mainboard, the network config was wrong. The new network card had a new name.
Therefor those machines really were not reachable. But i fixed the network config, rebooted again.
And the Server now has the same IP as before, and all connections work. Yet Zabbix doesn't recover .... (waited 4+ hours already)
Also the zabbix server log file does not display any related errors, on Error Level 3.