Re: ntpd crashes.
El 2012-09-21 a las 22:13 +0200, Mauro escribió:
(resending to the list)
> On 21 September 2012 16:30, Camaleón <noelamac@gmail.com> wrote:
> > On Fri, 21 Sep 2012 12:05:01 +0200, Mauro wrote:
> >
> >> On 20 September 2012 22:20, Mauro <mrsanna1@gmail.com> wrote:
> >>> On 20 September 2012 16:56, John Hasler <jhasler@newsguy.com> wrote:
> >>>> Someone who Stefan failed to identify wrote:
> >>>>> ...ntpd crashes on my server. Time jumps forward one hour every time
> >>>>> this has happened.
> >>>>
> >>>> I doubt ntpd is crashing. Most likely something else is jumping the
> >>>> system clock and ntpd is behaving as designed and exiting when it sees
> >>>> a one hour error. Shut down ntpd, set the clock correctly, and wait.
> >>>> I suspect that eventually you'll see the clock jump even without ntpd
> >>>> running.
> >>>
> >>> Yes that is.
> >>> I have no cron jobs at all, I only have xen and heartbeat + pacemaker
> >>> on my two nodes and no processes that set the system clock. The clock
> >>> jumps ahead of one or two hours and I don't know why. Perhaps some
> >>> kernel bug?
> >
> > ntpd should avoid the clock going that forward and keep it disciplined.
> >
> >> It seems not ntp problem but a kernel bug:
> >>
> >> http://my.opera.com/marcomarongiu/blog/2010/08/18/debugging-ntp-again-part-4-and-last
> >
> > You can try the mentioned work-around and see if that works for you.
> >
> > Anyway, if that's the case, you should experience the same with different
> > ntp daemons and not just with ntpd :-?
>
> I've experienced the same problem also with openntp.
That makes more sense.
Anyway, no NTP daemon should crash because of skewed time; one thing is
that it refushes to sync (which can be fine, and should log this fact
so the admin can make the proper measures) but a different thing is
completely killing the service.
> Now I'm back with ntp using the workaround mentioned, hope it works.
Perfect, tell us how it went.
Greetings,
--
Camaleón
Reply to: