[I'm putting this as a comment to bug 276150 because it seems to
me to be the same symptoms: viz, crash on startup with certain time
servers.]
ntpd crashes on startup with a segmentation fault. This seems to be
reproducible for me. Here's a backtrace from gdb (I built ntpd from
the source package); it seems to reliably crash in the same place:
(gdb) run -n
Starting program: /usr/local/src/ntp-4.2.0a+stable/build-simple/ntpd/ntpd -n
Program received signal SIGSEGV, Segmentation fault.
sendpkt (dest=0x807b1c0, inter=0x0, ttl=0, pkt=0x807b1c0, len=134721984) at
../../ntpd/ntp_io.c:1413
1413 switch (inter->sin.ss_family) {
(gdb) bt
#0 sendpkt (dest=0x807b1c0, inter=0x0, ttl=0, pkt=0x807b1c0, len=134721984) at
../../ntpd/ntp_io.c:1413
#1 0x08061d44 in peer_xmit (peer=0x807b1b8) at ../../ntpd/ntp_proto.c:2418
#2 0x0805e279 in transmit (peer=0x807b1b8) at ../../ntpd/ntp_proto.c:301
#3 0x080691c8 in timer () at ../../ntpd/ntp_timer.c:289
#4 0x08051777 in ntpdmain (argc=0, argv=0xbfefceb0) at ../../ntpd/ntpd.c:1079
#5 0x0805138b in main (argc=134721984, argv=0x807b1c0) at ../../ntpd/ntpd.c:239
Here's my ntp.conf:
===begin===
# NTP configuration file (ntp.conf)
server time.aaisp.net
# Miscellaneous stuff
logfile /var/log/xntpd
#precision -18 # clock reading precision (usec)
driftfile /etc/ntp.drift # path for drift file
statsdir /var/log/ntpstats/ # directory for statistics files
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
# Authentication stuff
#keys /usr/local/bin/ntp.keys # path for keys file
#trustedkey 1 2 3 4 14 15 # define trusted keys
#requestkey 15 # key (7) for accessing server variables
#controlkey 15 # key (6) for accessing server variables
#authdelay 0.000072 # authentication delay (SPARC4c/65 SS1+ DES)
#authdelay 0.000159 # authentication delay (SPARC4c/65 SS1+ MD5)
===endit===
If I change the server to 'pool.ntp.org' then ntp works fine.
NB: I am not running exec-shield -- the remarks in this bug about that
are in my opinion a different problem (which should probably have its
own bug report).
-- PMM
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
