On Thursday 21 January 2010 07:24:26 [email protected] wrote: > > Having a bit of an issue at the moment with NTP. Server has been running > > for nigh on 2-3 years now. NTP was always running and always perfect. > > > > Recently had a truck take out power lines in the street and no power for > > 3-4 hours. Server sits behind somewhat out-of-date, (but still has > > reserve power) UPS and was shut down in time cleanly. > > > > However, since then server loses time BIG time. Funny thing is, other > > server in same subnet (also NTP) keeps perfect time. Both running CentOS > > 5.x. > > > > Now, could be any number of issues, just looking for some guidance on > > where to start looking pls? Anyone got any ideas? > > I would start with changing the CMOS battery and seeing if that makes > a difference.
Guys when saying *something* a few words of explanation is really nice for those reading the post. IMHO this is rubbish, the CMOS is not used after boot, *but* NTP won't fix gross errors, being too smart .. ntpdc -p tells you what your machine is doing npt logs explain lots ummm RTM there is a way to stop the daemon, set the time and restart the daemon. also look at the drift file (TBM - TheMan) again. Errors here will surely screwup things for a while. Also hwclock tells you about the CMOS clock James -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
