Done:
"Matthias Urlichs" <[email protected]>
Bug is archived. No further changes may be made.
Toggle useless messages
Report forwarded
to
[email protected], Bdale Garbee <[email protected]>
:
Bug#117276
; Package
ntp
.
(
full text
,
mbox
,
link
).
Acknowledgement sent
to
"Germane" <[email protected]>
:
New Bug report received and forwarded. Copy sent to
Bdale Garbee <[email protected]>
.
(
full text
,
mbox
,
link
).
Message #5
received at [email protected] (
full text
,
mbox
,
reply
):
Package: ntp
Version: 1:4.1.0-3
Since i upgradet my ntpd i got that nice error. its flooding my syslog. i
use a dsl connection to the internet.
after reconnection to the internet i get this errors. when i restart ntp
after connection to the internet all seams ok.
here part of my logfile
Oct 27 12:01:56 loki ntpd[12346]: ntpd 4.1.0 Fri Sep 28 00:50:30 PDT 2001
Oct 27 12:01:56 loki ntpd[12346]: signal_no_reset: signal 13 had flags
4000000
Oct 27 12:01:56 loki ntpd[12346]: precision = 17 usec
Oct 27 12:01:56 loki ntpd[12346]: kernel time discipline status 0040
Oct 27 12:01:56 loki ntpd[12346]: frequency initialized 18.766 from
/var/lib/ntp/ntp.drift
Oct 27 12:01:56 loki ntpd[12347]: signal_no_reset: signal 17 had flags
4000000
<- here is all ok ->
Oct 27 12:55:09 loki pppd[23864]: Hangup (SIGHUP)
Oct 27 12:55:09 loki pppoe[11082]: Received signal 1.
Oct 27 12:55:09 loki pppoe[11082]: Sent PADT
Oct 27 12:55:09 loki pppd[23864]: Modem hangup
Oct 27 12:55:09 loki pppd[23864]: Connection terminated.
Oct 27 12:55:09 loki pppd[23864]: Connect time 409.7 minutes.
Oct 27 12:55:09 loki pppd[23864]: Sent 832246 bytes, received 8349556 bytes.
Oct 27 12:55:39 loki pppd[23864]: Serial connection established.
Oct 27 12:55:39 loki pppd[23864]: Using interface ppp0
Oct 27 12:55:39 loki pppd[23864]: Connect: ppp0 <--> /dev/pts/0
Oct 27 12:55:40 loki pppoe[12709]: PADS: Service-Name: ''
Oct 27 12:55:40 loki pppoe[12709]: PPP session is 5261
Oct 27 12:55:40 loki pppd[23864]: kernel does not support PPP filtering
Oct 27 12:55:42 loki ntpd[12346]: sendto(142.3.100.15): Invalid argument
Oct 27 12:55:43 loki pppd[23864]: Cannot determine ethernet address for
proxy ARP
Oct 27 12:55:43 loki pppd[23864]: local IP address 217.81.136.13
Oct 27 12:55:43 loki pppd[23864]: remote IP address 217.5.98.32
Oct 27 12:55:44 loki ntpd[12346]: sendto(129.132.2.21): Invalid argument
Oct 27 12:55:45 loki ntpd[12346]: sendto(194.95.250.36): Invalid argument
Oct 27 12:55:46 loki ntpd[12346]: sendto(130.159.196.118): Invalid argument
Oct 27 12:55:50 loki ntpd[12346]: sendto(131.188.3.36): Invalid argument
Oct 27 12:55:54 loki ntpd[12346]: sendto(204.152.184.72): Invalid argument
Oct 27 12:55:56 loki ntpd[12346]: sendto(134.214.100.6): Invalid argument
Oct 27 12:55:57 loki ntpd[12346]: sendto(193.204.114.231): Invalid argument
Oct 27 12:55:59 loki ntpd[12346]: sendto(128.118.46.3): Invalid argument
Oct 27 12:56:12 loki ntpd[12346]: sendto(130.149.17.21): Invalid argument
Oct 27 12:56:51 loki ntpd[12346]: sendto(193.67.79.202): Invalid argument
<-here i restarted ntp and all looks ok ->
Oct 27 12:57:02 loki ntpd[12346]: ntpd exiting on signal 15
Oct 27 12:57:04 loki ntpd[12776]: ntpd 4.1.0 Fri Sep 28 00:50:30 PDT 2001
Oct 27 12:57:04 loki ntpd[12776]: signal_no_reset: signal 13 had flags
4000000
Oct 27 12:57:04 loki ntpd[12776]: precision = 18 usec
Oct 27 12:57:04 loki ntpd[12776]: kernel time discipline status 0040
Oct 27 12:57:04 loki ntpd[12776]: frequency initialized 18.766 from
/var/lib/ntp/ntp.drift
Oct 27 12:57:04 loki ntpd[12777]: signal_no_reset: signal 17 had flags
4000000
Oct 27 13:00:20 loki ntpd[12776]: kernel time discipline status change 41
here my ntp.conf
# /etc/ntp.conf, configuration for xntpd
# ntpd will use syslog() if logfile is not defined
#logfile /var/log/ntpd
driftfile /var/lib/ntp/ntp.drift
statsdir /var/log/ntpstats/
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
#server
#stratum 1
server ntps1-0.cs.tu-berlin.de
server ptbtime2.ptb.de
server swisstime.ethz.ch
server time.ien.it
server clock.isc.org
server wwv.otc.psu.edu
server ntp1.fau.de
server ntp0.nl.net
#sreatum 2
server ntp.univ-lyon1.fr
server ntp.cs.strath.ac.uk
server timelord.uregina.ca
server time.alcanet.no
i think i can solv the problem with iputting ntp into /etc/ppp/ip-up.d and
/etc/ppp/ip-down.d but before upgrading all was ok.
greatings
Information forwarded to [email protected], Bdale Garbee <[email protected]>, [email protected]:
Bug#117276; Package ntp.
(full text, mbox, link).
Acknowledgement sent to [email protected] (Bdale Garbee):
Extra info received and forwarded to list. Copy sent to Bdale Garbee <[email protected]>, [email protected].
(full text, mbox, link).
Message #10 received at [email protected] (full text, mbox, reply):
It's not entirely clear to me that what you're seeing is really a bug in ntp.
You say your syslog is being "flooded". What do you mean? The ntp code goes
to some pains to cache information about hosts that aren't reachable, so that
you only get one complaint per host per loss of connectivity. If you're seeing
more in your logs than that, it might be a bug in that caching code... but if
you're just complaining about seeing the Invalid argument errors once per
host per each time you lose connectivity, that's not a bug...
Bdale
Information forwarded to [email protected], Bdale Garbee <[email protected]>, [email protected]:
Bug#117276; Package ntp.
(full text, mbox, link).
Acknowledgement sent to Kevin Turner <[email protected]>:
Extra info received and forwarded to list. Copy sent to Bdale Garbee <[email protected]>, [email protected].
(full text, mbox, link).
Message #15 received at [email protected] (full text, mbox, reply):
I'm on an intermittent dial-up connection myself, and I'm experiencing
the same thing. My primary problem isn't that it "floods" syslog, but
that once an address is reported as an "invalid argument", ntp doesn't
contact that server forever after. It used to be (probably more than
173 days ago, or whenever this bug was filed) that if my link went down
and then back up a while later, packets would just start going through
again and ntp would recover just fine. Now, even when the link is up
and working fine, "ntpq -p" shows that these hosts still have a polling
interval of, say, 128 seconds, but the "when" says they haven't been
contacted in hours. Until I restart ntpd, but that's no fun.
Merged 117276 145629.
Request was from Bdale Garbee <[email protected]>
to [email protected].
(full text, mbox, link).
Information forwarded to [email protected], Debian NTP Team <[email protected]>:
Bug#117276; Package ntp.
(full text, mbox, link).
Acknowledgement sent to Mattias Urlichs <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian NTP Team <[email protected]>.
(full text, mbox, link).
Message #22 received at [email protected] (full text, mbox, reply):
it turns out that the code responsible for that (ntp_io.c) isn't
turnoffable either at configuration or deployment time and doesn't seem
to time out its entries either.
As a stopgap measure, I'll add a configuration option.
Matthias Urlichs | noris network AG | http://smurf.noris.de/
Tags added: wontfix
Request was from Matthias Urlichs <[email protected]>
to [email protected].
(full text, mbox, link).
Disconnected #117276 from all other report(s).
Request was from Matthias Urlichs <[email protected]>
to [email protected].
(full text, mbox, link).
Tags added: fixed-in-experimental
Request was from Matthias Urlichs <[email protected]>
to [email protected].
(full text, mbox, link).
Reply sent to "Matthias Urlichs" <[email protected]>:
You have taken responsibility.
(full text, mbox, link).
Notification sent to "Germane" <[email protected]>:
Bug acknowledged by developer.
(full text, mbox, link).
Message #33 received at [email protected] (full text, mbox, reply):
This bug was tagged closed-in-experimental.
I'm now really closing it, as 4.2.0a-1 has been uploaded to Unstable.
Matthias Urlichs
Send a report that this bug log contains spam.
Debian bug tracking system administrator <[email protected]>.
Last modified:
Sat Feb 10 20:55:23 2024;
Machine Name:
bembo
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
