On 11/05/12 14:24, Mark Rogers wrote:
On 11/05/12 13:24, steve-ALUG@hst.me.uk wrote:
Is there anything else in the log that's getting a signal 15 at the same time as ntp dying?
Nothing else in the logs around that time, other than cron (which you'll recall was where I started).
Looking at them now (at about 2:02pm):
- hwclock reports the time as 13:02:35 UTC (correct)
- date reports the time as 13:16:46 UTC (~15 mins out).
ISTR something about NTP having trouble if the H/W clock and system time were vastly different, but I'd have thought it could cope with 15 mins, but more to the point, why are they different if NTP is working? Can you manually set both to more or less the correct time, and then see what happens?
The time jumping backwards, I would guess is because NTP *is* adjusting the clock, but, if NTP is running correctly, I'd have thought it would adjust the clock gradually, having noted the drift between the h/w clock and the internet time servers, rather than jumping.
But also, shouldn't it be adding something to the log to say it's changed the clock?
Ah, yes, probably.
Ideas: log ntp to a separate log file. Increase the debug-log level.
I couldn't see how to do this?
http://linux.die.net/man/8/ntpd if you kill the deamon, run it from a prompt, and use -d or -dd or -ddd etc for more levels of debug logging. As to logging to a separate file, I misread the config file - you can log the statistics to a file if you want by having statsdir /var/log/ntpstats/ in the conf file. Dunno if that would help though.
Notable is the comment on that page that regarding syslog that: "If your local server steps the time ahead or back suddenly, it will report that here also with a message such as: time reset -6.394626 s." I am not seeing anything like this logged.
Indeed.
I have a nagging feeling that this nothing to do with ntp. I've just killed ntp to see what happens to the clock in its absence.
Thanks for the help!
Dunno how much help I'm actually being! Don't really know what else to suggest - sorry! :-(
Steve