<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0"> <TITLE>[Nagios-users] Notifications not visible for certain days</TITLE> </HEAD> <BODY> <DIV id=idOWAReplyText18456 dir=ltr> <DIV dir=ltr>Sudhir,</DIV> <DIV dir=ltr> </DIV> <DIV dir=ltr>Was there an adjustment of the system time on your nagios server ?</DIV> <DIV dir=ltr>When system time is adapted and time is stepped back, this cause strange results. Convert the epoch date in the two archives files to spit it out.</DIV> <DIV dir=ltr> </DIV> <DIV dir=ltr>To avoid such problems, sync your nagios server clock with xntpd.</DIV> <DIV dir=ltr> </DIV> <DIV dir=ltr>kind regards,</DIV> <DIV dir=ltr> </DIV> <DIV dir=ltr>ludo</DIV> <DIV dir=ltr> </DIV></DIV> <DIV dir=ltr> <HR tabIndex=-1> Van: nagios-users-admin@lists.sourceforge.net namens Sudhir Mahale Verzonden: vr 1/07/2005 15:43 Aan: nagios-users@lists.sourceforge.net Onderwerp: [Nagios-users] Notifications not visible for certain days </DIV> <DIV> All, I am running Nagios 1.2 and am facing this problem in vieiwing notifications for particular days. I do not see any notifications for particular days. During the day I see notifications being recorded. But the next day, after the log rotation the notifications disappear.If i go to Notifications => Earlier archive in the web interface, I see the message "No notifications have been recorded in this archived log file" I checked the var/archives and found that for the days that notifications are missing we have two archive files, for example one nagios-06-30-2005-00.log and the other nagios-06-30-2005-23.log For the days that we see the notifications, only one archive file , for example nagios-06-29-2005-00.log is seen Any help will be greatly appreciated. I use "24x7" for all my servers and "test" for one of the test boxes Thanks, Sudhir Note:- My time periods definition looks like this # '24x7' timeperiod definition define timeperiod{ timeperiod_name 24x7 alias 24 Hours A Day, 7 Days A Week sunday 08:00-24:00 monday 00:00-24:00 tuesday 00:00-24:00 wednesday 00:00-24:00 thursday 00:00-24:00 friday 00:00-24:00 saturday 00:00-20:00 } # 'test' timeperiod definition define timeperiod{ timeperiod_name test_ftmfedora alias Test time period for ftmfedora sunday 08:00-24:00 monday 00:00-24:00 tuesday 00:00-24:00 wednesday 00:00-24:00 thursday 00:00-22:20 friday 00:00-22:20 saturday 00:00-20:00 } # 'workhours' timeperiod definition define timeperiod{ timeperiod_name workhours alias "Normal" Working Hours monday 09:00-17:00 tuesday 09:00-17:00 wednesday 09:00-17:00 thursday 09:00-17:00 friday 09:00-17:00 } # 'nonworkhours' timeperiod definition define timeperiod{ timeperiod_name nonworkhours alias Non-Work Hours sunday 00:00-24:00 monday 00:00-09:00,17:00-24:00 tuesday 00:00-09:00,17:00-24:00 wednesday 00:00-09:00,17:00-24:00 thursday 00:00-09:00,17:00-24:00 friday 00:00-09:00,17:00-24:00 saturday 00:00-24:00 } # 'none' timeperiod definition define timeperiod{ timeperiod_name none alias No Time Is A Good Time } ___________________________________________________________ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos <A href="http://uk.photos.yahoo.com">http://uk.photos.yahoo.com</A> ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. <A href="http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click">http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click</A> _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net <A href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </DIV> </BODY> </HTML>