[Bug 114505] Re: ntp brought up before network is ready; fails not resolve any ip or host names; ntp does not recover

Imre Gergely gimre at narancs.net
Sat Jan 24 14:29:58 GMT 2009


I probably won't add anything new to this, but here it goes:

I've just installed Hardy for a mail/dns/webserver with a NTP server
also and I ran into this little 'bug'.

- machine boots, NTP is stopped and started when eth0 (statically configured) comes up
- down the line, NTP is again started with rc2.d/S23ntp (obviously nothing happens because it's already running)
- I log in, check ntpq -p, i get nothing ("No association ID's returned").

I have my own DNS server running on localhost, and I have
/etc/resolv.conf with

nameserver 127.0.0.1

a.k.a. I'm using my own nameserver, which isn't available at network
start, becase it starts later (but before S23).

So this is a server install with little to none network ups/downs,
nothing dynamic, nothing fancy, just the good old static network config,
and the fact that the nameserver used is 127.0.0.1.

I can see how one would try to do a good thing by (re)syncing the clock
whenever the network is (re)started, but doing that for _every single
network interface_ the machine has ?

If I happen to have 3-4 interfaces, NTP gets restarted that many times,
that's just silly. And what if I have eth1 for internal LAN and do an
ifdown/ifup eth1 (because say I changed the IP address, or whatever),
which has nothing to do with NTP ? It still gets restarted. It doesn't
seem the right thing to do IMHO.

-- 
ntp brought up before network is ready; fails not resolve any ip or host names; ntp does not recover
https://bugs.launchpad.net/bugs/114505
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.



More information about the Ubuntu-server-bugs mailing list