avahi daemon erroneously assumes host name conflicts (and causes more trouble then)

Bug #831022 reported by Hadmut Danisch
56
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Avahi
New
Unknown
avahi (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Hi,

i am running the server edition of Ubuntu LTS on a HP Proliant server. That avahi daemon is driving me crazy.

The server is named Server1 , retrieves it's IP address pseudostatically from a DHCP server, and announces several of its services through avahi (e.g. offering print services to iPads, that's why Avahi is needed).

every now and then (not always) avahi daemon claims to have detected a name collision at boot time. It then logs

Aug 22 13:09:40 Server1 avahi-daemon[1520]: Host name conflict, retrying with <Server1-2>

and uses Server1-2 as it's name, causing even the DHCP-Server to apply with a different host name, thus causing a new IP address to be assigned. This avahi daemon is breaking my network structure and does not even tell in the logs, where the conflict came from or what made the daemon believe that there was a conflict.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: avahi-daemon 0.6.25-1ubuntu6.2
ProcVersionSignature: Ubuntu 2.6.32-33.72-server 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-server x86_64
Architecture: amd64
Date: Mon Aug 22 13:24:06 2011
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/tcsh
SourcePackage: avahi

Revision history for this message
Hadmut Danisch (hadmut) wrote :
George Gill (ggilliii10)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in avahi (Ubuntu):
status: New → Confirmed
Revision history for this message
Rene Treffer (treffer+launchpad) wrote :

I get the same problem on my gentoo box. A simple way to reproduce is adding
"127.0.1.1 hostname"
to you /etc/hosts

It looks like avahi will tread nslookup success that does not map to an _assigned_ ip of the local host as a conflict. Not sure about secondary IPs, but I would expect other bugs/reports to be related....

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Bug 1091645 is a similar problem.

Revision history for this message
Jeff (ad-sicks) wrote :

Same here. Hostname in /etc/hosts on Gentoo causes the same problem. net-dns/avahi-0.6.31-r2

Revision history for this message
TJ (tj) wrote :

This is still affecting 18.04, I've added a link to an upstream bug report.

Changed in avahi:
status: Unknown → New
TJ (tj)
Changed in avahi (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Medium
Revision history for this message
Trent Lloyd (lathiat) wrote :

FYI this will not effect DHCP as the hostname change is only used for mDNS and is not used as the system hostname and thus would affect DHCP etc

The cause of this is knwon and hopefully a fix will get done for it soon.. basically its when IP addresses are added then removed too fast. Can also happen with IPv6 because if a global address comes up the link local address is dropped. The code doesn't then handle teh previous announcement coming back into the avahi process and thiunks its a conflict. It's basically a race condition.

Correct upstream issue is https://github.com/lathiat/avahi/issues/117

Changed in avahi:
status: New → Fix Released
Changed in avahi:
status: Fix Released → Unknown
Changed in avahi:
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.