[Bug 999725] Re: broken start-up dependencies for ntp (starts before NIS is available)

2013-01-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ntp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/999725 Ti

[Bug 999725] Re: broken start-up dependencies for ntp (starts before NIS is available)

2012-12-02 Thread John Hupp
No, nis is not on hosts line of nsswitch.conf. I agree that my case is not the same as the one reported. But since the problem here is reported to be one in which ntp is being started before the system is capable of resolving DNS, I couldn't help but notice the similarity to my previous problem i

[Bug 999725] Re: broken start-up dependencies for ntp (starts before NIS is available)

2012-12-02 Thread Thomas Hood
@John: Does the affected machine have "nis" on the "hosts" line in /etc/nsswitch.conf? If not then your problem is not the same as this one. ** Changed in: ntp (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is s

[Bug 999725] Re: broken start-up dependencies for ntp (starts before NIS is available)

2012-12-02 Thread John Hupp
I'm currently troubleshooting a problem with a Lubuntu Quantal setup with LTSP (terminal server network). Most of the clients stop responding at a blank/black screen during bootup. But only after successfully PXE network booting, getting DHCP assignments, and beginning the process of booting from

[Bug 999725] Re: broken start-up dependencies for ntp (starts before NIS is available)

2012-07-18 Thread Launchpad Bug Tracker
[Expired for ntp (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ntp (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/

[Bug 999725] Re: broken start-up dependencies for ntp (starts before NIS is available)

2012-05-19 Thread Paul Crawford
It is probably true that this has not been seen much as a bug due to DNS normally being available, hence NIS dependency (if present) being a secondary issue. However, we found that ntp did not recover by itself, so possibly it only tries to find the nameservers once, but will re-try for the time se

[Bug 999725] Re: broken start-up dependencies for ntp (starts before NIS is available)

2012-05-18 Thread Nathan Stratton Treadway
> I'm not sure off hand how the decision is made whether to > convert a package such as ntp to Upstart... but I see a > couple other bugs open on the topic: LP #604717 , LP #913379 Sorry, should have written those bug references as: LP: #604717 , LP: #913379 -- You received this bug notification

Re: [Bug 999725] Re: broken start-up dependencies for ntp

2012-05-18 Thread Nathan Stratton Treadway
On Fri, May 18, 2012 at 17:47:21 -, Paul Crawford wrote: > I think this bug should concentrate on the key issue: > that ntp (and maybe others?) is being brought up on the > wrong event, that is it comes up with the interface, and > not with the chosen type of name server. More specifically, th

[Bug 999725] Re: broken start-up dependencies for ntp

2012-05-18 Thread Paul Crawford
Yes, you are right in that our NIS servers are solaris boxes, and they do support behind-the-scenes DNS lookups as it turns out. It is also true that NIS is depreciated, though a lot of older installations like ours still use it, and for most machines DNS is available and will probably fix our spec

Re: [Bug 999725] Re: broken start-up dependencies for ntp

2012-05-18 Thread Nathan Stratton Treadway
On Thu, May 17, 2012 at 19:33:37 -, Paul Crawford wrote: > domain, I think). I don't really understand NIS, and the > guy usually responsible for this sort of thing is away, > but as far as I know it only provides local-area > user/machine authentication and so I would be surprised > if it 'kno

[Bug 999725] Re: broken start-up dependencies for ntp

2012-05-18 Thread Paul Crawford
I think this bug should concentrate on the key issue: that ntp (and maybe others?) is being brought up on the wrong event, that is it comes up with the interface, and not with the chosen type of name server. In our case NIS provides user and name server resolution, and ntp comes up before it with

[Bug 999725] Re: broken start-up dependencies for ntp

2012-05-18 Thread Paul Crawford
Yes, it looks very much like the DNS system is broken here, but when I tried to look things up I get Bug #1001189 so overall not impressed with 12.04 so far :( Still, adding some "dns-nameservers" lines to /etc/network/interfaces is the next obvious thing to try. -- You received this bug notific

Re: [Bug 999725] Re: broken start-up dependencies for ntp

2012-05-17 Thread Nathan Stratton Treadway
On Thu, May 17, 2012 at 19:33:37 -, Paul Crawford wrote: > $ cat /etc/nsswitch.conf [...] > hosts: files nis dns > domain, I think). I don't really understand NIS, and the > guy usually responsible for this sort of thing is away, > but as far as I know it only provides local-area > u

[Bug 999725] Re: broken start-up dependencies for ntp

2012-05-17 Thread Paul Crawford
These are the nsswitch results: -- $ ls -l /etc/nsswitch.conf -rw-r--r-- 1 root root 600 May 1 11:28 /etc/nsswitch.conf -- $ cat /etc/nsswitch.conf # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # I

Re: [Bug 999725] Re: broken start-up dependencies for ntp

2012-05-17 Thread Nathan Stratton Treadway
On Thu, May 17, 2012 at 18:43:59 -, Paul Crawford wrote: > So ping is able to perform the name-to-IP conversion fine, but host > and nslookup both fail! Right, host and nslookup both (attempt to) do DNS queries directly, while ping does the lookup using libc6 library routines... So, what do y

[Bug 999725] Re: broken start-up dependencies for ntp

2012-05-17 Thread Paul Crawford
It is somewhat odd, as I get this: $ ping ntp0.dundee.ac.uk PING ntp0.dundee.ac.uk (172.30.254.253) 56(84) bytes of data. 64 bytes from 443-gb-core-6513.private.dundee.ac.uk (172.30.254.253): icmp_req=1 ttl=254 time=0.281 ms 64 bytes from 443-gb-core-6513.private.dundee.ac.uk (172.30.254.253): i

Re: [Bug 999725] Re: broken start-up dependencies for ntp

2012-05-17 Thread Nathan Stratton Treadway
On Thu, May 17, 2012 at 16:46:15 -, Paul Crawford wrote: > Results for 12.04 machine are: > $ ls -l /etc/resolv.conf > lrwxrwxrwx 1 root root 29 Apr 30 17:39 /etc/resolv.conf -> > ../run/resolvconf/resolv.conf > > $ cat /etc/resolv.conf > # Dynamic resolv.conf(5) file for glibc resolver(3) ge

[Bug 999725] Re: broken start-up dependencies for ntp

2012-05-17 Thread Paul Crawford
Results for 12.04 machine are: $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 29 Apr 30 17:39 /etc/resolv.conf -> ../run/resolvconf/resolv.conf $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGE

Re: [Bug 999725] Re: broken start-up dependencies for ntp

2012-05-17 Thread Nathan Stratton Treadway
On Thu, May 17, 2012 at 16:10:39 -, Paul Crawford wrote: > # The primary network interface > auto eth0 > iface eth0 inet static > address 134.36.22.69 > netmask 255.255.255.0 > gateway 134.36.22.1 Since the resolvconf package is installed by default in Precise, you'd normally need to have a

[Bug 999725] Re: broken start-up dependencies for ntp

2012-05-17 Thread Paul Crawford
I am not 100% sure of how the network was configured (the guy who did it is away today) but can report that the contents of /etc/network/interfaces are: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The

[Bug 999725] Re: broken start-up dependencies for ntp

2012-05-17 Thread Scott Moser
Hi, Could you tell us how networking is configured in your system? Ie, are you using network manager? ntp (or any rc-sysvinit script) should not start until all "static networking" is up. "static networking" means anything defined in /etc/network/interfaces, but does not include network