FW: Problems with distributed setup, master overload?
Tyler Lund
tlund at hostedsolutions.com
Tue Jun 26 17:02:17 CEST 2007
Marc Powell wrote:
> FWIW, I have a fairly large passive-only install with just over 4000
> passive checks every 5 minutes. I haven't experienced this problem. It's
> a pretty simple, standard install but one difference is I don't perform
> any host checks. Perhaps you have host checks that are not optimized or
> completing in a timely manner and are holding up processing of other
> tasks. Nagios will stop all other processing during host checks until
> they complete.
>
> --
> Marc
Marc,
Thanks for that little bit of info... I didn't realize Nagios behaved
this way. I played around with timing out host checks quickly, and even
turning them off globally to see if this made any difference, but I
still end up in situations where nagios just stops reading the command
fifo.
I think I may have narrowed it down to the even broker and ndo2db. I'm
running the ndo module and logging service info to a mysql database for
integration with other internal applications. Nagios seems to be getting
hung up talking to ndomod when the mysql database gets somewhat large
(>3 Gigs) . If I disable the ndo2db module or just truncate the tables
everything seems fine. I've been fine tuning the event broker and the
ndo2db config to try to keep the database as small as I can, but I think
the root cause of my problem is nagios getting busy dumping event broker
data and not getting around to reading that fifo.
Thanks,
-Tyler
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Nagios-users mailing list
Nagios-users at 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
More information about the Users
mailing list