Ah... I just needed to wait a while longer... when the lateindex services triggered, it then rescheduled them for 1:00am. I did force checks on the index services and they were rescheduled correctly as well.
Thanks for your help! Andrew On Tue, Jun 30, 2009 at 8:46 AM, Andrew Noonan<anoo...@gmail.com> wrote: > Ah, yes. That would be the danger of using a GUI, I suppose. You're > absolutely correct, I clicked on the wrong one when setting these up. > Confusing everyone else was just a fun side-effect. That being said, > I went ahead and changed those so they match up, but I'm still seeing > strange behavior. The index service is next scheduled at 1:00am, and > the lateindex service is next scheduled at 8:45am (it's 8:40am now > here). I would have expected those services to be properly > rescheduled to basically the exact opposite. The lateindex should be > 1:00am and the index service should be the currently running service. > And yes, I did check to make sure that the index service is running > the correct service template and vice versa :) Do I need to do > something to reset the scheduler over then a reload? > > Andrew > > >> >> This looks decidedly odd. "Time-7a_to_1a" uses the check_period >> "1a-7a_every_day". Either you were very confused when you named >> the timeperiods or you were very confused when you created these >> templates. Or you just want to confuse everyone else ;-) >> >> I'm guessing they should be reversed, no? >> >> -- >> Andreas Ericsson andreas.erics...@op5.se >> OP5 AB www.op5.se >> Tel: +46 8-230225 Fax: +46 8-230231 >> >> Considering the successes of the wars on alcohol, poverty, drugs and >> terror, I think we should give some serious thought to declaring war >> on peace. >> > ------------------------------------------------------------------------------ _______________________________________________ Nagios-users mailing list Nagios-users@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
