Question about "Last Check" fields.

Marc Powell marc at ena.com
Fri Mar 11 19:53:06 CET 2005



> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Michael Halligan
> Sent: Friday, March 11, 2005 12:43 PM
> To: nagios
> Subject: [Nagios-users] Question about "Last Check" fields.
> 
> I notice that even though I have all of my checks running every 5
minutes,
> the Last Check field in nagios will sometimes be several days out of
> date..
> What can I do to force nagio to be more accurate in that field? It has
> raised some doubt amongst management as to if Nagios is really working
or
> not.

Last Check data is updated at the same time the status information is
(i.e. when checks are performed) so they should always be accurate. Do
you have any orphaned check processes? Are you allowing enough
concurrent checks to be run (max_concurrent_checks)? Are you reaping
service check results often (service_reaper_frequency). I don't
understand why the information would be days old in either case. Perhaps
you _might_ have multiple daemons running? More information on your
installation, number of hosts and services and the type of hardware
might be helpful. Output of /path/to/nagios -s /path/to/nagios.cfg would
be informative as well.

--
Marc


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
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