On 17 September 2012 19:33, Gerald Turner <gtur...@unzane.com> wrote: > Mauro <mrsan...@gmail.com> writes: >> I think ntpd crashes are because my server lost time. >> I have ntpd in two server, now I've seen that in one of these ntp >> crashes and the time of the server is 1 hour forward. >> That's why ntp crashes: server time goes 1 hour forward and ntp can't >> resynchronize so it crashes. >> Now I don't know why my server time goes 1 hour forward. >> Hwclock --debug says that the time is correct, it is set on UTC, so >> why sometimes it goes forward? >> Perhaps a problem in the cmos battery? > > Hi Mauro, I find this interesting because I have seen the same behavior > with ntpd crashes on my server. Time jumps forward one hour every time > this has happened. However I'm not convinced it's the hardware causing > ntpd to crash. I don't understand why ntpd process exiting silently > would allow the jump either, I would expect it to drift a few seconds > over time, but one hour exactly every time?! Even with monit in place, > within the two minute window that polling takes place and ntpd has > crashed, before monit automatically starts ntpd, time is forward an > hour.
I'm trying openntp now, I hope it works. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cae17a0v5ughbzgwxraar4dsmktrv9hagt8dzaewhr9iw+ss...@mail.gmail.com
