Welcome to Pandora FMS Community › Forums › Community support › Host Alive starts to fail for all hosts, but works after Pandora server reboot
-
Host Alive starts to fail for all hosts, but works after Pandora server reboot
Posted by summa_sp on January 3, 2010 at 20:37Every few days, my Pandora server starts failing the Host Alive check for all hosts, all at once. The other modules and alerts work correctly, but it says every ICMP check for Host Alive has failed. A tcpdump of the network interface shows no ICMP packets being sent by the server. A restart of the Pandora server fixes the issue, and all the ICMP checks clear within a minute or two.
I’m running 3.0 RC2 in the OpenSUSE VM.
Sancho replied 15 years, 1 month ago 2 Members · 3 Replies -
3 Replies
-
::
Every few days, my Pandora server starts failing the Host Alive check for all hosts, all at once. The other modules and alerts work correctly, but it says every ICMP check for Host Alive has failed. A tcpdump of the network interface shows no ICMP packets being sent by the server. A restart of the Pandora server fixes the issue, and all the ICMP checks clear within a minute or two.
I’m running 3.0 RC2 in the OpenSUSE VM.
Check the server logs at /var/log/pandora/ for a clue on whats happening
-
::
I see a lot of these in /var/log/pandora/pandora_server.error. They don’t have time stamps, so I can’t be sure they are related. These are the only errors in the logs.
Use of uninitialized value $output in string eq at /usr/lib/perl5/site_perl/5.10.0/PandoraFMS/NetworkServer.pm line 268
. -
::
I see a lot of these in /var/log/pandora/pandora_server.error. They don’t have time stamps, so I can’t be sure they are related. These are the only errors in the logs.
Use of uninitialized value $output in string eq at /usr/lib/perl5/site_perl/5.10.0/PandoraFMS/NetworkServer.pm line 268
.These are “warnings”, not fatal errors. Anyway this is because a “missing” parameter in a SNMP module, like an empty SNMP OID, an empty SNMP target IP or empty SNMP community.
Try to set verbosity to 10, and watch errors in the logs again.