Dormant child reaped

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
lgaddam
Posts: 116
Joined: Wed Aug 28, 2019 1:01 am

Dormant child reaped

Post by lgaddam »

HI Guys,

I used to get error like below in /var/log/messages & /usr/local/nagios/var/nagios.log.
Is these type of errors ae critical and do affect Nagios system, please help....

[root@p01 ~]# tail -25 /usr/local/nagios/var/nagios.log
[1599329870] wproc: CHECK job 2281 from worker Core Worker 8532 timed out after 60.01s
[1599329870] wproc: host=CMEVDBT - 192.168.4.52; service=OracleServiceORCL;
[1599329870] wproc: early_timeout=1; exited_ok=0; wait_status=0; error_code=62;
[1599329870] Warning: Check of service 'OracleServiceORCL' on host 'CMEVDBT - 192.168.4.52' timed out after 60.007s!
[1599329870] SERVICE ALERT: CMEVDBT - 192.168.4.52;OracleServiceORCL;CRITICAL;SOFT;1;(Service check timed out after 60.01 seconds)
[1599329870] wproc: Core Worker 8532: job 2281 (pid=24586): Dormant child reaped
[1599329870] SERVICE ALERT: FSTOR16 - 192.168.27.2;CPU Usage;OK;SOFT;2;OK (Sample Period 60 sec) - Average CPU Utilisation 0.36%
[1599329870] SERVICE ALERT: CMEVDBT - 192.168.4.52;OracleServiceORCL;OK;SOFT;2;OK - Found 0 Services(s), 0 OK and 0 with problems (0 excluded).
[1599329874] Warning: Return code of 255 for check of service 'Nagios' on host 'nagios-servicios-192.168.200.60' was out of bounds.
[1599329874] Warning: Return code of 255 for check of service 'CPU Usage' on host 'SGLWODGI01 : 192.168.202.82' was out of bounds.
[1599329876] SERVICE ALERT: FSSIG12 - 192.168.42.1;CPU Usage;OK;SOFT;2;OK (Sample Period 60 sec) - Average CPU Utilisation 0.67%
[1599329877] wproc: Core Worker 8530: job 2290 (pid=25893) timed out. Killing it
[1599329877] wproc: CHECK job 2290 from worker Core Worker 8530 timed out after 60.01s
[1599329877] wproc: host=SOURCESAFE : 192.168.5.175; service=Memory Usage;
[1599329877] wproc: early_timeout=1; exited_ok=0; wait_status=0; error_code=62;
[1599329877] Warning: Check of service 'Memory Usage' on host 'SOURCESAFE : 192.168.5.175' timed out after 60.006s!
[1599329877] wproc: Core Worker 8530: job 2290 (pid=25893): Dormant child reaped
[1599329879] wproc: Core Worker 8535: job 2292 (pid=26088) timed out. Killing it
[1599329879] wproc: CHECK job 2292 from worker Core Worker 8535 timed out after 60.01s
[1599329879] wproc: host=Ucm11prod - 192.168.172.36; service=Uptime;
[1599329879] wproc: early_timeout=1; exited_ok=0; wait_status=0; error_code=62;
[1599329879] Warning: Check of service 'Uptime' on host 'Ucm11prod - 192.168.172.36' timed out after 60.011s!
[1599329879] wproc: Core Worker 8535: job 2292 (pid=26088): Dormant child reaped
[1599329883] SERVICE ALERT: CMEVDBT - 192.168.4.52;Memory Usage;OK;SOFT;2;OK - Physical Memory: Total: 11.989GB - Used: 1.097GB (9%) - Free: 10.892GB (91%)
[1599329894] SERVICE ALERT: FE32C - 10.1.30.36;CogentDataHubV7.exe;OK;SOFT;2;OK - Found 1 Instance(s) of "CogentDataHubV7.exe" running (0 excluded). (List is on next line)
[root@p01 ~]#
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Dormant child reaped

Post by scottwilkerson »

The "Dormant child reaped" line isn't an error, it is just the cleanup that happens after a host/service check goes to the timeout limit, and the process is getting cleaned up
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
Locked