FYI, we have 266 hosts and 2744 services currently. This default setup didn't work very well for us with large volume of events affecting already overloaded mysql instance. Also it caused slight delays in Nagios restarts and processing as the process is syncronous - Nagios was waiting on event broker / db writes.
So currently it's setup with a 'buffer' file in the middle of processing: ndomod records events into a flat file /usr/local/groundwork/nagios/var/ndo.dat every 15 minutes Nagios runs another event broker command, rotate_ndo_log, which moves data from the flat file above to Unix socket read by ndo2db: /gw/nagios/bin/file2sock -s /gw/nagios/var/ndo.dat -d /gw/nagios/var/ndo.sock -t unix && /bin/mv /gw/nagios/var/ndo.dat /gw/nagios/var/ndo.`date +%s` This works well and gives a slight performance boost, however, from time to time it seems rotate command doesn't execute properly and ndo.dat file does not get rotated. Then, when that happens, file grows and every rotate_ndo_log execution takes longer and longer, until it exceeds it's timeout in nagios. And at that point, normal processing can only be restored by hand. It is not much of a problem in short term however, as no data is actually lost - file2sock and rotationg may be done manually w/o the timeout. Any clue as to why rorate_ndo_log would not work as expected? ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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