nagios 3 host checks logic problem on some kernels/distros

Ethan Galstad nagios at nagios.org
Thu Sep 20 23:19:41 CEST 2007


Thanks all - I found the cause of the problem and fixed it.  A patch 
will be in CVS shortly.

Thomas Stolle wrote:
> 
> From: SCHAER Frederic <frederic.schaer <at> cea.fr>
> Subject: *nagios 3 host checks logic problem on some kernels/distros* 
> <http://news.gmane.org/find-root.php?message_id=%3cEA04FF699CD5274E9EC52CB5EC0508707667A0%40DIODON.extra.cea.fr%3e>*
> Newsgroups: <http://news.gmane.org/gmane.network.nagios.devel>* 
> <http://news.gmane.org/gmane.network.nagios.devel>*MailScanner has 
> detected a possible fraud attempt from "news.gmane.org" claiming to be* 
> *gmane.network.nagios.devel* 
> <http://news.gmane.org/gmane.network.nagios.devel>*
> Date: 2007-09-10 16:17:30 GMT (1 week, 15 hours and 23 minutes ago) *
> 
> *Hi, *
> 
> *  *
> 
> *I think I identified a problem (but not and the solution) on the nagios 
> 3 source tree… *
> 
> *I tried with both the 3.0b3 and cvs HEAD source files and could not get 
> rid of the problem. *
> 
> *I’m running a 2.4.21 kernel on a RHEL3 box. *
> 
> *  *
> 
> *What happens is that as soon as I start nagios 3, it starts eating all 
> of the *CPU*. *
> 
[snip]
> 
> *I have 53 hosts defined, I don’t understand why nagios is checking ever 
> and ever the same host… and why this is not happening on all systems. *
> 
> *  *
> 
> *De-activating host checks magically “solves” the problem. *
> 
> *  *
> 
> *I just found out that commenting hosts “check_command” caused this 
> behaviour (with host_checks_enabled=true), and that defining a correct 
> check_command prevented nagios from being so *CPU* hungry… *
> 
> *  *
> 
> *Hope I helped… *
> 
> *  *
> 
> *Cheers *
> 
> 
> 
> Dear List,
> 
> I can confirm the problem Frederic reported.
> I am using Nagios 3.0b3 on CentOS 4.4
> After starting nagios, the process catches nearly 100 % CPU (See 
> top-output  below)
> Disableing hostchecks let the process return to normal values.
> As far as I can remember, the problem did not occour with nagios3.0a 
> (but I can not verify at the moment)
> 
> Tasks:  89 total,   3 running,  86 sleeping,   0 stopped,   0 zombie
> Cpu(s): 26.0% us,  1.3% sy,  0.0% ni, 72.6% id,  0.0% wa,  0.1% hi, 
>  0.0% si
> Mem:   4041580k total,  1373844k used,  2667736k free,    60200k buffers
> Swap:  4192956k total,        0k used,  4192956k free,  1137348k cached
> 
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
> 28617 nagios    25   0 29756  10m 1056 R   96  0.3  17:12.48 nagios
>     1 root      16   0  4752  552  460 S    0  0.0   0:02.75 init
>     2 root      RT   0     0    0    0 S    0  0.0   0:00.04 migration/0
> 
> 
> Thomas
> 
> 
> P *Please consider the environmental impact of needlessly printing this 
> e-mail.*
> 


Ethan Galstad,
Nagios Developer
---
Email: nagios at nagios.org
Website: http://www.nagios.org

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/




More information about the Developers mailing list