Alleviating Nagios i/o contention problem

[Matthias.Flacke at gmx.de]

> - The ramdisk idea is also interesting.   I'm curious though, about why one
> would want to rsync it back to the local disk periodically.  It's just a
> run-time status file, right?  Unless I misread the docs, it goes away when
> Nagios is shut down.  What would having a local disk copy of status.dat
> benefit me?  Also, nagios.log isn't written to that often in our case (we
> don't log passive check results, for example).  I'm not sure I'd see the
> benefit for us in putting that on ramdisk.  Although... we do have Splunk
> watch that file so that would be some additional read overhead I guess.

This is a misunderstanding ;). Only nagios.log needs to be saved for statistics, history etc, but status.dat and the checkresults files do not. status.dat will be recreated soon and losing some checkresults is mostly a matter of the retry interval.

nagios.log - as you said - depends on the traffic there. Max as far as I remember syncs it regularily. We normally have less than 5 messages per minute, so no reason to put it on ramdisk.

-Matthias

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
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