[avahi] Unexpected resolution failures

[Ludovic Courtès]

Hi,

Lennart Poettering <lennart at poettering.net> writes:

> On Fri, 25.08.06 10:40, Ludovic Courtès (ludovic.courtes at laas.fr) wrote:
>
>> Hi,
>> 
>> At my office, I often notice that, after `avahi-daemon' has been running
>> for some time, several services suddenly become "unresolvable".
>> Restarting the daemon magically makes them resolvable again.
>> Concretely, here is what I observe:
>> 
>>   $ avahi-browse -rk _daap._tcp
>>   + eth0 IPv4 Juan                                          _daap._tcp           local
>>   + eth0 IPv4 civodul                                       _daap._tcp           local
>>   + eth0 IPv4 Marc                                          _daap._tcp           local
>>   Failed to resolve service 'Juan' of type '_daap._tcp' in domain 'local': Timeout reached
>>   Failed to resolve service 'civodul' of type '_daap._tcp' in domain 'local': Timeout reached
>>   Failed to resolve service 'Marc' of type '_daap._tcp' in domain 'local': Timeout reached
>>   Got SIGINT, quitting.
>
> Is any of these three services on the local machine?
>
> Do the other machines run Avahi or native Bonjour?

One of them was on the local machine.  All other machines run Apple's
Bonjour on MacOS X.

>> Is it something that other people already experienced?  If not, how can
>> I provide more useful information?
>
> Nope, I for sure didn't experience that.
>
> Could you please capture the mDNS traffic that happens when you call
> avahi-browse like you did above?

As usual in this kind of situation, I was unable to reproduce it so
far.  Anyway, I'll send the data as soon as I can get to it.

Also, Rhythmbox was indeed running at the same time.

Thanks,
Ludovic.