Time Synchronization with ntpd

QNX USERS QNX6 - Applications
1

Hi All

I use the ntpd command to synchronize the local time with Windows server, I found no synchronization done.kindly please help for advice.

thanks in advance

Shilunz

ntpd -d

create_sockets(123)
interface OK
ignoring lo0 - not AF_INET
interface OK
interface OK
ignoring en0 - not AF_INET
interface OK
bind() fd 3, family 2, port 123, addr 0.0.0.0, flags=1
bind() fd 4, family 2, port 123, addr 127.0.0.1, flags=0
bind() fd 5, family 2, port 123, addr 192.168.0.41, flags=1
init_io: maxactivefd 5
peer_clear: at 0 assoc ID 0
newpeer: 192.168.0.41->192.168.0.100 mode 3 vers 4 poll 6 10 flags 281 1 ttl 0 k
ey 00000000
report_event: system event ‘event_restart’ (0x01) status ‘sync_alarm, sync_unspe
c, 1 event, event_unspec’ (0xc010)
transmit: at 1 192.168.0.41->192.168.0.100 mode 3
auth_agekeys: at 1 keys 1 expired 0
receive: at 1 192.168.0.41<-192.168.0.100 mode 4 code 1
peer 192.168.0.100 event ‘event_reach’ (0x84) status ‘unreach, conf, 1 event, ev
ent_reach’ (0x8014)
clock_filter: n 1 off 638.423131 del 0.000488 dsp 7.945557 jit 0.000488, age 0
transmit: at 16 192.168.0.41->192.168.0.100 mode 3
receive: at 16 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423426 del 0.000488 dsp 3.949641 jit 0.000488, age 0
transmit: at 17 192.168.0.41->192.168.0.100 mode 3
receive: at 17 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423579 del 0.000488 dsp 1.951633 jit 0.000488, age 0
transmit: at 21 192.168.0.41->192.168.0.100 mode 3
receive: at 21 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 3 off 638.423191 del 0.000488 dsp 0.952649 jit 0.000488, age 0
transmit: at 25 192.168.0.41->192.168.0.100 mode 3
receive: at 25 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 4 off 638.423803 del 0.000488 dsp 0.453159 jit 0.000488, age 0
transmit: at 26 192.168.0.41->192.168.0.100 mode 3
receive: at 26 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 5 off 638.423956 del 0.000488 dsp 0.203394 jit 0.000508, age 0
transmit: at 27 192.168.0.41->192.168.0.100 mode 3
receive: at 27 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 5 off 638.423109 del 0.000488 dsp 0.078511 jit 0.000597, age 0
transmit: at 28 192.168.0.41->192.168.0.100 mode 3
receive: at 28 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 5 off 638.423262 del 0.000488 dsp 0.016069 jit 0.000488, age 0
auth_agekeys: at 60 keys 1 expired 0
transmit: at 93 192.168.0.41->192.168.0.100 mode 3
receive: at 93 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423209 del 0.000488 dsp 0.016543 jit 0.000488, age 0
auth_agekeys: at 120 keys 1 expired 0
transmit: at 158 192.168.0.41->192.168.0.100 mode 3
receive: at 158 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423155 del 0.000488 dsp 0.016778 jit 0.000488, age 0
auth_agekeys: at 180 keys 1 expired 0
transmit: at 224 192.168.0.41->192.168.0.100 mode 3
receive: at 224 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423255 del 0.000488 dsp 0.016901 jit 0.000488, age 0
auth_agekeys: at 240 keys 1 expired 0
transmit: at 290 192.168.0.41->192.168.0.100 mode 3
receive: at 290 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423355 del 0.000488 dsp 0.016961 jit 0.000488, age 0
auth_agekeys: at 300 keys 1 expired 0
transmit: at 356 192.168.0.41->192.168.0.100 mode 3
receive: at 356 192.168.0.41<-192.168.0.100 mode 4 code 1
clock_filter: n 2 off 638.423454 del 0.000488 dsp 0.016989 jit 0.000488, age 0

…

2

Im not quite sure if this is the problem, but we had once trouble synchronizing because the difference between the two workstations was to big.
Also i am not really familiar with the ntpd on QNX, after “synchronizing” manually via date up to 1-2 sec. it suddenly worked for us.

3

Are you using the “ntpd” command to synchronize?

As long as I know, the “ntpd” command is used to make your own machine behave as a NTP server.

If you want to synchronize with a remote NTP server just use "ntpdate ". Maybe you need some attempts depending on the
server, but it usually works fine.

4

Ubuntu comes with ntpdate as standard, and will run it once at boot time to set up your time according to Ubuntu’s NTP server. However, a server’s clock is likely to drift considerably between reboots, so it makes sense to correct the time occasionally. The easiest way to do this is to get cron to run ntpdate every day. With your favourite editor, as root, create a file /etc/cron.daily/ntpdate containing: ntpdate is a bit of a blunt instrument - it can only adjust the time once a day, in one big correction. The ntp daemon ntpd is far more subtle. It calculates the drift of your system clock and continuously adjusts it, so there are no large corrections that could lead to inconsistent logs for instance. The cost is a little processing power and memory, but for a modern server this is negligible.

5

I am not sure about how to synchronize the local time with Windows server but we use the “ntpd” command is used to make your own machine behave as a NTP server. So I think you are using a wrong command to do synchronize. Please correct it.