This may sound odd, but look at /etc/ntp/drift
it). There should be a number in it, can be zero, negative or positive, doesn't matter, but there needs to be a value -- in the "old days," NTP wouldn't sync up properly if that file was null and you had to poke a zero in it for things to get going (echo 0 > /etc/ntp/drift
). After a raw install of 13.1 I found that I had to do that, who knows why, might be worth a shot.
The other thing is your ntp.conf
file; this one works (on all my systems, Slackware and SPARC Solaris). Edit the country code to suit your location:
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
# Drift file. Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
multicastclient # listen on default 220.127.116.11
# Keys file. If you want to diddle your server at run time, make a
# keys file (mode 600 for sure) and define the key number to be
# used for making requests.
# PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote
# systems might be able to reset your clock at will.
# Don't serve time or stats to anyone else by default (more secure)
restrict default noquery nomodify
# Trust ourselves. :-)
I like to have a log file and I stick it in /tmp/ntp.log
. It gets blown away every time the daemon is started. I do that by slightly modifying /etc/rc.d/rc.ntpd
# Start/stop/restart ntpd.
# Start ntpd:
# Clear the log file
echo -n "Starting NTP daemon: $CMDLINE"
$CMDLINE -p /var/run/ntpd.pid -l /tmp/ntp.log
You may need to set your clock (with ntpdate
) just to get it "close enough" that NTP will sync (if it's too far off, ntpd
And, finally, it might be an idea to ping the servers you've specified and see what kind of response you get (just make sure the things actually exist, eh).
Hope this helps some.