all servers stuck in INIT after reboot
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ntp (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Since I updated to 18.04.1 (ntp version 1:4.2.8p10+
$ ntpq -c peers
Thu Nov 1 06:33:19 EDT 2018
remote refid st t when poll reach delay offset jitter
=======
otc2.psu.edu .INIT. 16 u - 64 0 0.000 0.000 0.000
ntp-2.vt.edu .INIT. 16 u - 64 0 0.000 0.000 0.000
dns3.cit.cornel .INIT. 16 u - 64 0 0.000 0.000 0.000
This happens after every reboot. I have to restart the ntp service, then it runs normally again.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ntp 1:4.2.8p10+
ProcVersionSign
Uname: Linux 4.15.0-38-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 1 18:23:58 2018
InstallationDate: Installed on 2015-05-01 (1280 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
NtpStatus:
remote refid st t when poll reach delay offset jitter
======
+otc2.psu.edu 146.186.222.4 3 u 344 137m 375 31.612 0.222 1.043
*ntp-2.vt.edu 198.82.247.164 2 u 89m 137m 377 14.930 1.267 2.263
+dns3.cit.cornel 146.186.222.14 2 u 2032 137m 377 23.562 2.050 1.578
SourcePackage: ntp
UpgradeStatus: Upgraded to bionic on 2018-09-27 (35 days ago)
modified.
modified.
mtime.conffile.
mtime.conffile.
| Andrew Schulman (z-ubuntuone-andrex) wrote | #1 |
| Andrew Schulman (z-ubuntuone-andrex) wrote | #2 |
| Christian Ehrhardt (paelzer) wrote | #3 |
| Andrew Schulman (andrex) wrote | #4 |
OK, looking in /var/log/syslog, I see these entries from this morning's boot:
Nov 1 06:27:47 helium ntpd[1212]: ntpd 4.2.8p10@1.3728-o (1): Starting
Nov 1 06:27:47 helium ntpd[1212]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -4g -u 125:135
Nov 1 06:27:47 helium ntpd[1243]: proto: precision = 0.042 usec (-24)
Nov 1 06:27:47 helium ntpd[1243]: restrict: ignoring line 11, address/host 'louie.udel.edu' unusable.
Nov 1 06:27:47 helium ntpd[1243]: restrict: ignoring line 12, address/host 'clock.psu.edu' unusable.
Nov 1 06:27:47 helium ntpd[1243]: restrict: ignoring line 13, address/host 'ntp-2.vt.edu' unusable.
Nov 1 06:27:47 helium ntpd[1243]: restrict: ignoring line 14, address/host 'ntp0.cornell.edu' unusable.
Nov 1 06:27:47 helium ntpd[1243]: Listen and drop on 0 v4wildcard 0.0.0.0:123
Nov 1 06:27:47 helium ntpd[1243]: Listen normally on 1 lo 127.0.0.1:123
Nov 1 06:27:47 helium ntpd[1243]: Listening on routing socket on fd #18 for interface updates
Nov 1 06:27:52 helium ntpd[1243]: Listen normally on 2 eth0 192.168.1.2:123
Nov 1 06:27:52 helium ntpd[1243]: new interface(s) found: waking up resolver
Nov 1 06:33:40 helium ntpd[1243]: ntpd exiting on signal 15 (Terminated)
Nov 1 06:33:40 helium ntpd[1243]: 128.118.25.3 local addr 192.168.1.2 -> <null>
Nov 1 06:33:40 helium ntpd[1243]: 198.82.247.71 local addr 192.168.1.2 -> <null>
Nov 1 06:33:40 helium ntpd[1243]: 132.236.56.250 local addr 192.168.1.2 -> <null>
Nov 1 06:33:40 helium ntpd[3473]: ntpd 4.2.8p10@1.3728-o (1): Starting
Nov 1 06:33:40 helium ntpd[3473]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -4g -u 125:135
Nov 1 06:33:40 helium ntpd[3476]: proto: precision = 0.058 usec (-24)
Nov 1 06:33:40 helium ntpd[3476]: Listen and drop on 0 v4wildcard 0.0.0.0:123
Nov 1 06:33:40 helium ntpd[3476]: Listen normally on 1 lo 127.0.0.1:123
Nov 1 06:33:40 helium ntpd[3476]: Listen normally on 2 eth0 192.168.1.2:123
Nov 1 06:33:40 helium ntpd[3476]: Listening on routing socket on fd #19 for interface updates
So ntpd is at first ignoring all of the 'restrict' commands because the hostnames are 'unusable'. Why would that be? Is ntpd trying to start before the external network interface is up?