clock slip with ntpd and 9.3?

[swinokur]

Hi all,

I was running ntpd with no problems on my S3 & 9.2 -- since upgrading to 9.3 I've noticed that ntpd does not appear to be adjusting the clock on my tivo.


/var/log/messages shows things like this:

Apr 25 18:51:45 (none) ntpd[14085]: adjusting local clock by 19.936901s
Apr 25 18:55:28 (none) ntpd[14085]: adjusting local clock by 20.006539s
Apr 25 18:59:15 (none) ntpd[14085]: adjusting local clock by 20.066095s
Apr 25 19:00:37 (none) ntpd[14085]: adjusting local clock by 20.153424s
Apr 25 19:04:55 (none) ntpd[14085]: adjusting local clock by 20.244497s
Apr 25 19:07:41 (none) ntpd[14085]: adjusting local clock by 20.348223s
Apr 25 19:11:20 (none) ntpd[14085]: adjusting local clock by 20.448284s
Apr 25 19:14:13 (none) ntpd[14085]: adjusting local clock by 20.505045s
Apr 25 19:17:32 (none) ntpd[14085]: adjusting local clock by 20.568239s
Apr 25 19:18:42 (none) ntpd[14085]: adjusting local clock by 20.685773s

I can use rdate to force the clock into sync with a time server, but I'd rather be using ntpd.

Has anyone else run into this? I've checked the setup based on the initial install directions (files, directories, permissions) and I think everything is okay.

(I do notice that the /var/tmp/ntp directory is empty -- shouldn't there be a .drift file in there?)

[swinokur]

Hm... This might be the "Clock Drifts" problem that tivo talks about here:

hxxp://forums.tivo.com/pe/action/forums/displaysinglethread?rootPostID=10345632

Odd that I get it *after* the 9.3a update, where it seems that tivo has been trying to fix it.

[bizzy]

is ntpd configured to write a 'driftfile'; is it writable, and is it on persistent storage that survives reboots? It looks to me like ntpd is running with no driftfile available.

http://www.cis.udel.edu/~mills/ntp/html/miscopt.html#driftfile

[swinokur]

this version of ntpd gives a syntax error message when I add the driftfile argument to ntpd.conf.

Also remember that I mentioned that this version of ntpd kept time just fine with 9.2a but doesnt seem to do so for 9.3a

[bizzy]

What does an 'ntpq -p' show? If the binary isnt available on the tivo, you may be able to run 'ntpq -p <tivo address>' from another host on your network, depending on how your ntpd is configured.

[supernaut]

Hi all,

I was running ntpd with no problems on my S3 & 9.2 -- since upgrading to 9.3 I've noticed that ntpd does not appear to be adjusting the clock on my tivo.


/var/log/messages shows things like this:

Apr 25 18:51:45 (none) ntpd[14085]: adjusting local clock by 19.936901s
Apr 25 18:55:28 (none) ntpd[14085]: adjusting local clock by 20.006539s
Apr 25 18:59:15 (none) ntpd[14085]: adjusting local clock by 20.066095s
Apr 25 19:00:37 (none) ntpd[14085]: adjusting local clock by 20.153424s
Apr 25 19:04:55 (none) ntpd[14085]: adjusting local clock by 20.244497s
Apr 25 19:07:41 (none) ntpd[14085]: adjusting local clock by 20.348223s
Apr 25 19:11:20 (none) ntpd[14085]: adjusting local clock by 20.448284s
Apr 25 19:14:13 (none) ntpd[14085]: adjusting local clock by 20.505045s
Apr 25 19:17:32 (none) ntpd[14085]: adjusting local clock by 20.568239s
Apr 25 19:18:42 (none) ntpd[14085]: adjusting local clock by 20.685773s

I can use rdate to force the clock into sync with a time server, but I'd rather be using ntpd.

Has anyone else run into this? I've checked the setup based on the initial install directions (files, directories, permissions) and I think everything is okay.

(I do notice that the /var/tmp/ntp directory is empty -- shouldn't there be a .drift file in there?)

See the latest version posted.