[karmic] resolvconf not started at system boot

[Wesley Schwengle]

resolvconf is not started at boot, the init.d script is only run when booting to single user mode. This becomes a problem when /var/run is a tmpfs filesystem, since /var/run/resolvconf is created by the init.d start script. If this dir is missing then my network doesn't come up properly. See this interfaces file config:

iface home-fixed inet static
    test peer address 192.168.1.1 mac 00:60:4C:CC:86:39 source 192.168.1.14
    address 192.168.1.14
    netmask 255.255.255.0
    gateway 192.168.1.1
    dns-domain opperschaap.net
    dns-search opperschaap.net euronet.nl wanadoo.nl online.nl
    dns-nameservers 194.134.5.5 194.134.0.97
    metric 1

$ sudo aptitude install resolvconf
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following NEW packages will be installed:
  resolvconf
0 packages upgraded, 1 newly installed, 0 to remove and 40 not upgraded.
Need to get 0B/55.2kB of archives. After unpacking 274kB will be used.
Writing extended state information... Done
Preconfiguring packages ...
Selecting previously deselected package resolvconf.
(Reading database ... 203636 files and directories currently installed.)
Unpacking resolvconf (from .../resolvconf_1.44ubuntu1_all.deb) ...
Processing triggers for man-db ...
Setting up resolvconf (1.44ubuntu1) ...

Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done

/home/wesleys/resolvconf-1.44ubuntu1$ ls -altr /etc/rc?.d/* | grep resolv
lrwxrwxrwx 1 root root 20 2009-08-27 20:33 /etc/rcS.d/S07resolvconf -> ../init.d/resolvconf

The issue can be fixed by running:
sudo ln -s /etc/init.d/resolvconf /etc/rc2.d/S07resolvconf

resolvconf:
  Installed: 1.44ubuntu1
  Candidate: 1.44ubuntu1
  Version table:
 *** 1.44ubuntu1 0
        500 http://archive.ubuntu.com karmic/universe Packages
        100 /var/lib/dpkg/status

Linux eniac 2.6.31-6-generic #26-Ubuntu SMP Fri Aug 21 17:48:16 UTC 2009 i686 GNU/Linux

Distributor ID: Ubuntu
Description: Ubuntu karmic (development branch)
Release: 9.10
Codename: karmic

[Anders Kaseorg (andersk)]

I think you have slightly misdiagnosed the problem. /etc/rcS.d/* are run in all runlevels, not just single user mode. (Single user mode runs /etc/rcS.d/* and /etc/rc1.d/*; multiuser mode runs /etc/rcS.d/* and /etc/rc2.d/*.)

However, you seem to have the same symptoms as bug 448095, which is caused because resolvconf starts after ifupdown. I will mark this as a duplicate for now.

[Wesley Schwengle (wesleys)]

The duplicate status is incorrect. I found out what is causing the bug. /etc/resolvconf/run was a symlink to /var/run/resolvconf. I removed the symlink and purged/installed resolvconf and rebooted my machine. Everything runs as expected.

[GianlucaDAndrea (acid-burn-x-privat)]

I have the same problem: resolvconf is not started at boot time, BUT

cvs@ubuntu-sicurezza:/etc$ ls -lr resolvconf/
total 20
drwxr-xr-x 2 root root 4096 2009-11-02 16:58 update-libc.d
drwxr-xr-x 2 root root 4096 2009-11-02 16:54 update.d
drwxr-xr-x 3 root root 4096 2009-11-04 10:47 run
drwxr-xr-x 2 root root 4096 2009-11-02 16:54 resolv.conf.d
-rw-r--r-- 1 root root 116 2009-03-30 10:02 interface-order

/etc/resolvconf/run is NOT a symlink to /var/run/resolvconf AND

cvs@ubuntu-sicurezza:/etc$ find rc*.d -iname "*resolvconf*"
rcS.d/S07resolvconf
cvs@ubuntu-sicurezza:/etc$ find rc*.d -iname "*networking*"
rc0.d/S35networking
rc6.d/S35networking
cvs@ubuntu-sicurezza:/etc$ find rc*.d -iname "*ifupdown*"
rc0.d/S15wpa-ifupdown
rc6.d/S15wpa-ifupdown

resolvconf is started BEFORE networking and ifupdown.

Both on Karmic new install and update from Intrepid.

[PaulSchulz (paulschulz)]

I can get the correct details appearing in '/etc/resolv.conf' if I do the following by hand after a reboot.

  /etc/init.d/resolvconf start
  ifdown eth0; ifup eth0

[Juan Simón (simonbcn)]

This still occurs in Ubuntu 10.04 LTS!! o_O