Ubuntu
ntp package

  1. Bug #114505
  2. Comment #3

Comment 3 for bug 114505

Revision history for this message
Lethe (nick-ukfsn) wrote : Re: ntp is being brought up before network is ready, causing ntp to not resolve any ip or host names and it appears ntp does not recover

Yes, I can replicate this exactly - same issue - please refer:

https://answers.launchpad.net/ubuntu/+question/13064

It seems DHCP is the issue. Here is more info from my system logs:

Sep 9 13:00:58 palantir avahi-daemon[5314]: No service found in /etc/avahi/services.
Sep 9 13:00:58 palantir avahi-daemon[5314]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.30.
Sep 9 13:00:58 palantir avahi-daemon[5314]: New relevant interface eth0.IPv4 for mDNS.
Sep 9 13:00:58 palantir avahi-daemon[5314]: Network interface enumeration completed.
Sep 9 13:00:58 palantir avahi-daemon[5314]: Registering new address record for fe80::21c:23ff:fe92:b82e on eth0.*.
Sep 9 13:00:58 palantir avahi-daemon[5314]: Registering new address record for 192.168.1.30 on eth0.IPv4.
Sep 9 13:00:58 palantir avahi-daemon[5314]: Registering HINFO record with values 'I686'/'LINUX'.
Sep 9 13:00:58 palantir NetworkManager: <information>^Inm_device_init(): device's worker thread started, continuing.
Sep 9 13:00:58 palantir NetworkManager: <information>^INow managing wired Ethernet (802.3) device 'eth0'.
Sep 9 13:00:58 palantir NetworkManager: <information>^IDeactivating device eth0.
Sep 9 13:00:58 palantir avahi-daemon[5314]: Withdrawing address record for 192.168.1.30 on eth0.
Sep 9 13:00:58 palantir avahi-daemon[5314]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.30.
Sep 9 13:00:58 palantir avahi-daemon[5314]: Interface eth0.IPv4 no longer relevant for mDNS.
Sep 9 13:00:58 palantir avahi-daemon[5314]: Withdrawing address record for fe80::21c:23ff:fe92:b82e on eth0.
Sep 9 13:00:58 palantir NetworkManager: <information>^IWill activate wired connection 'eth0' because it now has a link.

...
...

and then later:

Sep 9 13:01:00 palantir ntpd[5676]: ntpd 4.2.2p4@1.1585-o Wed Mar 7 20:43:30 UTC 2007 (1)
Sep 9 13:01:00 palantir ntpd[5677]: precision = 1.000 usec
Sep 9 13:01:00 palantir ntpd[5677]: Listening on interface wildcard, 0.0.0.0#123 Disabled
Sep 9 13:01:00 palantir ntpd[5677]: Listening on interface wildcard, ::#123 Disabled
Sep 9 13:01:00 palantir ntpd[5677]: Listening on interface lo, ::1#123 Enabled
Sep 9 13:01:00 palantir ntpd[5677]: Listening on interface lo, 127.0.0.1#123 Enabled
Sep 9 13:01:00 palantir ntpd[5677]: kernel time sync status 0040
Sep 9 13:01:00 palantir ntpd[5677]: frequency initialized 5.764 PPM from /var/lib/ntp/ntp.drift
Sep 9 13:01:00 palantir NetworkManager: <information>^IDHCP daemon state is now 1 (starting) for interface eth0
Sep 9 13:01:01 palantir ntpd[5677]: sendto(192.168.1.20) (fd=16): Network is unreachable
Sep 9 13:01:02 palantir dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Sep 9 13:01:02 palantir dhclient: DHCPACK from 192.168.1.23
Sep 9 13:01:02 palantir avahi-daemon[5314]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.30.
Sep 9 13:01:02 palantir avahi-daemon[5314]: New relevant interface eth0.IPv4 for mDNS.
Sep 9 13:01:02 palantir avahi-daemon[5314]: Registering new address record for 192.168.1.30 on eth0.IPv4.
Sep 9 13:01:02 palantir NetworkManager: <information>^IDHCP daemon state is now 4 (reboot) for interface eth0
Sep 9 13:01:02 palantir NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Sep 9 13:01:02 palantir NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) started...
Sep 9 13:01:02 palantir dhclient: bound to 192.168.1.30 -- renewal in 17345 seconds.
Sep 9 13:01:02 palantir NetworkManager: <information>^IRetrieved the following IP4 configuration from the DHCP daemon:
Sep 9 13:01:02 palantir NetworkManager: <information>^I address 192.168.1.30
Sep 9 13:01:02 palantir NetworkManager: <information>^I netmask 255.255.255.0
Sep 9 13:01:02 palantir NetworkManager: <information>^I broadcast 192.168.1.255
Sep 9 13:01:02 palantir NetworkManager: <information>^I gateway 192.168.1.20
Sep 9 13:01:02 palantir NetworkManager: <information>^I nameserver 192.168.1.20
Sep 9 13:01:02 palantir NetworkManager: <information>^I domain name 'linicks.net'

So it seems DHCP goes a bit AWOL.

BTW, using a static IP works perfectly fine.

Nick