[Bug 1000244] Re: resolv.conf not populated because /etc/resolv.conf symlink was not created

Cerin 1000244 at bugs.launchpad.net
Fri Jun 1 14:26:22 UTC 2012


Thomas,

>You say that your setup is "partially" fixed. What part is not fixed?

When I initially applied pdf's fix, I was able to resolve external
domains, but not internal domains. However, this seems to have resolved
itself, so now it seems my setup is completely fixed.

Also, the output of those commands are:

user at localhost:~$ debconf-show resolvconf
debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied
* resolvconf/downup-interfaces:
* resolvconf/linkify-resolvconf: false
* resolvconf/link-tail-to-original: false
  resolvconf/fixing-immutable:
  resolvconf/reboot-recommended-after-removal:
user at localhost:~$ who -b
         system boot  2012-05-31 20:09
user at localhost:~$ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 May 22 10:33 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
user at localhost:~$ lsattr /etc/resolv.conf
lsattr: Operation not supported While reading flags on /etc/resolv.conf
user at localhost:~$ ls -l /run/resolvconf
total 4
-rw-r--r-- 1 root root  0 May 31 20:09 enable-updates
drwxr-xr-x 2 root root 60 Jun  1 10:01 interface
-rw-r--r-- 1 root root 97 Jun  1 10:01 resolv.conf
user at localhost:~$ ls -l /run/resolvconf/interface
total 4
-rw-r--r-- 1 root root 67 Jun  1 10:01 NetworkManager
user at localhost:~$ for F in /run/resolvconf/interface/* ; do echo "=== $F ===" ; cat "$F" ; done
=== /run/resolvconf/interface/NetworkManager ===
domain mydomain.com
search mydomain.com
nameserver 127.0.0.1
user at localhost:~$ for F in /etc/resolvconf/resolv.conf.d/* ; do echo "=== $F ===" ; cat "$F" ; done
=== /etc/resolvconf/resolv.conf.d/base ===
=== /etc/resolvconf/resolv.conf.d/head ===
# 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
=== /etc/resolvconf/resolv.conf.d/original ===
# Generated by NetworkManager
domain mydomain.com
search mydomain.com
nameserver 10.157.10.12
nameserver 10.157.10.14
nameserver 192.168.1.1
user at localhost:~$ cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile
dns=dnsmasq

[ifupdown]
managed=false
user at localhost:~$ cat /run/nm-dns-dnsmasq.conf
server=10.157.10.12
server=10.157.10.14
server=192.168.1.1
user at localhost:~$ df
Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/sda2      152180736 87537376  57024220  61% /
udev             3935756        4   3935752   1% /dev
tmpfs            1579044      928   1578116   1% /run
none                5120        0      5120   0% /run/lock
none             3947600      612   3946988   1% /run/shm
cgroup           3947600        0   3947600   0% /sys/fs/cgroup

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1000244

Title:
  resolv.conf not populated because /etc/resolv.conf symlink was not
  created

Status in “resolvconf” package in Ubuntu:
  Incomplete

Bug description:
  I upgraded an 11.10 install to 12.04, and now I'm unable to resolve
  domain names because Network Manager does not populate my
  /etc/resolv.conf file.

  For example, my local wireless router uses the domain "mylocaldomain"
  and nameservers 10.157.10.12 and 10.157.10.14, so in 11.10, after
  connecting to the router I would see this in my /etc/resolv.conf:

  domain mylocaldomain
  search mylocaldomain
  nameserver 10.157.10.12
  nameserver 10.157.10.14

  Now /etc/resolv.conf contains the settings last set before I upgraded
  to 12.04, and doesn't update them for whatever network I'm currently
  on. I have to manually guess the settings and modify /etc/resolv.conf
  in order to resolve domain names.

  I believe this may be related to
  https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/922677 and
  how the "resolvconf" program has been introduce to manage this. I
  believe this is a new bug with how prior installs are improperly
  upgraded.

  I tried removing the line "dns=dnsmasq" from
  /etc/NetworkManager/NetworkManager.conf and then running `sudo restart
  network-manager`, but that had no effect.

  I tried running `resolvconf --enable-updates` but I get the error
  "resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing
  anything."

  Based on https://help.ubuntu.com/12.04/serverguide/network-
  configuration.html#name-resolution, I tried establishing this symlink
  myself, but the file /run/resolvconf/resolv.conf does not exist on my
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
  Date: Wed May 16 09:57:25 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012)
  IpRoute:
   default via 192.168.1.1 dev eth2  proto static 
   169.254.0.0/16 dev eth2  scope link  metric 1000 
   192.168.1.0/24 dev eth2  proto kernel  scope link  src 192.168.1.205  metric 2 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-05-10 (5 days ago)
  nmcli-dev:
   DEVICE     TYPE              STATE         DBUS-PATH                                  
   eth2       802-11-wireless   connected     /org/freedesktop/NetworkManager/Devices/1  
   eth0       802-3-ethernet    unavailable   /org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING         VERSION    STATE           NET-ENABLED   WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
   running         0.9.4.0    connected       enabled       enabled         enabled    enabled         enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions




More information about the foundations-bugs mailing list