Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
[Wed Nov 21 23:57:43 2018] wproc: Core Worker 22697: job 13048 (pid=105199) timed out. Killing it
[Wed Nov 21 23:57:43 2018] wproc: CHECK job 13048 from worker Core Worker 22697 timed out after 30.01s
[Wed Nov 21 23:57:43 2018] wproc: host=ATTESTSR05; service=(null);
[Wed Nov 21 23:57:43 2018] wproc: early_timeout=1; exited_ok=0; wait_status=0; error_code=62;
[Wed Nov 21 23:57:43 2018] wproc: stdout line 01: PING CRITICAL - Packet loss = 100%|rta=5000.000000ms;3000.000000;5000.000000;0.000000 pl=100%;75;100;0
I don't understand what it means, because single ping can't get a timeout.
The problem for me is, that this wproc errors are sometimes the last output before the nagios process dies. It seems to me, as if nagios would kill himself.
This message is normal when the host check fails and would indicate that the host is down or not responding to icmp packets. Are you able to ping ATTESTSR05 from the command line of the nagios machine? It's not uncommon for icmp packets to be dropped and you may need to rely on a different plugin to check this host.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.