<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:lucida console,sans-serif;font-size:10pt"><div>To answer your questions:<br><br>/etc/resolv.conf looks like this when I boot up single-user:<br><br>domain local<br>search local<br>nameserver 192.168.1.1<br><br>Note that in single-user the network interfaces are up<br>and configured, and dhclient is running (but NetworkManager<br>is not running). (Is it possible to boot Debian without<br>networking?)<br><br>There is no nameserver running on the Debian machine, but<br>there is one (DNSMasq) in my router (192.168.1.1).<br><br>The hosts line of /etc/nsswitch.conf:<br><br>hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4<br><br>And some extra information: the servers lines from /etc/ntp.conf:<br><br>server 0.debian.pool.ntp.org iburst dynamic<br>server 1.debian.pool.ntp.org iburst dynamic<br>server 2.debian.pool.ntp.org iburst
dynamic<br>server 3.debian.pool.ntp.org iburst dynamic<br><br>Also note that I am using dhcp for network configuration.<br>The dhcp server is in my router (192.168.1.1).<br><br>---<br><br>First, I don't think that ntpd is getting a permanent error<br>from the router's nameserver: syslog indicates that the<br>network interface is down at the time, so the router is<br>unreachable.<br><br>Second, it seems that the 'dynamic' option in ntp.conf<br>should tell ntpd to keep trying to resolve the server<br>addresses and contact the servers. Yet I can assure you<br>that if ntpq -p says "No association ID's..." right<br>after boot, it will still say "No association ID's..."<br>an hour later. One of us should probably look at the<br>ntp source code.<br><br>Third, I'm mystified why you don't have this problem,<br>but I'm not the only one who has it (see #535049).<br><br>The good news is that /etc/network/if-up.d/ntp seems<br>to be a good workaround for
me.<br><br></div><div style="font-family: lucida console,sans-serif; font-size: 10pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Kurt Roeckx <kurt@roeckx.be><br><b><span style="font-weight: bold;">To:</span></b> Carl Mascott <cmascott@yahoo.com>; 561622@bugs.debian.org<br><b><span style="font-weight: bold;">Sent:</span></b> Fri, December 18, 2009 5:03:12 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [pkg-ntp-maintainers] Bug#561622: Race condition between ntp and NetworkManager at entry to runlevel 2<br></font><br>
On Fri, Dec 18, 2009 at 11:40:15AM -0800, Carl Mascott wrote:<br>> Subject: Race condition between ntp and NetworkManager at entry to runlevel 2<br>> Package: ntp<br>> Version: 1:4.2.4p4+dfsg-8lenny3<br>> Severity: important<br>> <br>> *** Please type your report below this line ***<br>> Related bug: 535049<br>> Symptom: On some startups ntpq -p reports "No association ID's...".<br>> On other startups ntpq -p reports servers & status normally.<br>> I.E., problem is intermittent.<br>> Cause: When ntpq -p reports "No association ID's..." it is because<br>> NetworkManager has not yet brought up the network interface<br>> (eth0 for me) when ntpd is trying to resolve server IP<br>> addresses. If ntpd gives up on resolving addresses at<br>> this point it will never try again later.<br>> Effect: ntpd does not provide time
unless restarted manually.<br>> Scope: The symptom I see is a problem with ntp. The underlying<br>> cause could affect other network services as well.<br>> Non-solution: Reorder startup scripts in /etc/rc2.d.<br>> Correct solution: ??<br><br>I have no idea why ntpd is saying that resolving failed. But that<br>means it got a permanent error resolving from somewhere. I have<br>no idea how your configuration is set up, but I never get such<br>permanent error.<br><br>I can perfectly bring up my wireless after some time, and ntpd<br>will pick up the servers after some time. Note that it doesn't<br>directly get them when the network gets up, but it does get them.<br><br>Anyway, the current ntp init script has this in it:<br># Required-Start: $network<br><br>I have no idea how that interacts with network manager, but I<br>would expect atleast some basic things to work.<br><br>Do you know what's in your
/etc/resolv.conf before the network<br>is brought up by network manager? Do you have some sort of<br>local nameserver? What does "grep ^hosts /etc/nsswitch.conf"<br>return?<br><br>What I find weird in your log is:<br>> Dec 18 09:26:08 ganymede ntpd[2741]: signal_no_reset: signal 17 had flags 4000000<br><br>I've never seen that message before. It seems the child sees<br>an old signal halder for SIGCHLD with SA_RESTORER set. (I have<br>no idea why ntpd is logging this.) This is probably unrelated<br>to your problem.<br><br>> Workaround: Use modified version of etch's /etc/network/if-up.d/ntp<br>> script as follows:<br><br>There should not be a need to restart ntpd, I think something<br>else is broken.<br><br><br>Kurt<br><br></div></div>
<!-- cg12.c3.mail.sp2.yahoo.com compressed/chunked Tue Dec 1 20:05:44 PST 2009 -->
</div><br>
</body></html>