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