Nagios 3.0.5 problem

[Rick Mangus]

Patrick:

The check results are being written to a ramdisk, so I think we're
safe on that.  :(

I am now starting to examine what happens when nagios sends perfdata
to service_perfdata_command.  In the case of perfparse, it is a perl
script that opens a named pipe for appending, and tacks the perfdata
on the end.  That leaves an option for blocking i/o that should exit
in 5 seconds due to the perfdata_timeout, but should happen
~2000x/minute.

While I think I can tweak the database performance or queue my
perfdata logging, I still think there's something inelegant about
that. On the other hand, once it works, I'll stop spending my time
writing test scripts and sql queries.

--Rick

On Thu, Feb 4, 2010 at 1:29 AM, Morris, Patrick <patrick.morris at hp.com> wrote:
>
> Rick Mangus wrote:
<snip>
> Are your check results going to the same disk partition where all the I/O is happening?  If Nagios is stuck waiting for disk, moving them somewhere else may just fix your problem.

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
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