This is a mystery!
I tried using 69.17.7.16 as the only NTP server on my Debian box. I get
basically the same pathology. My ntpd seems to poll every 1-3 seconds,
and has been for several minutes. Does anyone have a non-Debian ntpd
install they'd be willing to try this on? At this point I'm willing to
bet it's a bug in generic ntpd and the responses this server is sending
out, but it'd be nice to verify that.
The only thing I see funny in Anthony's packet trace is the Peer Polling
Interval: 0 in the response from the server. That's clearly not the most
useful response, but ntpd should be smart enough to cope with it. Maybe
it's a simple bug in handling insane input?
It'd be nice to know what that server is doing. 69.17.7.16 is
badforyou.net, and it seems easy enough to contact that system's owner.
But I'm holding off a bit until we figure out what we can on our own.
Here's my ntp.conf that's just talking to 69.17.7.16. I don't think I
did any weird configuration from the Debian default. When I use
different servers I get normal NTP polling behaviour, it's only this one
server that gives me fits.
# /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 69.17.7.16
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
