Please turn on debugging in
nagios.cfg. Set
debug_level to
-1 and
debug_verbosity to
2. Then, restart nagios.
Now, when you see the message appear please run
ps uw -C nagios, and see which PID is taking up the most resources. Run
gdp -p pid (install gdp if needed, and replace pid with the #). Now, run
bt and post the results of the backtrace here. This should help out developers see what exactly is going on.
An example is below -
- Code: Select all
# ps uw -C nagios
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
nagios 8828 0.0 0.0 18636 2860 ? Ss 10:55 0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios 8829 0.0 0.0 12932 2624 ? S 10:55 0:00 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagi
nagios 8831 25.3 0.0 12932 2624 ? S 10:55 0:00 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagi
nagios 8835 0.0 0.0 18120 1624 ? S 10:55 0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
# gdb -p 8831
. . . a couple of pages of gdb stuff . . .
(gdb) bt
#0 0x00007f2f5ae63643 in __epoll_wait_nocancel () from /lib64/libc.so.6
#1 0x0000000000472b80 in iobroker_poll (iobs=0x108c040, timeout=timeout@entry=30004)
at iobroker.c:337
#2 0x000000000047595e in enter_worker (sd=sd@entry=3, cb=<optimized out>)
at worker.c:830
#3 0x0000000000416166 in nagios_core_worker (
path=0x7ffc391d2ed0 "/usr/local/nagios/var/rw/nagios.qh") at nagios.c:182
#4 main (argc=<optimized out>, argv=0x7ffc391d2c48) at nagios.c:318
(gdb) detach
Detaching from program: /usr/local/nagios/bin/nagios, process 8829
(gdb) q
#
It might not be the same problem, but it's most likely related to this thread somehow.
viewtopic.php?f=7&t=36767#p169505