Date: Tue, 01 Jan 2008 12:32:07 -0400 From: "Marc G. Fournier" <scrappy@hub.org> To: freebsd-questions@freebsd.org Cc: jarrod@netleader.com.au, freebsd-stable@freebsd.org Subject: Nagios + 6.3-RELEASE == Hung Process Message-ID: <59DD6CCE263ECD75A7283A7B@ganymede.hub.org>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 G'day ... Yesterday, I setup nagios to do some system monitoring ... installed the latest version from ports into a jail, so that I could easily move it around between machines as I upgrade, without losing data ... after about 30 minutes running, I get a second nagios process running (fork?) that takes up ch CPU time as is available, and just hangs there until I kill -9 it ... Figuring that it might be a problem with the jail (trying to access somethign that isn't available to the process in a jail), I moved it to the physical server level ... but, again, after ~30 minutes, its doing the same thing: # ps aux | grep nagios nagios 32065 73.2 0.1 10948 3516 ?? R 11:15AM 7:40.77 /usr/local/bin/nagios -d /usr/local/etc/nagios/nagios.cfg nagios 82120 0.0 0.1 10948 3580 ?? Ss 10:47AM 0:01.18 /usr/local/bin/nagios -d /usr/local/etc/nagios/nagios.cfg So, definitely not jail related ... I've tried to do a 'truss -p 32065', it just hangs. And: ktrace -f /tmp/output -p 32065 ... produces nothing: # kdump -f /tmp/output 32065 nagios PSIG SIGKILL SIG_DFL Once I kill -9 the process, a bunch of 'check_ping' processes start up and then things go back to normal ... My last kernel / world build on that box is: Mon Nov 12 06:43:30 AST 2007 After searching the 'Net a bit, came across this thread: <http://www.nagiosexchange.org/nagios-users.34.0.html?&tx_maillisttofaq_pi1%5Bmode%5D=1&tx_maillisttofaq_pi1%5BshowUid%5D=7694>; That recommends modifying libmap.conf with: [/usr/local/bin/nagios] libpthread.so.2 libthr.so.2 libpthread.so libthr.so This seems to fix the problem on the physical server, and am currently testing it in the jail itself to make sure it fixes it there too ... Should this be something that is more prominently documented somewhere? Maybe in the port itself? azureus has similar problems that are fixed with entries in libmap.conf, so its not "just a nagios issue" ... - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHemsH4QvfyHIvDvMRApUOAKCLRDnmRba6ho4St8qZ6U19V8yJ+wCghMBp Xph3ac9d7QsMjeKBMtmgkuw= =mXxF -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?59DD6CCE263ECD75A7283A7B>