Problems with many hanging Nagios processes (Nagios spawning rogue nagios processes eventually crashing Nagios server)

Gaspar, Carson Carson.Gaspar at gs.com
Wed Dec 20 01:58:24 CET 2006


Mahesh Kunjal wrote:
> 
> This was not enough and the child process started to wait for memory
to be freed so that the pipe data retrieved can be put in buffer.
> 
> While this child process waited for memory to be freed, the command
worker thread got woken up and realized that there is data in pipe and
forked another child. This got repeated and eventually server went out
of memory.

This is a bug. A second reader should not be created if a prior reader
still exists. Locking is required here.

-- 
Carson

-------------------------------------------------------------------------
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




More information about the Developers mailing list