[ntp:questions] Re: ACTS - too many recvbufs allocated (40) (Correct the Version of ntp-dev)

David L. Mills mills at udel.edu
Fri Feb 4 17:16:20 UTC 2005


Giuseppe,

I've heard mixed reports. In the recent integration of USNO/NIST/PTB 
driver, the USNO and NIST formats were rigorously verified, but I could 
not verify the PTB format. I have heard at least one report that it 
works, then I hear your report that it doesn't. This is not hard to fix, 
but I can't do that from here. Someone needs to look at the sscanf call 
in the driver and compare with the PTB string actually received. The 
rcvbuf situation should have nothing to do with a possible format 
decoding bug.

Dave

Giuseppe wrote:

> I found a similar situation with the Italian telephone time code, that
> as far as I know use the same format of TDS.
> With the stable version of NTP (4.2.0) and the little changes in the
> setup string of the modem (&C0), ntpd works fine.
> But if I try the latest tarball of ntp-dev (ntpd 4.2.0a at 1.1318-o),
> ntpd die  with segmentation fault after the reception of the first
> string from the modem.
> I've tried also this newer version of NTP without ACTS refclock and
> with 3 stratum 1 peer: in this case it works fine.
> 
> Giuseppe Vizio
> 
> 
> -----------------------------------------------------------
> 
> My host is a PC - Pentium III, with Linux 2.4.18. 
> This is the output of gdb:
> 
> gdb /usr/sbin/ntpd
> GNU gdb 2002-04-01-cvs
> ...
> (gdb) run -d
> Starting program: /usr/sbin/ntpd -d
> ntpd 4.2.0a at 1.1318-o Fri Feb  4 14:03:26 UTC 2005 (3)
> addto_syslog: signal_no_reset: signal 13 had flags 4000000
> addto_syslog: precision = 1.000 usec
> create_sockets(123)
> addto_syslog: no IPv6 interfaces found
> bind() fd 8, family 2, port 123, addr 0.0.0.0, flags=8
> Added addr 0.0.0.0 to list of addresses
> addto_syslog: Listening on interface wildcard, 0.0.0.0#123
> bind() fd 9, family 2, port 123, addr 127.0.0.1, flags=0
> Added addr 127.0.0.1 to list of addresses
> addto_syslog: Listening on interface lo, 127.0.0.1#123
> bind() fd 10, family 2, port 123, addr xxx.xxx.xxx.xxx, flags=8
> Added addr xxx.xxx.xxx.xxx to list of addresses
> addto_syslog: Listening on interface eth0, xxx.xxx.xxx.xxx#123
> init_io: maxactivefd 11
> local_clock: time 0 base 0.000000 offset 0.000000 freq 0.000 state 0
> ntp_syslogmask = 0x00ffff00 (+clockall)
> ntp_syslogmask = 0x00fffff0 (+peerall)
> ntp_syslogmask = 0x00ffffff (+sysall)
> ntp_syslogmask = 0x0fffffff (+syncall)
> addto_syslog: frequency initialized -7.483 PPM from
> /var/lib/ntp/ntp.drift
> local_clock: time 0 base 0.000000 offset 0.000000 freq -7.483 state 1
> key_expire: at 0
> peer_clear: at 0 assoc ID 54508 refid INIT
> newpeer: 127.0.0.1->127.127.18.1 mode 3 vers 4 poll 6 10 flags 0x21
> 0x1 ttl 0 key 00000000
> key_expire: at 0
> addto_syslog: system event 'event_restart' (0x01) status 'sync_alarm,
> sync_unspec, 1 event, event_unspec' (0xc010)
> report_event: system event 'event_restart' (0x01) status 'sync_alarm,
> sync_unspec, 1 event, event_unspec' (0xc010)
> refclock_transmit: at 1 127.127.18.1
> auth_agekeys: at 1 keys 1 expired 0
> timer: refresh ts 0
> refclock_setup fd 12 modem status: 0x4166
> refclock_ioctl: fd 12 flags 0x24
> acts: setup ATB0&C0&D2E0L1M1Q0V1
> acts: (2 3) 2 OK
> filegen  2 3316518070 0 3316464000
> acts: dial 0 ATDT263
> acts: (3 36) 17 CONNECT 1200/NONE
> acts: (4 20) 1 *
> acts: (4 19) 78 2005-02-04 16:01:36 CET 
> 50503500000020050204150153405-5+00070      =32s     *
> 
> Program received signal SIGSEGV, Segmentation fault.
> socktoa (sock=0x20202028) at socktoa.c:38
> 38                      switch(sock->ss_family) {



More information about the questions mailing list