resolvconf borkage [solved]

[wuxmedia]

Hi all,

The other morning the normally always on (or suspended) work machine with Honey on had a problem.
its been fine (apart from no host, dig or nslookup -still) and fairly regularly upgraded.
I added a monitor and moved the box, which caused the power to come out.
plug it all back in, booted. No DNS resolving... pings, but no internet,jabber or remote shell.
panicked - using the Mint cinnamon fallback for actually doing things.

Then I had the same thing with the laptop with Arrogance on.
I noticed an error about:

resolvconf: Error: /etc/resolvconf/run/interface either does not exist or is not a directory

googled it, didn't understand the 2010 bug filed, so I purged then reinstalled resolvconf.
Seems to have worked. Will try with the work machine later next week.
I did notice in the last upgrade 'rpcbind' was removed... not sure why, or if it is the cause.

Anyway just in case anyone runs into this one.

[machinebacon]

Thanks wux,

and here on Sidbang et al. the nslookup/host/dig brings this error:
symbol lookup error: /usr/lib/libisccc.so.90: undefined symbol: isc_safe_memcmp

which in turn is this bug in bind9-host, reported by the great Joey Hess:
https://bugs.debian.org/cgi-bin/bugrepo ... bug=741188

Here I fixed it with

Code: Select all

sudo apt-get update && sudo apt-get install --reinstall bind9-host 

I'll move this to the Upgrade warnings, so it is readable for visitors.

[wuxmedia]

Cool, didn't think of doing a reinstall for 'host' for the fix.
Thanks!

[wuxmedia]

hmm, it resolvconf freaked out again... probably my fault.
no DNS at all, happily still in the apt-cache... re-installed again and it was ok...

[machinebacon]

wux, do you still have the /etc/resolv.conf file? And would you please post the directory of /etc/resolvconf/*?

[wuxmedia]

Thanks, Yeah the /etc/resolv.conf is in there. just 8.8.8.8 and 8.8.4.4
and;

Code: Select all

wux@chauvin:~$ ls -lash /etc/resolvconf/*
4.0K -rw-r--r-- 1 root root  481 May  8 12:58 /etc/resolvconf/interface-order
   0 lrwxrwxrwx 1 root root   15 May 25 16:58 /etc/resolvconf/run -> /run/resolvconf/

/etc/resolvconf/resolv.conf.d:
total 16K
4.0K drwxr-xr-x 2 root root 4.0K May 25 16:58 ./
4.0K drwxr-xr-x 4 root root 4.0K May 25 16:58 ../
   0 -rw-r--r-- 1 root root    0 May  8 12:58 base
4.0K -rw-r--r-- 1 root root  151 May  8 12:58 head
4.0K -rw-r--r-- 1 root root  189 Sep 13  2012 original
   0 -rw-r--r-- 1 root root    0 May 25 16:58 tail

/etc/resolvconf/update.d:
total 16K
4.0K drwxr-xr-x 2 root root 4.0K May 25 16:58 ./
4.0K drwxr-xr-x 4 root root 4.0K May 25 16:58 ../
8.0K -rwxr-xr-x 1 root root 4.6K May  8 12:58 libc*

ahh, there's the symlink for run... OK.
IDK whats going on.

[wuxmedia]

This was only still an issue on my honey desktop at home for some reason, no matter how much mucking around it never worked.
the only thing that worked in the end was ceni.
I tried what Bacon suggested, using dpkg-reconfigure, but that didn't work.
A colleague suggested removing all the damn resolvconf/ dir and sticking with resolv.conf.
the resolv.conf was a symlink to to somewhere that didn't exist.

Anyway i've purged resolvconf package, rm -rf the whole damn resolvconf/ dir and resolv.conf. made a new resolv.conf, put in the nameservers and it just worked, no reboots or anything.
Hopefully this is solved for good now, and won't happen to anyone else.

[machinebacon]

Can you post the result after reboot? Thank you :)

[wuxmedia]

Fine and dandy, just rebooted, straight into browser and no probs.
I should add, I suppose because of ceni, that I have a 'dns-nameservers' entry in the interfaces file.
Which probably helps.

Code: Select all

wux@honeypot:~$ ls /etc/resol*
/etc/resolv.conf
wux@honeypot:~$ cat /etc/resolv.conf 
nameserver 8.8.8.8
wux@honeypot:~$ sudo cat /etc/network/interfaces
....snip....
auto eth0
iface eth0 inet dhcp
	dns-nameservers 8.8.8.8
root@honeypot:~# dpkg -l | grep resolvc
rc  resolvconf                                              1.75                               all          name server information handler

edit: hadn't actually removed resolvconf package, I did so and still works after reboot.

[daggoth]

I have also had the aforementioned resolvconf error:

resolvconf: Error: /etc/resolvconf/run/interface either does not exist or is not a directory

But in my case, the context was clear. The error only occured when I test booted my system with "systemd" instead of "init" - I haven't yet made a permanent shift.

Looking further, this Debian bug says it happens because resolvconf was never started by systemd. And that this bug will mainly affect systems which don't have Network Manager installed. Indeed, my own system only uses ifupdown. And the fix in the debian bug posts #24 and #39 worked for me too.

That said, I am not using a linuxbbq distro, just Debian "testing". But even so, I believe the above will still be true for you guys - they haven't released a fixed resolvconf package yet.