Re: [Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
My apologies, I have to backtrack on my prev statement. I thought to have read that on LWN some time in the past, but I cannot find such statement anymore through google. Fact is, that Debian hasn't moved to upstart OR systemd (or initng for that matter) yet, even in unstable, and is using insserv (optional) to parallelize the boot sequence. They are still contemplating which direction to take. see http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot and http://lists.debian.org/debian-devel-announce/2009/09/msg3.html and the most recent announcement http://lists.debian.org/debian-devel-announce/2010/05/msg9.html .. where upstart is described as 'the most promising candidate'. Again, sorry for the confusion :) On Monday 27 September 2010 11:52:48 you wrote: Isn't Debian still planning on moving to upstart? If so that would be a major vote of confidence and would guarantee upstart sticks around for a while longer. systemd looks very neat. That both RedHat and OpenSUSE are moving to adopt it is telling but I don't think it's very likely Ubuntu will give up upstart any time soon. More likely we'll see some borrowing of code and ideas. FWIW, SysVinit compatibility is the highest on my wishlist. OTOH, if Debian decide to move to systemd all bets are off. In that case I hope Ubuntu does the right thing and chucks upstart out rather than increase Ubuntu's divergence from the rest of the Linux world. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a direct subscriber of the bug. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
On Wednesday 15 September 2010 19:27:47 Liraz wrote: Many thanks to everyone who helped track down this regression, which effected TurnKey Linux users of the new TurnKey Core Lucid-based beta as well: https://bugs.launchpad.net/turnkeylinux/+bug/596560 IMHO, for desktop usage upstart has great potential. But for servers it's a net loss. Booting a few seconds faster doesn't matter as much as stability and simplicity. I just wish there was some way to save all of this asynchronous cleverness for the desktop. In a few years once Ubuntu and Debian transition fully to upstart we should be OK, but now it's ugly out there. Hmm I'm starting to doubt that, since many distributions are moving to systemd, and none except Ubuntu (and derivatives) to upstart. This will likely mean that most upstream projects will not take upstart into consideration, so Ubuntu alone will have to maintain it. If this bug is any indication.. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Yeah I'm actually stunned that such a design failure is not acted upon by Ubuntu. Guess they just capitalize on the work done by Debian, without having to do the hard work of actually maintaining a distribution. However this bug MUST sting on servers and 'old-school' people that use /etc/network/interfaces instead of NetworkManager, not to mention all the HOWTOs on the net that suggest solutions involving /etc/network/interfaces. Just apply the new versions of resolvconf files attached to the bug and your problems will be gone, at least until the upgrade to 10.04 :-/ I myself am moving to Debian ASAP grtz, Sander On Sunday 07 February 2010 10:25:55 you wrote: Just to say I have this bug too. :( Symptom: After a reboot, /etc/resolv.conf contains only this: $ 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 CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 nameserver 10.18.4.3 nameserver 10.18.4.1 There is no search domain, yet I specified it in /etc/network/interfaces as follows: dns-nameservers 10.18.4.3 10.18.4.1 dns-search blah.co.uk fudd.co.uk However, if I now issue the following command : $ sudo /etc/init.d/networking restart It fixes /etc/resolv.conf, as per this: $ 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 CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search blah.co.uk fudd.co.uk nameserver 10.18.4.3 nameserver 10.18.4.1 Can't wait till this is fixed. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
I think the problem is that there is a significant post-boot delay before resolv.conf is updated. It took ~ 90sec (after gdm start) on last boot. But at least it's working +Reardon On Mon, Dec 28, 2009 at 5:11 AM, Sander van Grieken san...@3v8.net wrote: ok, time for a full checklist :) - update /sbin/resolvconf from bug attachment - update /etc/resolvconf/update.d/libc from bug attachment - install /etc/init/resolvconf.conf from bug attachment - remove /etc/rcS.d/S07resolvconf - make sure /etc/resolv.conf symlinks to /lib/init/rw/resolvconf/resolv.conf vpn or tunnelling should work as good as before. Nothing has changed for 'late' connections. debugging is a bit hard, but you can see the non-zero exit code if you boot in rescue mode. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a direct subscriber of the bug. Status in “ifupdown” package in Ubuntu: Won't Fix Status in “resolvconf” package in Ubuntu: Confirmed Bug description: Binary package hint: resolvconf ifdown -a ; ifup -a fixes the problem after a reboot. ProblemType: Bug Architecture: i386 Date: Sat Oct 10 17:55:06 2009 DistroRelease: Ubuntu 9.10 Package: resolvconf 1.44ubuntu1 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-13.43-generic SourcePackage: resolvconf Uname: Linux 2.6.31-13-generic i686 To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/448095/+subscribe -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Ok, I've tried with all your latest, and basically nothing has changed, it's all still broken. On system boot, resolv.conf remains blank (or rather, it is created, but with no entries, only the top comment lines). ifdown/ifup fixes the problem. Same as the Ubuntu release problem. Have you tried with vpnc or similar tunnel installed? Does anything from /sbin/resolvconf get logged that I can read or send to you? +Reardon On Sat, Dec 26, 2009 at 7:11 PM, Sander van Grieken san...@3v8.net wrote: Found one more tiny bug. fixed it and replaced /sbin/resolvconf attachment. ** Attachment added: /sbin/resolvconf http://launchpadlibrarian.net/37215643/resolvconf ** Attachment removed: replacement for /sbin/resolvconf http://launchpadlibrarian.net/37141756/sbin.resolvconf -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a direct subscriber of the bug. Status in “ifupdown” package in Ubuntu: Won't Fix Status in “resolvconf” package in Ubuntu: Confirmed Bug description: Binary package hint: resolvconf ifdown -a ; ifup -a fixes the problem after a reboot. ProblemType: Bug Architecture: i386 Date: Sat Oct 10 17:55:06 2009 DistroRelease: Ubuntu 9.10 Package: resolvconf 1.44ubuntu1 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-13.43-generic SourcePackage: resolvconf Uname: Linux 2.6.31-13-generic i686 To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/448095/+subscribe -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
My mistake this time. It's working properly now with your updated /sbin/resolvconf +Reardon On Sat, Dec 26, 2009 at 7:16 AM, Sander van Grieken san...@3v8.net wrote: Did you redownload the /sbin/resolvconf replacement? Can you confirm there are no differences between your copy and the attachment? Because you report the same error the first /sbin/resolvconf replacement I posted had, and I cannot reproduce your current error with the current one. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a direct subscriber of the bug. Status in “ifupdown” package in Ubuntu: Won't Fix Status in “resolvconf” package in Ubuntu: Confirmed Bug description: Binary package hint: resolvconf ifdown -a ; ifup -a fixes the problem after a reboot. ProblemType: Bug Architecture: i386 Date: Sat Oct 10 17:55:06 2009 DistroRelease: Ubuntu 9.10 Package: resolvconf 1.44ubuntu1 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-13.43-generic SourcePackage: resolvconf Uname: Linux 2.6.31-13-generic i686 To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/448095/+subscribe -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Your solution did not work on reboot. Now when I try ''sudo resolvconf -i' I get a different error $ sudo resolvconf -i mkdir: cannot create directory `': No such file or directory resolvconf: Error: unable to create +Reardon On Fri, Dec 25, 2009 at 11:30 AM, Sander van Grieken san...@3v8.net wrote: You should use the /sbin/resolvconf from #17. I made a stupid mistake in the one I posted first. There's no need to create /lib/init/rw/resolvconf/interface by hand. It should be created at boot, or by calling /sbin/resolvconf -i as root. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a direct subscriber of the bug. Status in “ifupdown” package in Ubuntu: Won't Fix Status in “resolvconf” package in Ubuntu: Confirmed Bug description: Binary package hint: resolvconf ifdown -a ; ifup -a fixes the problem after a reboot. ProblemType: Bug Architecture: i386 Date: Sat Oct 10 17:55:06 2009 DistroRelease: Ubuntu 9.10 Package: resolvconf 1.44ubuntu1 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-13.43-generic SourcePackage: resolvconf Uname: Linux 2.6.31-13-generic i686 To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/448095/+subscribe -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
I've tried your fix Sander and it sort of works. Which is to say that resolvconf properly runs at boot. HOWEVER, it does not run correctly on ifdown/ifup: $ sudo ifdown eth0 [sudo] password for reardon: resolvconf: Error: /lib/init/rw/resolvconf/interface is not a directory resolvconf: Error: /lib/init/rw/resolvconf/interface is not a directory run-parts: /etc/network/if-down.d/resolvconf exited with return code 1 There is already a pid file /var/run/dhclient.eth0.pid with pid 1166 killed old client process, removed PID file Internet Systems Consortium DHCP Client V3.1.2 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:1d:92:a0:77:90 Sending on LPF/eth0/00:1d:92:a0:77:90 Sending on Socket/fallback DHCPRELEASE on eth0 to 192.168.0.1 port 67 resolvconf: Error: /lib/init/rw/resolvconf/interface is not a directory * Reloading /etc/samba/smb.conf smbd only ...done. $ sudo ifup eth0 Internet Systems Consortium DHCP Client V3.1.2 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:1d:92:a0:77:90 Sending on LPF/eth0/00:1d:92:a0:77:90 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 DHCPOFFER of 192.168.0.198 from 192.168.0.1 DHCPREQUEST of 192.168.0.198 on eth0 to 255.255.255.255 port 67 DHCPACK of 192.168.0.198 from 192.168.0.1 * Reloading /etc/samba/smb.conf smbd only ...done. resolvconf: Error: /lib/init/rw/resolvconf/interface is not a directory bound to 192.168.0.198 -- renewal in 2147483648 seconds. resolvconf: Error: /lib/init/rw/resolvconf/interface is not a directory run-parts: /etc/network/if-up.d/000resolvconf exited with return code 1 +Reardon On Thu, Dec 24, 2009 at 6:47 AM, Sander van Grieken san...@3v8.net wrote: but still, this is probably not the bug you suffer from.. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a direct subscriber of the bug. Status in “ifupdown” package in Ubuntu: Won't Fix Status in “resolvconf” package in Ubuntu: Confirmed Bug description: Binary package hint: resolvconf ifdown -a ; ifup -a fixes the problem after a reboot. ProblemType: Bug Architecture: i386 Date: Sat Oct 10 17:55:06 2009 DistroRelease: Ubuntu 9.10 Package: resolvconf 1.44ubuntu1 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-13.43-generic SourcePackage: resolvconf Uname: Linux 2.6.31-13-generic i686 To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/448095/+subscribe -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
I created the directory /lib/init/rw/resolvconf/interface by hand. But no idea what should go in here. The whole point of installing resolvconf in the first place was so that vpn clients would work properly (in my case, vpnc). But no updates to resolv.conf are made when I connect with vpnc (this did work with the original script, though the boot case was broken). +Reardon On Thu, Dec 24, 2009 at 2:02 PM, TR Reardon thomas_rear...@hotmail.comwrote: I've tried your fix Sander and it sort of works. Which is to say that resolvconf properly runs at boot. HOWEVER, it does not run correctly on ifdown/ifup: -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
