I scanned the mailing list trying to find a solution for this. I found a brief discussion where someone had the same problem but there was nothing really discussed what was potentially wrong.
My system: Dual 2.8GHz P4 processors 4GB of RAM FreeBSD 6.1-RELEASE-p10 Running processes: Nagios 2.6 (installed from ports without embedded perl or nanosleep) One mysqld process for the nagiosweb utility A few NSCA daemon processes for passive checking A backup tool daemon Apache+modssl (latest from ports) Basic FreeBSD services (sshd, sendmail, etc.) Problem: Random service and host check control processes will lock up and 'spin' on the CPU. This is really bad when a host check does it because it brings all checks to a halt. It doesn't seem to even notice that all checks have gone stale. It will look like this in top: PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 94068 nagios 1 116 0 7500K 6748K CPU2 0 727:37 30.15% nagios 94082 nagios 1 116 0 7500K 6748K CPU2 0 734:28 32.55% nagios 94104 nagios 1 116 0 7500K 6748K CPU2 0 845:21 37.42% nagios 75338 nagios 5 20 0 7500K 6776K kserel 0 91:33 0.00% nagios In this example the main nagios pid is 75338. The hung service and/or host processes are the other ones. The service checks are almost entirely custom scripts, but the host check is a standard check_ping that comes with the nagios program. Any ideas on how to figure out which service or host check is hung? Or how to deal with this problem at all? Jonathan Call Network Engineer - NTT/Verio 801.437.7476 ------------------------------------------------------------------------- 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 _______________________________________________ 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
