<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <style>  </style> </head> <body lang=FR link=blue vlink=purple> <div class=Section1> Hi,<o:p></o:p> <o:p> </o:p> I think I identified a problem (<s>but not</s> and the solution) on the nagios 3 source tree…<o:p></o:p> I tried with both the 3.0b3 and cvs HEAD source files and could not get rid of the problem.<o:p></o:p> I’m running a 2.4.21 kernel on a RHEL3 box.<o:p></o:p> <o:p> </o:p> What happens is that as soon as I start nagios 3, it starts eating all of the CPU.<o:p></o:p> Stracing the nagios process shows this (and almost only this):<o:p></o:p> gettimeofday({1189419621, 161574}, NULL) = 0<o:p></o:p> time([1189419621]) = 1189419621<o:p></o:p> time([1189419621]) = 1189419621<o:p></o:p> gettimeofday({1189419621, 183742}, NULL) = 0<o:p></o:p> gettimeofday({1189419621, 183780}, NULL) = 0<o:p></o:p> gettimeofday({1189419621, 183814}, NULL) = 0<o:p></o:p> time([1189419621]) = 1189419621<o:p></o:p> gettimeofday({1189419621, 184172}, NULL) = 0<o:p></o:p> gettimeofday({1189419621, 184326}, NULL) = 0<o:p></o:p> time([1189419621]) = 1189419621<o:p></o:p> time([1189419621]) = 1189419621<o:p></o:p> gettimeofday({1189419621, 184734}, NULL) = 0<o:p></o:p> gettimeofday({1189419621, 184861}, NULL) = 0<o:p></o:p> <o:p> </o:p> I tried stracing nagios on a Ubuntu feisty (7.04) box, and the output is much different : there are nanosleep calls…<o:p></o:p> I tried activating and deactivating nanosleeps at nagios compile time, but this did not solve my problem.<o:p></o:p> <o:p> </o:p> Having full debug, I have this kind of output at the nagios start :<o:p></o:p> [1189438977.881574] [016.0] [pid=18234] Attempting to run scheduled check of host 'wn010': check options=0, latency=0.874000<o:p></o:p> [1189438977.881651] [001.0] [pid=18234] run_async_host_check_3x()<o:p></o:p> [1189438977.881665] [016.0] [pid=18234] ** Running async check of host 'wn010'...<o:p></o:p> [1189438977.881678] [001.0] [pid=18234] check_host_check_viability_3x()<o:p></o:p> [1189438977.881691] [001.0] [pid=18234] check_time_against_period()<o:p></o:p> [1189438977.881712] [001.0] [pid=18234] check_host_dependencies()<o:p></o:p> [1189438977.881726] [016.1] [pid=18234] A check of this host is already being executed, so we'll pass for the moment...<o:p></o:p> [1189438977.881739] [016.1] [pid=18234] Unable to run scheduled host check at this time<o:p></o:p> <o:p> </o:p> If I run nagios just for 2 seconds and then hit CTRL+C, I still see this :<o:p></o:p> >grep "A check of this host is already being executed" /var/log/nagios/nagios.debug | wc -l<o:p></o:p> 971<o:p></o:p> <o:p> </o:p> >grep "Attempting to run scheduled check of host 'wn010'" /var/log/nagios/nagios.debug | wc -l<o:p></o:p> 971<o:p></o:p> >grep "Attempting to run scheduled check of host" /var/log/nagios/nagios.debug | wc -l<o:p></o:p> 971<o:p></o:p> <o:p> </o:p> 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.<o:p></o:p> <o:p> </o:p> De-activating host checks magically “solves” the problem.<o:p></o:p> <o:p> </o:p> 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…<o:p></o:p> <o:p> </o:p> Hope I helped…<o:p></o:p> <o:p> </o:p> Cheers<o:p></o:p> </div> </body> </html>