William Kenworthy wrote:
Is the clock almost in sync? - if its too far out ntp will silently fail
to sync (by design - large scale time steps can be destructive for
heavily active databases for instance)
Check out the -g option to ntpd in 'man ntpd'
or 'tinker panic 0' in ntp.conf
Also, has ntp.conf specified a writable frift file in a directory that
exists?
ntp can be VERY complex when it doesnt "just work" :)
BillK
It syncs and adjusts the time. It just doesn't do it like my older
rig. My old rig, when I booted it up, ntp would sync and in about a
hour or so it would be accurate enough that it would only sync a few
times a day. Since I have long uptimes, that worked out well. With
this new rig, it syncs about every ten to 15 minutes and adjusts and
just keeps doing the same thing. It never sets the drift file to a
setting that allows it to go more than ten or fifteen minutes without
resetting the clock. This is what is in messages:
Jan 4 21:09:26 localhost ntpd[10181]: time reset +0.636966 s
Jan 4 21:16:25 localhost ntpd[10181]: synchronized to 67.159.5.90,
stratum 2
Jan 4 21:22:53 localhost ntpd[10181]: synchronized to 64.6.144.6, stratum 2
Jan 4 21:26:01 localhost ntpd[10181]: time reset +0.567349 s
Jan 4 21:30:25 localhost ntpd[10181]: synchronized to 67.159.5.90,
stratum 2
Jan 4 21:41:09 localhost ntpd[10181]: time reset +0.603411 s
Jan 4 21:45:32 localhost ntpd[10181]: synchronized to 64.6.144.6, stratum 2
Jan 4 21:51:56 localhost ntpd[10181]: synchronized to 67.159.5.90,
stratum 2
Jan 4 21:54:39 localhost ntpd[10181]: synchronized to 64.6.144.6, stratum 2
Jan 4 21:56:17 localhost ntpd[10181]: time reset +0.604867 s
Jan 4 22:03:13 localhost ntpd[10181]: synchronized to 67.159.5.90,
stratum 2
Jan 4 22:07:18 localhost ntpd[10181]: synchronized to 64.6.144.6, stratum 2
Jan 4 22:11:56 localhost ntpd[10181]: time reset +0.649596 s
Jan 4 22:16:47 localhost ntpd[10181]: synchronized to 67.59.168.233,
stratum 3
Jan 4 22:20:06 localhost ntpd[10181]: synchronized to 67.159.5.90,
stratum 2
Jan 4 22:24:24 localhost ntpd[10181]: synchronized to 64.6.144.6, stratum 2
Jan 4 22:28:37 localhost ntpd[10181]: synchronized to 67.159.5.90,
stratum 2
Jan 4 22:28:46 localhost ntpd[10181]: time reset +0.621297 s
Jan 4 22:37:41 localhost ntpd[10181]: synchronized to 67.159.5.90,
stratum 2
Now on my old system, it would adjust the drift file and the adjustments
would get smaller and smaller. On the new rig, as you can see it stays
about the same. I would like it to get to a point where it doesn't have
to sync so often. I read on the website where they are needing more
servers to help with the load and I don't want to be one of the ones
putting a load on it.
I downgraded back to a stable ntp and it did generate a drift file after
a while. The messages above are from the stable ntp. I think I have it
configured correctly but just need to add a option somewhere to make it
do better. I'm even wondering if it could be something kernel related.
Maybe I forgot to enable something.
Dale
:-) :-)
