[pkg-ntp-maintainers] Bug#833136: Bug#461461: This bug is still present -- change to systemd did not fix it!

[Kurt Roeckx]

On Mon, Aug 01, 2016 at 04:23:54AM -0700, Rick Thomas wrote:
> > May 18 03:52:23 ultimate ntpd[381]: ntpd 4.2.8p7 at 1.3265-o Sat Apr 30 11:18:37 UTC 2016 (1): Starting
> > May 18 03:52:23 ultimate ntpd[381]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 112:120
> > May 18 03:52:23 ultimate ntp[315]: Starting NTP server: ntpd.
> > May 18 03:52:23 ultimate systemd[1]: Started LSB: Start NTP daemon.
> > May 18 03:52:23 ultimate ntpd[399]: proto: precision = 2.410 usec (-19)
> > May 18 03:52:23 ultimate ntpd[399]: Listen and drop on 0 v6wildcard [::]:123
> > May 18 03:52:23 ultimate ntpd[399]: Listen and drop on 1 v4wildcard 0.0.0.0:123
> > May 18 03:52:23 ultimate ntpd[399]: Listen normally on 2 lo 127.0.0.1:123
> > May 18 03:52:23 ultimate ntpd[399]: Listen normally on 3 lo [::1]:123
> > May 18 03:52:23 ultimate ntpd[399]: bind(20) AF_INET6 fe80::f2ad:4eff:fe00:613c%2#123 flags 0x11 failed: Cannot assign requested
> > May 18 03:52:23 ultimate ntpd[399]: unable to create socket on eth0 (4) for fe80::f2ad:4eff:fe00:613c%2#123
> > May 18 03:52:23 ultimate ntpd[399]: failed to init interface for address fe80::f2ad:4eff:fe00:613c%2
> > May 18 03:52:23 ultimate ntpd[399]: Listening on routing socket on fd #20 for interface updates
> > May 18 03:52:23 ultimate dbus[320]: [system] Successfully activated service 'org.freedesktop.ColorManager'
> > May 18 03:52:23 ultimate systemd[1]: Started Manage, Install and Generate Color Profiles.
> > May 18 03:52:24 ultimate ntpd[399]: error resolving pool pool.rcthomas.org: Temporary failure in name resolution (-3)
[...]
> > May 18 03:52:25 ultimate ntpd[399]: error resolving pool us.pool.ntp.org: Temporary failure in name resolution (-3)
[...]
> > May 18 03:52:26 ultimate dhclient[247]: bound to 192.168.3.4 -- renewal in 3521 seconds.
> > May 18 03:52:26 ultimate sh[234]: bound to 192.168.3.4 -- renewal in 3521 seconds.
> > May 18 03:52:26 ultimate ntpd[399]: Soliciting pool server 2001:4978:1:400:202:b3ff:feb4:59cb
[...]
> > May 18 03:52:28 ultimate ntpd[399]: Listen normally on 5 eth0 192.168.3.4:123
> > May 18 03:52:28 ultimate ntpd[399]: Listen normally on 6 eth0 [2001:4978:2d2:1:f2ad:4eff:fe00:613c]:123
> > May 18 03:52:28 ultimate ntpd[399]: Listen normally on 7 eth0 [fe80::f2ad:4eff:fe00:613c%2]:123
[...]
> > May 18 03:52:40 ultimate ntpd[399]: Soliciting pool server 192.168.3.111
> > May 18 03:52:41 ultimate ntpd[399]: Soliciting pool server 192.168.3.207
[...]
> > May 18 03:53:29 ultimate ntpd[399]: Soliciting pool server 199.199.208.25
> > May 18 03:53:30 ultimate ntpd[399]: Soliciting pool server 129.250.35.250
> > May 18 03:53:31 ultimate ntpd[399]: Soliciting pool server 50.116.55.65
> 
> The DHCPACK that assigns the IP address to the interface occurs during the middle of ntpd's startup, so two of three pool statements get failed DNS.  The third one succeeds, so ntpd gets some servers, but not all the servers it's configured for.
> 

It looked to me like it was working.  It says that it was a
temporary failure, and as far as I know it will retry it in that
case.

Also not that ntpd has some weird logic of how many servers it's
using when using "pool", and it's probably not using it from all
the pools.  You can set the maximum higher using "tos maxclock
XX".

I was under the impression that when using "server" and getting
a permanent DNS error it would give up on it but that with a
temporary error it will retry.  And that with pool it keeps
retrying, but I'm not sure about that.

Anyway, that it's a temporary or permanent error depends on what
glibc returns, and I've been trying to get that fixed for years.


Kurt