resolvconf starts too late, breaks DNS

Bug #37118 reported by Anders Kaseorg
10
Affects Status Importance Assigned to Milestone
resolvconf (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

I run Dapper on two machines, one with a PCMCIA wired network card, and one with a MiniPCI wireless card. On both of them, the /etc/resolv.conf file is empty on bootup (except for the "DO NOT EDIT" comment). This is less than useful.

The problem is that resolvconf somehow initializes after dhclient has already been run. This overwrites the dhclient-generated resolv.conf with a blank version.

If I tell resolvconf to start earlier, by moving /etc/rcS.d/S38resolvconf to S12resolvconf, the problem goes away on at least the first machine (I can't test the second now). There is probably still a race condition, but if there is one it will be tricky to fix: resolvconf can't start earlier than 11 since it uses /dev/shm.

Revision history for this message
Anders Kaseorg (andersk) wrote :

Changing Severity to Critical, because this makes the system useless for anyone who doesn't know how to restart the network.

Matt Edwards (mwedwards)
Changed in resolvconf:
status: Unconfirmed → Confirmed
Revision history for this message
Sebastian Kapfer (caci) wrote :

Updated package doesn't do that anymore. (You might need to tweak the symlink manually though on old installs. I don't know of a easy way to do that in postinst, so it hasn't been done.)

Revision history for this message
dix_ans (dichodaemon) wrote :

I have uninstalled the old version of resolvconf and deleted the /etc/resolvconf directory. After installing the latest version (1.34ubuntu1) and rebooting I've got what I suppose is the good simulink /etc/resolv.conf -> /etc/resolvconf/run/resolv.conf but there is no resolv.conf file in the run directory.

In the other hand, I may see an eth0.inet file in the run/interface directory containing the good configuration.

Revision history for this message
Sebastian Kapfer (caci) wrote :

Please provide a directory listing of /etc/resolvconf.

ls -l /etc/resolvconf

Revision history for this message
dix_ans (dichodaemon) wrote :

Here it is:

drwxr-xr-x 2 root root 4096 2006-04-04 12:20 resolv.conf.d
lrwxrwxrwx 1 root root 19 2006-04-04 12:20 run -> /var/run/resolvconf
drwxr-xr-x 2 root root 4096 2006-04-04 12:20 update.d
drwxr-xr-x 2 root root 4096 2005-12-18 17:16 update-libc.d

Revision history for this message
Marc Schiffbauer (mschiff) wrote :

I am having Problems with resolvconf, too.

I think the problem is that we have
  S07resolvconf
and
  S11mountdevsubfs
in /etc/rcS.d/
so resolvconf is started before /dev/shm is mounted by mountdevsubfs which cannot work IMO.... or am I missing something?

-Marc

Revision history for this message
Zak B. Elep (zakame) wrote :

Should now be fixed in latest Dapper 1.34ubuntu2 .

Changed in resolvconf:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.