logs

[Tony Earnshaw]

tor, 09.06.2005 kl. 23.58 skrev Arno Lehmann:

[...]

> >  >  I have turned on all types of logging options provided but the only 
> > I ever see is the startup log messages.  Apart from that I don't see any 
> > other log messages even the shutdown messages.
> >  >  Shouldn't I be seeing log of all actions nagios is performing?
> 
> Yes
> 
> > Another update - I ran the check_nagios command that the cgi should be 
> > running and here is its output:
> > 
> > "Nagios problem: located 3 processes, status log updated 1118352322 
> > seconds ago"
> > 
> > Does that mean that there should be only one nagios process running?
> 
> Not necessarily... although having more than one nagios process running 
> is usually an error. Try stopping nagios, wait some time and killall nagios.
> 
> What the above message tells is that the last write to the log was quite 
> a while ago... about 35 years, if I calculated correctly. I don't 
> believe that.

Actually, the log is giving incorrect info. What it should have said,
was: "Nagios problem: located 3 processes, status log updated
1118352322", period.

111835232 can be translated as: "Thu Jun  9 23:25:22 2005".

--Tonni

--

> Make sure your disk and filesystem are ok. Verify the file access 
> rights, or, possibly, rename that file and see if nagios starts a new one.
> 
> Arno
-- 
mail: tonye at billy.demon.nl
http://www.billy.demon.nl




-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
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