A debian server for which the previous administrator has disappeared is playing up. When bringing up networking we see something like (copied by hand; may contain typos)
$ sudo ifdown eth0 $ sudo ifup eth0 ADDRCONF(NETDEV_UP): eth0: link is not ready /etc/network/if-up.d/avahi-daemon: line 9: /usr/lib/avahi/avahi-daemon-check-dns.sh: No such file or directory /etc/network/if-up.d/avahi-daemon: line 9: exec: /usr/lib/avahi/avahi-daemon-check-dns.sh: cannot execute: No such file or directory run-parts: /etc/network/if-up.d/avahi-daemon exited with return code 126 /usr/lib/avahi doesn't exist, and I can't find avahi-daemon-check-dns.sh anywhere on the system. An apt-get update was performed about a week before the issues were noticed; it's possible that the system was restarted for the first time a week after the update was applied. My google-foo has failed to find answers this time. I'm assuming (and we all know what a good idea that is...) that something dodgy happened in the latest apt-get update, and the system has been left in an inconsistent state. I've tried commenting out the offending line in etc/network/if-up.d/avahi-daemon to no avail; the result is $ sudo ifdown eth0 $ sudo ifup eth0 ADDRCONF(NETDEV_UP): eth0: link is not ready run-parts: /etc/network/if-up.d/avahi-daemon exited with return code 1 Your suggestions for regaining network access, or of places I should look for clues, are solicited.
