On 2019-05-15 12:50:49 +0200, Michael Biebl wrote: > Which part of /usr/lib/avahi/avahi-daemon-check-dns.sh is taking so long? > Can you add a "set -x" and then manually invoke "ifdown eth0"
I get: + PATH=/bin:/usr/bin:/sbin:/usr/sbin + RUNDIR=/var/run/avahi-daemon/ + DISABLE_TAG=/var/run/avahi-daemon//disabled-for-unicast-local + NS_CACHE=/var/run/avahi-daemon//checked_nameservers + AVAHI_DAEMON_DETECT_LOCAL=1 + test -f /etc/default/avahi-daemon + . /etc/default/avahi-daemon + AVAHI_DAEMON_DETECT_LOCAL=1 + [ 1 != 1 ] + dns_reachable + grep -q nameserver /etc/resolv.conf + + egrep -q nameserver 127.0.0.1|::1 /etc/resolv.conf + + return 0 + dns_needs_check + TMP_CACHE=/var/run/avahi-daemon//checked_nameservers.8379 + RET=0 + ensure_rundir + [ ! -d /var/run/avahi-daemon/ ] + cat /etc/resolv.conf + grep nameserver + sort + [ -e /var/run/avahi-daemon//checked_nameservers ] + mv /var/run/avahi-daemon//checked_nameservers.8379 /var/run/avahi-daemon//checked_nameservers + return 0 + dns_has_local + [ -n ] + LC_ALL=C host -t soa local. + OUT=;; connection timed out; no servers could be reached + [ 1 -eq 0 ] + rm -f /var/run/avahi-daemon//checked_nameservers + return 1 + enable_avahi + [ -e /var/run/avahi-daemon//disabled-for-unicast-local ] + exit 0 with several seconds between + LC_ALL=C host -t soa local. and + OUT=;; connection timed out; no servers could be reached At least, this is consistent with the timeout. Moreover, I don't understand why it tries to reach servers as eth0 is down (this is called in an if-post-down.d script). -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
