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

Wagener, Brian H brian.h.wagener at lmco.com
Fri Nov 5 20:59:38 UTC 2004


I tried this, but nothing changed for me.  My clock is still not being
set.
Brian  

-----Original Message-----
From: Folkert van Heusden [mailto:folkert at vanheusden.com]
Sent: Friday, November 05, 2004 3:44 PM
To: Wagener, Brian H
Cc: questions at lists.ntp.isc.org
Subject: Re: [ntp:questions] Why won't my clock get set on QNX?


try
ntpd -g
that ignores offsets which are tooo big

On Fri, 5 Nov 2004, Wagener, Brian H wrote:

> Date: Fri, 05 Nov 2004 14:50:58 -0500
> From: "Wagener, Brian H" <brian.h.wagener at lmco.com>
> To: questions at lists.ntp.isc.org
> Subject: [ntp:questions] Why won't my clock get set on QNX?
>
> 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.
>
> #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
>
>
> #ntpd -d
> ntpd 4.2.0 at 1.1161-r Fri Nov 05 05:19:45 EST 2004 (2)
> addto_syslog: ntpd 4.2.0 at 1.1161-r Fri Nov 05 05:19:45 EST 2004 (2)
> addto_syslog: precision = 999.847 usec
> create_sockets(123)
> bind() fd 3, family 2, port 123, addr 0.0.0.0, flags=8
> bind() fd 4, family 24, port 123, addr ::, flags=0
> bind() fd 5, family 24, port 123, addr fe80:1::1, flags=0
> bind() fd 6, family 24, port 123, addr ::1, flags=0
> bind() fd 7, family 2, port 123, addr 127.0.0.1, flags=0
> bind() fd 8, family 24, port 123, addr fe80:2::230:59ff:fe01:80e2,
flags=0
> bind() fd 9, family 2, port 123, addr 192.9.201.105, flags=8
> init_io: maxactivefd 9
> local_clock: at 0 state 0
> peer_clear: at 0 assoc ID 53060 refid INIT
> 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
> addto_syslog: frequency initialized 0.000 PPM from
/mnt/fileserver/ntp/ntpd.vc.drift
> local_clock: at 0 state 1
> report_event: system event 'event_restart' (0x01) status 'sync_alarm,
sync_unspec, 1 event, event_unspec' (0xc010)
> transmit: at 1 192.9.201.105->166.27.114.72 mode 3
> auth_agekeys: at 1 keys 1 expired 0
> receive: at 1 192.9.201.105<-166.27.114.72 mode 4 code 1
> peer 166.27.114.72 event 'event_reach' (0x84) status 'unreach, conf, 1
event, event_reach' (0xa014)
> clock_filter: n 1 off 0.264327 del 0.000977 dsp 7.945801 jit 0.000977,
age 1
> auth_agekeys: at 60 keys 1 expired 0
> transmit: at 66 192.9.201.105->166.27.114.72 mode 3
> receive: at 66 192.9.201.105<-166.27.114.72 mode 4 code 1
> clock_filter: n 2 off 0.264327 del 0.000977 dsp 3.950439 jit 0.813947,
age 66
> auth_agekeys: at 120 keys 1 expired 0
> transmit: at 130 192.9.201.105->166.27.114.72 mode 3
> receive: at 130 192.9.201.105<-166.27.114.72 mode 4 code 1
> clock_filter: n 3 off 0.264327 del 0.000977 dsp 1.953114 jit 1.268243,
age 130
> auth_agekeys: at 180 keys 1 expired 0
> auth_agekeys: at 240 keys 1 expired 0
> transmit: at 259 192.9.201.105->166.27.114.72 mode 3
> receive: at 259 192.9.201.105<-166.27.114.72 mode 4 code 1
> clock_filter: n 4 off 0.264327 del 0.000977 dsp 0.955664 jit 2.120942,
age 259
> auth_agekeys: at 300 keys 1 expired 0
> auth_agekeys: at 360 keys 1 expired 0
> auth_agekeys: at 420 keys 1 expired 0
> auth_agekeys: at 480 keys 1 expired 0
> transmit: at 516 192.9.201.105->166.27.114.72 mode 3
> receive: at 516 192.9.201.105<-166.27.114.72 mode 4 code 1
> clock_filter: n 5 off 0.264327 del 0.000977 dsp 0.459345 jit 3.697629,
age 516
> auth_agekeys: at 540 keys 1 expired 0
> auth_agekeys: at 600 keys 1 expired 0
> auth_agekeys: at 660 keys 1 expired 0
> auth_agekeys: at 720 keys 1 expired 0
> auth_agekeys: at 780 keys 1 expired 0
> auth_agekeys: at 840 keys 1 expired 0
> auth_agekeys: at 900 keys 1 expired 0
> auth_agekeys: at 960 keys 1 expired 0
> auth_agekeys: at 1020 keys 1 expired 0
> transmit: at 1027 192.9.201.105->166.27.114.72 mode 3
> receive: at 1027 192.9.201.105<-166.27.114.72 mode 4 code 1
> clock_filter: n 6 off 13.056329 del 0.000977 dsp 0.210436 jit
10.629442, age 511
> auth_agekeys: at 1080 keys 1 expired 0
> auth_agekeys: at 1140 keys 1 expired 0
> auth_agekeys: at 1200 keys 1 expired 0
> auth_agekeys: at 1260 keys 1 expired 0
> auth_agekeys: at 1320 keys 1 expired 0
> auth_agekeys: at 1380 keys 1 expired 0
> auth_agekeys: at 1440 keys 1 expired 0
> auth_agekeys: at 1500 keys 1 expired 0
> auth_agekeys: at 1560 keys 1 expired 0
> auth_agekeys: at 1620 keys 1 expired 0
> auth_agekeys: at 1680 keys 1 expired 0
> auth_agekeys: at 1740 keys 1 expired 0
> auth_agekeys: at 1800 keys 1 expired 0
> auth_agekeys: at 1860 keys 1 expired 0
> auth_agekeys: at 1920 keys 1 expired 0
> auth_agekeys: at 1980 keys 1 expired 0
> auth_agekeys: at 2040 keys 1 expired 0
> transmit: at 2050 192.9.201.105->166.27.114.72 mode 3
> receive: at 2050 192.9.201.105<-166.27.114.72 mode 4 code 1
> clock_filter: n 2 off 25.913871 del 0.000977 dsp 0.088969 jit
12.857543, age 1023
> auth_agekeys: at 2100 keys 1 expired 0
> auth_agekeys: at 2160 keys 1 expired 0
> auth_agekeys: at 2220 keys 1 expired 0
> auth_agekeys: at 2280 keys 1 expired 0
> auth_agekeys: at 2340 keys 1 expired 0
> auth_agekeys: at 2400 keys 1 expired 0
> auth_agekeys: at 2460 keys 1 expired 0
> auth_agekeys: at 2520 keys 1 expired 0
> auth_agekeys: at 2580 keys 1 expired 0
> auth_agekeys: at 2640 keys 1 expired 0
> auth_agekeys: at 2700 keys 1 expired 0
> auth_agekeys: at 2760 keys 1 expired 0
> auth_agekeys: at 2820 keys 1 expired 0
> auth_agekeys: at 2880 keys 1 expired 0
> auth_agekeys: at 2940 keys 1 expired 0
> auth_agekeys: at 3000 keys 1 expired 0
> auth_agekeys: at 3060 keys 1 expired 0
> transmit: at 3074 192.9.201.105->166.27.114.72 mode 3
> receive: at 3074 192.9.201.105<-166.27.114.72 mode 4 code 1
> clock_filter: n 2 off 38.646568 del 0.000977 dsp 0.029155 jit
12.732696, age 1024
> auth_agekeys: at 3120 keys 1 expired 0
> auth_agekeys: at 3180 keys 1 expired 0
> auth_agekeys: at 3240 keys 1 expired 0
> auth_agekeys: at 3300 keys 1 expired 0
> auth_agekeys: at 3360 keys 1 expired 0
> auth_agekeys: at 3420 keys 1 expired 0
> auth_agekeys: at 3480 keys 1 expired 0
>
>
> Brian
>
> _______________________________________________
> questions mailing list
> questions at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/questions
>



Folkert van Heusden

+------------------------------------------------------------------+
|UNIX admin? Then give MultiTail (http://vanheusden.com/multitail/)|
|a try, it brings monitoring logfiles to a different level! See    |
|http://vanheusden.com/multitail/features.html for a feature list. |
+------------------------------------------= www.unixsoftware.nl =-+




More information about the questions mailing list