When a service goes offline, nagios is supposed to tell nagios ircbot about it. The message gets to nagircbot but nagios is stuck in a dead heat run at 100% cpu on read()
[1215140088.267404] [256.1] [pid=12801] Running command '/bin/echo "PROBLEM DispatchBuddy Internal_PING_WAP_Dayroom CRITICAL $OUTPUT$ $DATETIME$" > /etc/nagios/nagiosbot.pipe &'... [1215140088.274510] [064.1] [pid=12801] Making callbacks (type 10)... [1215140088.284985] [001.0] [pid=20014] process_macros() [1215140088.285654] [001.0] [pid=20014] process_macros() [1215140088.285925] [001.0] [pid=20014] process_macros() [1215140088.286113] [001.0] [pid=20014] process_macros() [1215140088.286279] [001.0] [pid=20014] process_macros() [1215140088.286455] [001.0] [pid=20014] process_macros() [1215140088.290542] [001.0] [pid=20014] process_macros() [1215140088.290890] [001.0] [pid=20014] process_macros() [1215140088.291084] [001.0] [pid=20014] process_macros() This was about 2.5 hours ago, the time now is +9400 seconds (2h36m) nagios is doing nothing else but: [...] read(7, 0xbfa75b1c, 1023) = -1 EAGAIN (Resource temporarily unavailable) read(7, 0xbfa75b1c, 1023) = -1 EAGAIN (Resource temporarily unavailable) read(7, 0xbfa75b1c, 1023) = -1 EAGAIN (Resource temporarily unavailable) read(7, 0xbfa75b1c, 1023) = -1 EAGAIN (Resource temporarily unavailable) read(7, 0xbfa75b1c, 1023) = -1 EAGAIN (Resource temporarily unavailable) read(7, 0xbfa75b1c, 1023) = -1 EAGAIN (Resource temporarily unavailable) read(7, 0xbfa75b1c, 1023) = -1 EAGAIN (Resource temporarily unavailable) read(7, 0xbfa75b1c, 1023) = -1 EAGAIN (Resource temporarily unavailable) read(7, 0xbfa75b1c, 1023) = -1 EAGAIN (Resource temporarily unavailable) read(7, 0xbfa75b1c, 1023) = -1 EAGAIN (Resource temporarily unavailable) read(7, 0xbfa75b1c, 1023) = -1 EAGAIN (Resource temporarily unavailable) read(7, 0xbfa75b1c, 1023) = -1 EAGAIN (Resource temporarily unavailable) read(7, 0xbfa75b1c, 1023) = -1 EAGAIN (Resource temporarily unavailable) [...] Ranger data # ls -l /proc/12801/fd/7 lr-x------+ 1 root root 64 Jul 4 01:32 /proc/12801/fd/7 -> pipe:[65450357] Ranger data # lsof|grep 65450357 nagios 12801 nagios 7r FIFO 0,5 65450357 pipe sh 20016 nagios 8w FIFO 0,5 65450357 pipe Ranger data # ps auxww|grep 20016 nagios 20016 0.0 0.0 2816 560 ? S Jul03 0:00 sh -c /bin/echo "PROBLEM DispatchBuddy Internal_PING_WAP_Dayroom CRITICAL $OUTPUT$ $DATETIME$" > /etc/nagios/nagiosbot.pipe & nagios won't do anything further. I have to restart it. ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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