Nagios defunct processes

[Mark Frasa]

Hello,

We have nagios running for our network elements.
The amount of elements we are monotoring is 453 and the number of services is 588

The problem we are experiencing is that (mostly) after a restart of nagios we are getting defunct processes like:

nagios   14417  2593  0 Jan16 ?        00:00:00 [nagios <defunct>]

Some notes about the hardware:

Dell PowerEdge
Dual Intel(R) Xeon(TM) CPU 2.40GHz
1GB Memory

Nagios version:
# nagios -V

Nagios 2.5
Copyright (c) 1999-2006 Ethan Galstad (http://www.nagios.org)
Last Modified: 07-13-2006

Operating System:
Red Hat Enterprise Linux ES release 3 (Taroon Update 8)

After some debugging it turns out that every nagios command that's finished gets the status defunct first before being actually killed:

nagios   14489  0.0  0.0     0    0 ?        Z    15:44   0:00 [check_snmp] <defunct>
nagios   16851  0.0  0.0     0    0 ?        Z    15:44   0:00 [check_ssh] <defunct>
nagios   16851  0.0  0.0     0    0 ?        Z    15:44   0:00 [check_ssh] <defunct>
nagios   17838  0.0  0.0     0    0 ?        Z    15:44   0:00 [check_http] <defunct>


But when we have a defunct process we get served wrong information, like nagios is running twice. 
After we issue: kill -HUP <defunct_pid>; kill -9 <defunct_pid>; /etc/init.d/nagios start

Everything runs fine.. Does anyone know what causes this? Of even better; know how to fix this?

Thnx in advance!

Cheers,
Mark

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null