Odd errors in nagios.log

[Marc Ismael]

On Thu, Apr 16, 2009 at 5:43 PM, Martin A. Brooks <martin at antibodymx.net>wrote:

> Jim Avery wrote:
> > You don't have more than one instance of the Nagios daemon running do
> > you?  Try stopping the Nagios daemon, make sure all instances of
> > nagios are stopped (using ps -ef | grep nagios), and kill any which
> > remain then start the Nagios daemon using /etc/init.d/nagios start .
>
> I looked for the before, and there's definitely only one nagios instance
> running.   The problem persists across nagios restarts and reboots.
>
> Thanks
>
> --
> Martin A. Brooks |  http://www.antibodymx.net/ | Anti-spam & anti-virus
>   Consultant    |  martin at antibodymx.net      | filtering. Inoculate
>  antibodymx.net  |  m: +447792493388           | your mail system.
>
>
>
try playing around with your check_result_reaper_* timings. I have a feeling
that your check results are already stale before the reaper gets a chance to
process them.

tip: for a while, try setting max_check_result_file_age to 0 and see if
you'd still get these errors. if not, then its a timing misconfiguration.

cheers,
Marc.I
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090417/150d1255/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
-------------- next part --------------
_______________________________________________
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