[ntp:questions] Re: NTP over multicast sat link with no return channel

Danny Mayer mayer at ntp.isc.org
Tue Apr 11 12:24:41 UTC 2006


juliansomers at googlemail.com wrote:
> I am not very worried about running the clients with 'disable auth' at
> the moment. (If someone other than us is able to send data over our
> space segment, then I have bigger problems than time keeping!).
> 
>> What version of ntp are you running?
> 4.2.0 at 1.1161-r with linux 2.6.11.12
> 
> Is there anything else, other than auth problems, which would cause my
> multicast data to not show up as an association on the client when I
> use ntpq -pn? I am pretty confident that the packets are arriving
> correctly.
> 
> Here is debug output
> 
> root # ntpd -ddd
> ntpd 4.2.0 at 1.1161-r Mon Dec 13 15:52:00 GMT 2004 (1)
> addto_syslog: ntpd 4.2.0 at 1.1161-r Mon Dec 13 15:52:00 GMT 2004 (1)
> addto_syslog: set_process_priority: Leave priority alone: priority_done
> is <2>
> addto_syslog: precision = 1.000 usec
> create_sockets(123)
> addto_syslog: no IPv6 interfaces found
> address_okay: listen Virtual: 1, IF name: eth0, Up Flag: 1
> address_okay: listen Virtual: 1, IF name: lo, Up Flag: 1
> address_okay: listen Virtual: 1, IF name: dvb0_0, Up Flag: 1
> address_okay: listen Virtual: 1, IF name: tun0, Up Flag: 1
> address_okay: listen Virtual: 1, IF name: ppp0, Up Flag: 1
> bind() fd 4, family 2, port 123, addr 0.0.0.0, flags=8
> flags for fd 4: 04002
> bind() fd 5, family 2, port 123, addr 192.168.1.1, flags=8
> flags for fd 5: 04002
> bind() fd 6, family 2, port 123, addr 127.0.0.1, flags=0
> flags for fd 6: 04002
> bind() fd 7, family 2, port 123, addr 192.168.238.238, flags=8
> flags for fd 7: 04002
> bind() fd 8, family 2, port 123, addr 1.2.3.4, flags=0
> flags for fd 8: 04002
> bind() fd 9, family 2, port 123, addr 192.168.16.43, flags=0
> flags for fd 9: 04002
> create_sockets: ninterfaces=6
> interface 0:  fd=4,  bfd=-1,  name=wildcard,  flags=0x8
>               sin=0.0.0.0  bcast=0.0.0.0,  mask=255.255.255.255
> interface 1:  fd=5,  bfd=-1,  name=eth0,  flags=0x9
>               sin=192.168.1.1  bcast=192.168.1.255,  mask=255.255.255.0
> interface 2:  fd=6,  bfd=-1,  name=lo,  flags=0x5
>               sin=127.0.0.1  mask=255.0.0.0
> interface 3:  fd=7,  bfd=-1,  name=dvb0_0,  flags=0x9
>               sin=192.168.238.238  bcast=192.168.238.255,
> mask=255.255.255.0
> interface 4:  fd=8,  bfd=-1,  name=tun0,  flags=0x3
>               sin=1.2.3.4  mask=255.255.255.255
> interface 5:  fd=9,  bfd=-1,  name=ppp0,  flags=0x3
>               sin=192.168.16.43  mask=255.255.255.255
> init_io: maxactivefd 9
> local_clock: at 0 state 0
> addto_syslog: frequency initialized 0.000 PPM from
> /var/lib/ntp/ntp.drift
> local_clock: at 0 state 1
> getnetnum given 127.0.0.1, got 127.0.0.1
> getnetnum given 229.1.1.8, got 229.1.1.8
> bind() fd 11, family 2, port 123, addr 229.1.1.8, flags=0
> flags for fd 11: 04002
> Added addr 229.1.1.8 to list of addresses
> io_multicast_add 229.1.1.8
> configuring filegen:
>         prefix: /var/log/ntpstats/
>         basename:       peerstats -> peerstats
>         type:   2 -> 2
>         flag: 1 -> 81
> authtrust: keyid 0000ffff life 1
> report_event: system event 'event_restart' (0x01) status 'sync_alarm,
> sync_unspec, 1 event, event_unspec' (0xc010)
> addto_syslog: select(): nfound=-1, error: Interrupted system call
> auth_agekeys: at 1 keys 1 expired 0
> timer: refresh ts 0
> addto_syslog: select(): nfound=-1, error: Interrupted system call
> addto_syslog: select(): nfound=-1, error: Interrupted system call
> 
> These addto_syslog errors occur once a second for as long as ntpd runs.
> Are they relevant? 
> 
> Thanks again, 
> 
> Julian

Please upgrade. That's a very old version. There have been lots of fixes
since then especially in the multicast area.

The select lines are not errors, they're just debug code.

Danny



More information about the questions mailing list