The error still occurs and NM still refuses to populate resolv.conf. –Cerin May 15 '12 at 22:38 Did the trick for me. Bob Tregilus (elaterite) wrote on 2012-12-24: #96 Hey Thomas - Okay, I just installed Linux Mint 14 64-bit KDE. (I was running Mint 13 KDE LTS.) Immediately after the install the Thomas Hood (jdthood) wrote on 2013-01-04: #105 Having a static file instead of a symlink at /etc/resolv.conf is supported. lsattr /etc/resolv.conf cat /etc/NetworkManager/NetworkManager.conf cat /run/nm-dns-dnsmasq.conf df Thomas Hood (jdthood) wrote on 2012-05-29: #18 We appear to have another case of this, reported in #922677.
rogersmaSeptember 6th, 2014, 10:15 AMI've got the same problem, but my resolv.conf is not a file, but a link to a directory: /etc/resolv.conf -> /etc/resolvconf/ That directory contains the following file If this is the only place you're seeing it, then this is probably bug #1003595, which has been fixed in yesterday's daily image for EC2. Images Bad Linux Mint image (bug #1004421): toby-murray, albert-bendicho Bad Ubuntu EC2 cloud image (bug #1003595): louisli Bad Ubuntu Secure Remix image (bug #1051348): jrog Using Linode image (which lacks resolvconf): Cerin (chrisspen) wrote on 2012-05-22: #4 Thanks pdf. check my blog
There is certainly no generic "critical error" on upgrade for users who are not manually modifying the state of /etc/resolv.conf on their systems. So this appears to be a program that has not yet been made resolvconf-compatible. The content of the file /etc/resolv.conf is dynamically generated. resolvconf --enable-updates sudo reboot This created the symlink and now I see : ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 29 Jul 25 21:17 /etc/resolv.conf -> ../run/resolvconf/resolv.conf Thomas Hood (jdthood) on
Bob Tregilus (elaterite) wrote on 2012-12-14: #94 FYI Thomas: follow this link
Even better would be to return to having an idempotent postinst; but then another solution would have to be found for the problem that the debconf-fiddling solved. Thomas Hood (jdthood) on 2012-05-30 summary: - Network Manager does not populate resolv.conf because /etc/resolv.conf- symlink was not created+ resolv.conf not populated because /etc/resolv.conf symlink was not+ created Thomas Hood (jdthood) On each of these, if resolvconf is running then "start resolvconf" returns 1 but "invoke-rc.d resolvconf start" returns 0. These might contain clues.
start: Job is already running: resolvconf invoke-rc.d: initscript resolvconf, action "start" failed. /usr/sbin/dpkg-reconfigure: Resolvconf Is Broken Or Not Fully Installed Reply Link alwuzomondo July 3, 2012, 1:38 pmThanks for pointing me in the right direction. Edit: If I try to run resolvconf, I get the error "resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing anything." What should it be a symlink to and/or how do I networking resolv.conf share|improve this question asked Jul 28 '11 at 18:22 Azendale 6,92153056 add a comment| 2 Answers 2 active oldest votes up vote 4 down vote accepted It's easy to
Reload to refresh your session. What part is not fixed? Resolvconf Is Broken Or Not Fully Installed Thomas Hood (jdthood) wrote on 2012-12-14: #95 I wrote that. /run/resolvconf/interface When the stable comes out I might switch to it.
Is it virtual hardware? Very simple number line with points 2048-like array shift Trying to create safe website where security is handled by the website and not the user Russian babel, lmodern, and sans-serif font I.e., gradually with apt-get (without problems to speak of). Oddly could access other wifi network. Dpkg-reconfigure Resolvconf
My colleague misinterpreted his symptoms, and I believe his issue is only related to #1003842. What version of sysv-rc did the affected system have at the time of the error? The 12.04 LTS -> 14.04 LTS upgrades started this week. Processing triggers for man-db ...
Waiting for br0 to get ready (MAXWAIT is 18 seconds). Resolv.conf Symlink resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing anything. --------------------- Louis Li in #922677 #15 -------------------------- Here's some information: [email protected]:~$ ls -l /etc/resolv.conf -r--r--r-- 1 root root 63 May 29 13:42 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
I however, did a "dpkg-reconfigure resolvconf " and that resolved my issues. Do I need to water seeds? Looking at the apt logs I see an upgrade done at 2012-12-03 18:23:13. Resolvconf Error /run/resolvconf/interface [email protected]:~$ 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: true resolvconf/reboot-recommended-after-removal: [email protected]:~$ sudo !!
The original problem was that /etc/resolv.conf was not populated and the reason for this seems to have been that the symlink /etc/resolv.conf --> ../run/resolvconf/resolv.conf didn't get created. He also assumes dnsmasq caused the problem, which it did not, so disabling it all together and going back to managing resolv.conf manually is massive overkill. it remains same. The last sentence is a bit ugly but I was trying to keep it short.