Bug#596487: [pkg-ntp-maintainers] Bug#596487: ntp: initscript should depend on $named
On Mon, Sep 13, 2010 at 10:34:57AM +1200, Francois Marier wrote: On 2010-09-12 at 23:40:08, Kurt Roeckx wrote: The other 2 common problem are: - Having libnss-mdns installed (#561622) Ah, it might be that one. I'll try removing it. Thanks for the pointer. In any case, do you think that ntp should depend on named though? I would assume that most people are using hostnames for their ntp servers and not IP addresses, but I do see that it's possible to run ntp and not rely on DNS. In which case the downside of that extra dependency would be that ntp gets started a bit later than necessary. Not everybody runs named, so we can't depend on it. I think there is also a way to say start it before us if it's available. But ntp can perfectly start without the nameserver working. You might not have a network connection at the time you boot. ntpd will start a slave process to do the resolving in that case, and so can resolv it later. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596487: [pkg-ntp-maintainers] Bug#596487: ntp: initscript should depend on $named
tags 596487 - patch thanks On Sun, Sep 12, 2010 at 10:33:33AM +1200, Francois Marier wrote: Package: ntp Version: 1:4.2.6.p2+dfsg-1 Severity: normal Tags: patch The initscript for ntp should add a dependency on $named because it fails to start when resolv.conf is set to 127.0.0.1 and the local dns server is not yet running. There are a few cases that might cause you problems. The most likely is a config error. Please check that you have the following 2 lines in your config file: restrict 127.0.0.1 restrict ::1 You most likely have a restrict 127.0.0.1 nomodify Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596487: [pkg-ntp-maintainers] Bug#596487: ntp: initscript should depend on $named
On 2010-09-12 at 22:14:37, Kurt Roeckx wrote: There are a few cases that might cause you problems. The most likely is a config error. Please check that you have the following 2 lines in your config file: restrict 127.0.0.1 restrict ::1 You most likely have a restrict 127.0.0.1 nomodify This is what I've got in my /etc/ntp.conf: $ grep restrict /etc/ntp.conf # Note that restrict applies to both servers and clients, so a configuration restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery restrict 127.0.0.1 restrict ::1 #restrict 192.168.123.0 mask 255.255.255.0 notrust This is the error message I see in my logs: ntpdate[1547]: name server cannot be used, reason: Temporary failure in name resolution ntpd[1595]: signal_no_reset: signal 17 had flags 400 Cheers, Francois -- Francois Marier identi.ca/fmarier http://feeding.cloud.geek.nz twitter.com/fmarier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596487: [pkg-ntp-maintainers] Bug#596487: ntp: initscript should depend on $named
On 2010-09-12 at 23:40:08, Kurt Roeckx wrote: The other 2 common problem are: - Having libnss-mdns installed (#561622) Ah, it might be that one. I'll try removing it. Thanks for the pointer. In any case, do you think that ntp should depend on named though? I would assume that most people are using hostnames for their ntp servers and not IP addresses, but I do see that it's possible to run ntp and not rely on DNS. In which case the downside of that extra dependency would be that ntp gets started a bit later than necessary. Cheers, Francois -- Francois Marier identi.ca/fmarier http://feeding.cloud.geek.nz twitter.com/fmarier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
