The global pool is certainly working and its DNS servers are resolving
correctly:
$ host 0.ubuntu.pool.ntp.org
0.ubuntu.pool.ntp.org has address 108.59.2.24
0.ubuntu.pool.ntp.org has address 129.250.35.250
0.ubuntu.pool.ntp.org has address 52.0.56.137
0.ubuntu.pool.ntp.org has address 72.14.179.135
Directly after the last occurrence of the resolver failure, your ntpd
resolved a large list of pool servers, including 5 within the same
second as the error message.
Without knowing your configuration, I'd guess this was a network-
manager-initiated restart, and your resolver setup simply wasn't
finished by the time ntpd was asking for DNS names. If you're using the
default ntp configuration (or similar to it), this will not be a
problem, because ntpd will retry the DNS lookups.
** Changed in: ntp (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1651707
Title:
ntpd[1243]: error resolving pool 0.ubuntu.pool.ntp.org: Name or
service not known (-2)
Status in ntp package in Ubuntu:
Invalid
Bug description:
This is logged into journalctl:
ntpd[1243]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not
known (-2)
in fact, all of the x.ubuntu.pool servers fail
oem@u64:~$ ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
0.ubuntu.pool.n .POOL. 16 p - 64 0 0.000 0.000 0.000
1.ubuntu.pool.n .POOL. 16 p - 64 0 0.000 0.000 0.000
2.ubuntu.pool.n .POOL. 16 p - 64 0 0.000 0.000 0.000
3.ubuntu.pool.n .POOL. 16 p - 64 0 0.000 0.000 0.000
ntp.ubuntu.com .POOL. 16 p - 64 0 0.000 0.000 0.000
+mica.ad-notam.n 131.188.3.221 2 u 112 128 377 23.004 1.092 1.416
+server1.webster 75.12.230.181 2 u 64 128 377 22.971 1.149 0.276
-postier.polylan 131.188.3.223 2 u 37 128 377 20.909 0.914 0.852
*www.mindstudios 145.238.203.14 2 u 120 128 377 17.638 1.377 0.293
+server2.bertold 131.211.8.244 2 u 156 128 372 27.835 1.206 1.417
oem@u64:~$ journalctl | grep ntpd
Dec 21 10:04:01 u64 audit[798]: AVC apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/sbin/ntpd" pid=798
comm="apparmor_parser"
Dec 21 10:04:20 u64 ntp[1187]: * Starting NTP server ntpd
Dec 21 10:04:20 u64 ntpd[1212]: ntpd [email protected] Fri Dec 16 07:29:13 UTC
2016 (1): Starting
Dec 21 10:04:20 u64 ntpd[1212]: Command line: /usr/sbin/ntpd -p
/var/run/ntpd.pid -g -u 118:129
Dec 21 10:04:20 u64 ntpd[1243]: proto: precision = 0.068 usec (-24)
Dec 21 10:04:20 u64 ntpd[1243]: Listen and drop on 0 v6wildcard [::]:123
Dec 21 10:04:20 u64 ntpd[1243]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Dec 21 10:04:20 u64 ntpd[1243]: Listen normally on 2 lo 127.0.0.1:123
Dec 21 10:04:20 u64 ntpd[1243]: Listen normally on 3 eth1 192.168.1.3:123
Dec 21 10:04:20 u64 ntpd[1243]: Listen normally on 4 lo [::1]:123
Dec 21 10:04:20 u64 ntpd[1243]: Listen normally on 5 eth1
[fe80::1d0d:5570:10c1:7a7c%3]:123
Dec 21 10:04:20 u64 ntpd[1243]: Listening on routing socket on fd #22 for
interface updates
Dec 21 10:04:52 u64 ntpd[1243]: error resolving pool 0.ubuntu.pool.ntp.org:
Name or service not known (-2)
Dec 21 10:05:17 u64 ntpd[1243]: error resolving pool 1.ubuntu.pool.ntp.org:
Name or service not known (-2)
Dec 21 10:05:17 u64 ntpd[1243]: Soliciting pool server 94.23.220.217
Dec 21 10:05:17 u64 ntpd[1243]: Soliciting pool server 37.59.27.22
Dec 21 10:05:17 u64 ntpd[1243]: Soliciting pool server 91.189.91.157
Dec 21 10:05:17 u64 ntpd[1243]: Soliciting pool server 178.33.111.47
Dec 21 10:05:17 u64 ntpd[1243]: Soliciting pool server 37.187.2.84
Dec 21 10:05:18 u64 ntpd[1243]: Soliciting pool server 94.23.0.110
Dec 21 10:05:18 u64 ntpd[1243]: Soliciting pool server 194.177.34.115
Dec 21 10:05:19 u64 ntpd[1243]: Soliciting pool server 5.196.160.139
Dec 21 10:05:19 u64 ntpd[1243]: Soliciting pool server 195.154.79.192
Dec 21 10:05:26 u64 ntpd[1243]: Soliciting pool server 62.210.28.176
Dec 21 10:05:27 u64 ntpd[1243]: Soliciting pool server 195.154.71.176
Dec 21 10:05:27 u64 ntpd[1243]: Soliciting pool server 163.172.228.190
Dec 21 10:25:32 u64 ntpd[1243]: 178.33.111.47 local addr 192.168.1.3 -> <null>
Dec 21 10:28:09 u64 ntpd[1243]: 62.210.28.176 local addr 192.168.1.3 -> <null>
Dec 21 10:28:53 u64 ntpd[1243]: 194.177.34.115 local addr 192.168.1.3 ->
<null>
Dec 21 10:36:46 u64 ntpd[1243]: 94.23.220.217 local addr 192.168.1.3 -> <null>
Dec 21 10:36:47 u64 ntpd[1243]: 5.196.160.139 local addr 192.168.1.3 -> <null>
Dec 21 10:36:53 u64 ntpd[1243]: 195.154.79.192 local addr 192.168.1.3 ->
<null>
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ntp 1:4.2.8p9+dfsg-2ubuntu1
ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
Uname: Linux 4.9.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 21 11:40:35 2016
SourcePackage: ntp
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1651707/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
