Fwd: check_nagios

[Rasmus Plewe]

On Fri, Mar 07, 2003 at 10:13:10PM +0800, Jasmine wrote:
> On Friday 07 March 2003 21:20, Jens Kruse wrote:
> >
> > I couldn't find a solution for the following problem with google, so
> > maybe someone has experienced this before ...
> >
> > check_nagios gives out the following ...
> >
> > nagios at monitor1-lx:~> /usr/local/nagios/libexec/check_nagios -F
> > /usr/local/nagios/var/status.log -e 5 -C /usr/local/nagios/bin/nagios
> > Nagios problem: located 80 processes, status log updated 1047042679
> > seconds ago
> >
> > though status.log is only some minutes old ...
> >
> > nagios at monitor1-lx:~> l var/status.log
> > -rw-r--r--    1 nagios   nagios          0 Mär  7 13:50 var/status.log
> 
> Hi I have the same problem too. And, would like to know hows its
> being solved.  
> - -rw-r--r--    1 root     root            0 Mar  7 22:05 status.log
> Time on checking: Fri Mar  7 22:12:44 SGT 2003

Simple: By making use of the file. You will notice that both your
files are empty, and if you had looked into the plugin source you
could have noticed the line:
        /* get the date/time of the last item updated in the log */


I didn't have a closer look at the source (but  it works for me with:
-rw-rw-r--    1 user    group      49078 Mar  7 15:51 status.log
and a "Nagios ok: located 167 processes, status log updated 9 seconds
ago" returned from the plugin). But I would think the guess is pretty
obvious. 


Rasmus


-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.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