OK, looking in /var/log/syslog, I see these entries from this morning's boot:
Nov 1 06:27:47 helium ntpd[1212]: ntpd [email protected] (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 [email protected] (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? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801183 Title: all servers stuck in INIT after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1801183/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
