Bind9resolvconf Error /etc/resolvconf/run/interface Is Not A Directory
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About /run/resolvconf/interface either does not exist or is not a directory Us Learn more about Stack Overflow the company Business Learn more about hiring
Resolvconf Is Broken Or Not Fully Installed
developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a /usr/sbin/dpkg-reconfigure resolvconf is broken or not fully installed question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are reinstall resolvconf voted up and rise to the top How can I repair “/run/resolvconf/interface” missing error? up vote 2 down vote favorite An upgrade from Ubuntu 14.04LTS to Ubuntu 15 failed. Package repair hangs at this point: Setting up resolvconf (1.77ubuntu1) ... Processing triggers for resolvconf (1.77ubuntu1) ... resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory dpkg: error processing package resolvconf (--configure) How can I get
Resolvconf Error /run/resolvconf/interface
past this point? sudo apt-get remove resolvconf Wants to remove ubuntu-base, which seems like a bad idea. I see Debian Bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749405 The problem was probably triggered by a manual attempt on my part to start networking using old school editing of /etc/resolv.conf network-manager dpkg boot-repair repair resolvconf share|improve this question asked Feb 29 at 3:59 Bryce 480422 What's the output of ls -l /run/resolvconf/interface ..also after changing /etc/resolv.conf manually you could just do sudo resolvconf -u do make resolvconf creating it again..resolvconf depends on lsb-base so removing it won't be a good idea.. –heemayl Feb 29 at 4:07 sudo resolvconf -u does not help. /run/resolvconf/ does not exist. –Bryce Feb 29 at 4:38 You can try sudo mkdir -p /run/resolvconf/interface and re-running your package repair. If that fails it might be difficult to fix and you may need to remove and re-install a ton of packages and you may have a broken system. See also - blog.bodhizazen.net/linux/… –bodhi.zazen Feb 29 at 5:32 I ran the repair script, except this time did not first start networking at that boot. Now it worked. –Bryce Mar 1 at 6:30 @Bryce, which
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might sudo dpkg-reconfigure resolvconf have Meta Discuss the workings and policies of this site About resolv conf is not installed Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with
Resolv.conf Missing
us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only http://askubuntu.com/questions/740304/how-can-i-repair-run-resolvconf-interface-missing-error takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top NetworkManager not populating resolv.conf up vote 37 down vote favorite 18 I recently upgraded from 11.10 to 12.04, and now NetworkManager isn't populating /etc/resolv.conf when connecting to wireless networks, http://askubuntu.com/questions/137037/networkmanager-not-populating-resolv-conf when it had been working perfectly in 11.10. I'm not seeing any explicit errors in either the NM UI or in syslog. How do I diagnose what's wrong? 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 get NM to populate it? This says the symlink should point to /run/resolvconf/resolv.conf, but that file does not exist on my system. network-manager dns resolv.conf share|improve this question edited Feb 16 '14 at 15:50 Braiam 38.8k1692153 asked May 14 '12 at 21:29 Cerin 1,44662648 I have tried a combination of the below solutions and then edited resolv.conf to include nameserver 127.0.0.1 because I had this problem about a year ago already and back then I think it had something to do with this line. After a restart the file was overwritten, but not with just comments but a different nameserver … line and some other things. Finally, it’s wor
for resolvconf is src:resolvconf. Reported by: Harald Braumann
together with resolvconf and it is configured to use resolvconf, it fails to start: # apt-get install resolvconf bind9 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: bind9-doc ufw The following NEW packages will be installed: bind9 resolvconf 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/344kB of archives. After this operation, 1155kB of additional disk space will be used. Preconfiguring packages ... Selecting previously deselected package bind9. (Reading database ... 89752 files and directories currently installed.) Unpacking bind9 (from .../bind9_1%3a9.6.1.dfsg.P1-3_amd64.deb) ... Selecting previously deselected package resolvconf. Unpacking resolvconf (from .../resolvconf_1.45_all.deb) ... Processing triggers for man-db ... Setting up bind9 (1:9.6.1.dfsg.P1-3) ... Adding group `bind' (GID 108) ... Done. Adding system user `bind' (UID 102) ... Adding new user `bind' (UID 102) with group `bind' ... Not creating home directory `/var/cache/bind'. wrote key file "/etc/bind/rndc.key" # Starting domain name service...: bind9resolvconf: Error: /etc/resolvconf/run/interface is not a directory invoke-rc.d: initscript bind9, action "start" failed. And it just hangs there. The culprit seems to be in bind9's init script: if [ "X$RESOLVCONF" != "Xno" ] && [ -x /sbin/resolvconf ] ; then echo "nameserver 127.0.0.1" | /sbin/resolvconf -a lo.named fi So resolvconf is executed, because the package is already installed but it fails, because resolvconf is not yet configured. If bind9 is installed after resolvconf is properly configured, there's no problem. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31.4-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=de_AT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bind9 depends on: ii adduser 3.111 add and remove users and groups ii bind9utils 1:9.6.1.dfsg.P1-3 Utilities for BIND ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii libbind9-50 1:9.6.1.dfsg.P1-3 BIND9 Shared Library used by BIND ii libc6 2.9-25 GNU C Library: Shared libraries ii libcap2 1:2.17-1 support