Control: retitle -1 avahi-daemon: 10-second timeout in
/usr/lib/avahi/avahi-daemon-check-dns.sh and other issues (buggy regexp...)
Any news?
BTW, it seems to be an issue similar to bug 559927
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559927
"/usr/lib/avahi/avahi-daemon-check-dns.sh s
On 2019-05-16 18:36:09 +0200, Michael Biebl wrote:
> Am 16.05.19 um 18:17 schrieb Vincent Lefevre:
> > On 2019-05-16 17:52:03 +0200, Michael Biebl wrote:
> >> I would suggest the following: If there is a local nameserver but no
> >> network connectivity, query the local nameserver only.
> >
> > OK
Am 16.05.19 um 18:17 schrieb Vincent Lefevre:
> On 2019-05-16 17:52:03 +0200, Michael Biebl wrote:
>> I would suggest the following: If there is a local nameserver but no
>> network connectivity, query the local nameserver only.
>
> OK, I can do that. Indeed, the default behavior of "host" is to t
On 2019-05-16 17:52:03 +0200, Michael Biebl wrote:
> I would suggest the following: If there is a local nameserver but no
> network connectivity, query the local nameserver only.
OK, I can do that. Indeed, the default behavior of "host" is to try
every server in /etc/resolv.conf until it succeeds.
Am 16.05.19 um 17:44 schrieb Vincent Lefevre:
> On 2019-05-16 16:54:26 +0200, Michael Biebl wrote:
>> I'm happy to review a tested patch, which considers your specific use case.
>
> Would one of the following behaviors be OK?
>
> 1. If there is no default route, then assume that we can't reach an
On 2019-05-16 16:54:26 +0200, Michael Biebl wrote:
> I'm happy to review a tested patch, which considers your specific use case.
Would one of the following behaviors be OK?
1. If there is no default route, then assume that we can't reach any
nameservers (there's potentially a local nameserver, bu
Am 16.05.19 um 16:37 schrieb Vincent Lefevre:
> On 2019-05-16 16:25:01 +0200, Michael Biebl wrote:
>> What happens, if you only list your local 127.0.0.1 in /etc/resolv.conf?
>
> See my other mail, i.e. no problems. FYI, I use 192.168.1.1 just
> as a fallback.
>
>> Well, the assumption that /usr/
On 2019-05-16 16:25:01 +0200, Michael Biebl wrote:
> What happens, if you only list your local 127.0.0.1 in /etc/resolv.conf?
See my other mail, i.e. no problems. FYI, I use 192.168.1.1 just
as a fallback.
> Well, the assumption that /usr/lib/avahi/avahi-daemon-check-dns.sh makes
> is, that if a
On 2019-05-16 16:09:04 +0200, Vincent Lefevre wrote:
> On 2019-05-16 15:59:09 +0200, Vincent Lefevre wrote:
> > On 2019-05-16 14:41:44 +0200, Michael Biebl wrote:
> > > Am 16.05.19 um 14:22 schrieb Vincent Lefevre:
> > > > On 2019-05-16 14:15:37 +0200, Michael Biebl wrote:
> > > >> Looks like you h
Am 16.05.19 um 16:09 schrieb Vincent Lefevre:
> On 2019-05-16 15:59:09 +0200, Vincent Lefevre wrote:
>> On 2019-05-16 14:41:44 +0200, Michael Biebl wrote:
>>> Am 16.05.19 um 14:22 schrieb Vincent Lefevre:
On 2019-05-16 14:15:37 +0200, Michael Biebl wrote:
> Looks like you have a local reso
On 2019-05-16 15:59:09 +0200, Vincent Lefevre wrote:
> On 2019-05-16 14:41:44 +0200, Michael Biebl wrote:
> > Am 16.05.19 um 14:22 schrieb Vincent Lefevre:
> > > On 2019-05-16 14:15:37 +0200, Michael Biebl wrote:
> > >> Looks like you have a local resolver configured in /etc/resolv.conf
> > >> (whi
Am 16.05.19 um 15:59 schrieb Vincent Lefevre:
> On 2019-05-16 14:41:44 +0200, Michael Biebl wrote:
>> Am 16.05.19 um 14:22 schrieb Vincent Lefevre:
>>> On 2019-05-16 14:15:37 +0200, Michael Biebl wrote:
Looks like you have a local resolver configured in /etc/resolv.conf
(which should be r
On 2019-05-16 14:41:44 +0200, Michael Biebl wrote:
> Am 16.05.19 um 14:22 schrieb Vincent Lefevre:
> > On 2019-05-16 14:15:37 +0200, Michael Biebl wrote:
> >> Looks like you have a local resolver configured in /etc/resolv.conf
> >> (which should be reachable via lo, even if eth0 is down).
> >
> >
Am 16.05.19 um 14:22 schrieb Vincent Lefevre:
> On 2019-05-16 14:15:37 +0200, Michael Biebl wrote:
>> Looks like you have a local resolver configured in /etc/resolv.conf
>> (which should be reachable via lo, even if eth0 is down).
>
> Yes, /etc/resolv.conf contains
>
> nameserver 127.0.0.1
> name
On 2019-05-16 14:15:37 +0200, Michael Biebl wrote:
> Looks like you have a local resolver configured in /etc/resolv.conf
> (which should be reachable via lo, even if eth0 is down).
Yes, /etc/resolv.conf contains
nameserver 127.0.0.1
nameserver 192.168.1.1
as I use "unbound".
--
Vincent Lefèvre
Am 16.05.19 um 00:27 schrieb Vincent Lefevre:
> 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
> +
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-d
Control: tags -1 + moreinfo
Am 15.05.19 um 10:29 schrieb Vincent Lefevre:
> Package: avahi-daemon
> Version: 0.7-4+b1
> Severity: normal
>
> /etc/network/if-post-down.d/avahi-daemon takes 12 seconds to complete,
> slowing the shutdown:
>
> [...]
> May 15 10:23:47 zira dhclient[19399]: DHCPRELEAS
Package: avahi-daemon
Version: 0.7-4+b1
Severity: normal
/etc/network/if-post-down.d/avahi-daemon takes 12 seconds to complete,
slowing the shutdown:
[...]
May 15 10:23:47 zira dhclient[19399]: DHCPRELEASE of 192.168.1.3 on eth0 to
192.168.1.1 port 67
May 15 10:23:47 zira ifdown[19369]: DHCPRELE
19 matches
Mail list logo
