Strange service scheduling

[Bernd Arnold]

> Hi,
> 
> Yes I have the same problem with this patch. For me the problem is only
> for
> services with timeperiods like this :
> 
> define timeperiod{
>        timeperiod_name  mytimeperiod
>        alias            a simple timeperiod definition
>        monday           07:30-12:00
>  }
> 
> 
> 
> --
> Julien  Mathis, CTO
> www.merethis.com
> Mobile  : +33(0)6.85.43.88.38
> Bureau : +33(0)1.78.12.00.23
> 
> 
> On Mon, Mar 2, 2009 at 4:59 PM, Ricardo Maraschini <
> ricardo.maraschini at opservices.com.br> wrote:
> 
> > Hi,
> >
> > ----- "Ricardo Maraschini" <ricardo.maraschini at opservices.com.br>
> > escreveu:
> > > Hello,
> > >
> > >    We had a strange behaviour with a service schedule last night; The
> > > service was scheduled to be checked only on February/2010(Fri Feb 26
> > > 00:08:36 2010). This is very strange, looking to the code we found the
> > > following piece:
> > >
> > > -------
> > >
> > > base/checks.c:
> > >
> > > /* the service could not be rescheduled properly - set the next check
> > > time for next year, but don't actually reschedule it */
> > >      if(time_is_valid==FALSE && next_valid_time==preferred_time){
> >
> >
> > Is there any problem with following patch?
> > http://article.gmane.org/gmane.network.nagios.devel/5554/match=next+year
> >
> > Awaiting.
> >
> > -rm
> >
> >
> >

Hi,

did you experience this strange re-scheduling after manually applying my patch? The patch you've mentioned isn't applied in the official source code, see (revision 1.167)

http://nagios.cvs.sourceforge.net/viewvc/nagios/nagios/base/checks.c?view=markup#l_282

There is still the line 285

svc->next_check=(time_t)(next_valid_time+(60*60*24*365));

Please try my patch and check if the services are re-scheduled properly then. If the re-scheduling isn't working correctly though you're running Nagios with this patch, please tell me too.

Thanks.

Regards
Bernd

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

------------------------------------------------------------------------------