[ntp:questions] Re: Why won't my clock get set on QNX?

Steve Kostecke kostecke at ntp.isc.org
Fri Nov 5 21:41:24 UTC 2004


On 2004-11-05, Wagener, Brian H <brian.h.wagener at lmco.com> wrote:

> I am running QNX on a PC104 stack running newest ntp. The internal
> clock is real bad, but ntpd is never correcting the clock. ntpd -q
> works to set the time, but when running as a daemon doesn't work. And
> I do set the time using ntpd -q before running as a daemon. Below is
> the debug log, and the ntpq -p.

Please configure your newsreader to wrap your lines of text at ~70
columns.

> #ntpq -p 192.9.201.105                              
>
>      remote       refid      st t when poll reach   delay   offset  jitter
>===========================================================================
>  166.27.114.72   0.0.0.0     15 u  429 1024  377    0.977  38646.5 12732.6

This tells me that 166.27.117.72 is not synchronized. You need to fix
this problem before you will be able to get clients (e.g. 192.9.201.105)
to sync with it.

> newpeer: 192.9.201.105->166.27.114.72 mode 3 vers 4 poll 6 10 \
>	flags 0x81 0x1 ttl 0 key 00000000
> addto_syslog: 166.27.114.72 is inappropriate address for the fudge \
>	command, line ignored

Are you trying to fudge 166.27.114.72 to something other that S15?

> addto_syslog: frequency initialized 0.000 PPM from \
>	/mnt/fileserver/ntp/ntpd.vc.drift

Have you tried deleting the drift file? If you do ntpd will spend some
time trying to calculate the drift value for your clock (which is most
likely _not_ 0.000 PPM).

-- 
Steve Kostecke <kostecke at ntp.isc.org>
NTP Public Support Project - http://ntp.isc.org/



More information about the questions mailing list