Felipe Neuwald wrote: > Andreas, > > of course I'm killing the process, but it's happening every time. The > service isn't in production cause this. >
Reread second paragraph of first response, and please refrain from top-posting. > Felipe. > > Andreas Ericsson escreveu: >> Felipe Neuwald wrote: >>> Hi Folks, >>> >>> I'm running nagios 2.9_2 and nagios-plugins 1.4.10,1 on a FreeBSD >>> 6.3-PRERELEASE system. >>> >>> [EMAIL PROTECTED] /]# pkg_info | grep nagios >>> nagios-2.9_2 Extremely powerful network monitoring system >>> nagios-plugins-1.4.10,1 Plugins for Nagios >>> [EMAIL PROTECTED] /]# uname -a >>> FreeBSD neptune.domain 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #0: Tue >>> Nov 27 14:38:41 BRST 2007 >>> [EMAIL PROTECTED]:/usr/src/sys/i386/compile/KERNEL1 i386 >>> >>> >>> Sometimes, nagios hangs with two nagios processes: >>> >> >> It happens every now and then. >> >>> [EMAIL PROTECTED] /]# ps ax | grep nagios >>> 65648 ?? Ss 0:04.50 /usr/local/bin/nagios -d >>> /usr/local/etc/nagios/nagios.cfg >>> 80843 ?? R 146:15.03 /usr/local/bin/nagios -d >>> /usr/local/etc/nagios/nagios.cfg >>> 89388 p0 R+ 0:00.00 grep nagios >>> >>> The PID 80843 uses 99% of my CPU, and it is hanging nagios. Anybody >>> knows how can I solve this? >>> >> >> $ man kill >> >> >> For a more permanent solution, browse the nagios-devel archives and >> apply the patch which prevents spinlocks on pthread mutexes. You'll >> have to mangle it a bit first, I think. >> > -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Nagios-users mailing list [email protected] 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
