After emerging net-dns/openresolv (replacement for resolvconf), the system will not boot because /etc/init.d/bootmisc checks that /etc/resolv.conf is a normal file. However, under openresolv it is actually a symlink. Reproducible: Always Steps to Reproduce: 1. Replace resolvconf with openresolv 1.3. 2. Reboot. Actual Results: Boot stops at /etc/init.d/bootmisc at the last line of the start function. Expected Results: Booted successfully. I don't think the openresolv 1.5 or 1.5.1 ebuilds have addressed this issue.
(In reply to comment #0) > After emerging net-dns/openresolv (replacement for resolvconf), > the system will not boot I can confirm this bug report. My /etc/resolv.conf was still a symlink left over from use of net-dns/resolvconf-gentoo-1.2, which was working when I unmerged it and then emerged net-dns/openresolv-1.3. (It previously pointed to resolvconf/run/resolv.conf, I believe, so the symlink was broken with use of openresolv.) I'm not sure if I rebooted between emerging V1.3 of openresolv and the time the package upgraded to V1.5.1. When I did finally reboot, the boot process failed like the original reporter described. The symptom was that /dev/.rcsysinit wasn't being properly removed during the boot process. This caused the scripts linked to in /etc/runlevels/boot/ to fail to run, complaining that runscipt "cannot run" these scripts "until sysinit completes" (eerror in line 42 of /sbin/runscript.sh). The only thing I had to do to fix the problem was rm /etc/resolv.conf (the old symlink). I can't remember there being any message printed urging users to rm this old symlink if it exists. If so, I just plain missed it. If there is no message, perhaps this package should print a warning when it installs? TIA. Clemmitt
(In reply to comment #1) > I can confirm this bug report. <snip> My `emerge --info' output: $ emerge --info Portage 2.1.4.4 (default-linux/x86/2007.0, gcc-4.1.2, glibc-2.6.1-r0, 2.6.24-gentoo-r7 i686) ================================================================= System uname: 2.6.24-gentoo-r7 i686 Intel(R) Pentium(R) M processor 1300MHz Timestamp of tree: Fri, 06 Jun 2008 14:16:01 +0000 app-shells/bash: 3.2_p33 dev-java/java-config: 1.3.7, 2.1.6 dev-lang/python: 2.4.4-r13 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.23-r3 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium3 -O2 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-march=pentium3 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="collision-protect distlocks fixpackages metadata-transfer parallel-fetch sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo http://gentoo.mirrors.pair.com/ http://gentoo.mirrors.tds.net/gentoo http://gentoo.osuosl.org/ http://gentoo.chem.wisc.edu/gentoo/ http://gentoo.seren.com/gentoo http://gentoo.itdnet.net/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="X Xaw3d a52 acl acpi additions alsa apm arts bash-completion berkdb bzip2 caps cdr cli connectionstatus cracklib crypt cups curl dbus dga dri dv dvd dvdread esd exif ffmpeg firefox flatfile foomaticdb fortran ftp gcj gdbm gif gimp gmp gphoto2 gpm gstreamer gtk hal highlight ibmacpi iconv ieee1394 imagemagick imlib ipv6 irc isdnlog java javascript jpeg jpeg2k kde kipi kqemu lm_sensors logrotate mad memlimit midi mime mmx mng motif mp3 mudflap ncurses nptl nptlonly nsplugin ogg opengl openmp oss pam pcmcia pcre pdf perl pmu png posix ppds pppd python qemu qt3 qt4 quicktime rdesktop readline real reflection scanner sdl session sharedmem spell spl sse sse2 ssl svg tcpd theora threads tiff timidity truetype usb utempter v4l vcd vnc vorbis wifi win32codecs wolfmame x86 xine xml xorg xpm xv xvid yv12 zlib" ALSA_CARDS="intel8x0" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="radeon vesa fbdev vga" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS FWIW, DNS-related ebuilds installed: $ equery -N -C l | grep -i dns [I--] [ ] dev-python/dnspython-1.5.0 (0) [I--] [ ] kde-base/kdnssd-3.5.9 (3.5) [I--] [ ] net-dns/bind-tools-9.4.1_p1 (0) [I--] [ ] net-dns/libidn-1.5-r1 (0) [I--] [ ] net-dns/openresolv-1.5.1 (0) [I--] [ ] net-dns/pdnsd-1.2.6 (0) [I--] [ ] net-misc/mDNSResponder-107.6-r5 (0)
(In reply to comment #1) > I can confirm this bug report. <snip> > When I did finally reboot, the boot process failed like the original > reporter described. Given that this reported bug is a boot-killer, I felt I better post more info (above). If thousands upon thousands of people aren't screaming about reboots failing after installing openresolv-1.5.1, perhaps this problem is caused by a strange interaction with other name resolution software -- in my specific case, net-dns/pdnsd, I'm guessing. So this reboot-fail problem hasn't bitten anyone else, eh? Strange.... I could find only the one thread onefriedrice posted the URL to on Gentoo forums with this complaint. Again, as posted there, the solution was to rm the broken /etc/resolv.conf symlink and ^D out of single-user mode, after which rebooting was successful. Clemmitt
I also thought that this 'bug' should be affecting more people if I understand it correctly, but we would definitely hear more noise about it if it were a widespread problem. I've never emerged net-dns/pdnsd, but there must be some unique config we both share. Well, as long as it doesn't affect the masses then I say it's a Good Thing and All's Well, and at least the workaround is simple and documented here if anyone else has this problem.
It looks like this problem is caused in the following situation: * You have net-dns/resolvconf-gentoo installed. * When updating, you are told that resolvconf-gentoo is deprecated, and that you should update to openresolv. * You download openresolv *before* uninstalling resolvconf-gentoo; uninstall resolvconf-gentoo; install openresolv without removing the /etc/resolv.conf softlink. If you do not download openresolv before uninstalling resolvconf-gentoo then you cannot install it because DNS resolution is broken. Most likely, you will remove the softlink and restart the net, solving the problem. Maybe restarting the net is enough. Maybe this is why the problem is not more widespread. SUGGESTION: If the openresolv ebuild finds a broken softlink as /etc/resolv.conf, it should remove it (or at least print a clear warning). See also http://forums.gentoo.org/viewtopic.php?p=5116725 Best regards Jakob
(In reply to comment #5) > If you do not download openresolv before uninstalling resolvconf-gentoo then > you cannot install it because DNS resolution is broken. Most likely, you will > remove the softlink and restart the net, solving the problem. I didn't download openresolv first. I just unmerged resolvconf-gentoo then emerged openresolv. My /etc/resolv.conf was a symlink pointing to resolvconf/run/resolv.conf, which I don't believe was removed when resolvconf-gentoo was unmerged. I'm guessing I created that file myself -- I remember reading somewhere I needed to do that. DNS resolution worked fine. My local resolv.conf file pointing to nameserver 127.0.0.1 along with pdnsd kept on ticking.... > SUGGESTION: > If the openresolv ebuild finds a broken softlink as /etc/resolv.conf, > it should remove it (or at least print a clear warning). Yes, this seems a prudent suggestion to help prevent problems for other users. Clemmitt
(In reply to comment #5) > It looks like this problem is caused in the following situation: > > * You have net-dns/resolvconf-gentoo installed. > * When updating, you are told that resolvconf-gentoo is deprecated, and that > you should update to openresolv. > * You download openresolv *before* uninstalling resolvconf-gentoo; uninstall > resolvconf-gentoo; install openresolv without removing the /etc/resolv.conf > softlink. I got hit by this bug too (it looked scary and was quite annoying), but just by upgrading from openresolv-1.3 to 1.5.1 with an emerge -Dvu world. Removing the /etc/resolv.conf symlink indeed solved the issue. > SUGGESTION: > If the openresolv ebuild finds a broken softlink as /etc/resolv.conf, it > should remove it Indeed. Erik
(In reply to comment #7) > (In reply to comment #5) > > It looks like this problem is caused in the following situation: > > > > * You have net-dns/resolvconf-gentoo installed. > > * When updating, you are told that resolvconf-gentoo is deprecated, and that > > you should update to openresolv. > > * You download openresolv *before* uninstalling resolvconf-gentoo; uninstall > > resolvconf-gentoo; install openresolv without removing the /etc/resolv.conf > > softlink. > > I got hit by this bug too (it looked scary and was quite annoying), but just by > upgrading from openresolv-1.3 to 1.5.1 with an emerge -Dvu world. Removing the > /etc/resolv.conf symlink indeed solved the issue. > > > SUGGESTION: > > If the openresolv ebuild finds a broken softlink as /etc/resolv.conf, it > > should remove it > Confirm! Exactly this happened on my system, too! ... and I vote for the suggested fix. Cheers Axel
Thanks guys, sorry you had trouble. I'm just looking over the openresolv bugs and conclude that this one isn't really an issue anymore given that the last comment is ~1.5 years ago.
(In reply to comment #9) > Thanks guys, sorry you had trouble. > > I'm just looking over the openresolv bugs and conclude that this one isn't > really an issue anymore given that the last comment is ~1.5 years ago. > closing.
