avahi daemon erroneously assumes host name conflicts (and causes more trouble then)
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
ProcVersionSign
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
description: | updated |
Changed in avahi: | |
status: | Unknown → New |
Changed in avahi (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → Medium |
Changed in avahi: | |
status: | New → Fix Released |
Changed in avahi: | |
status: | Fix Released → Unknown |
Changed in avahi: | |
status: | Unknown → New |
Status changed to 'Confirmed' because the bug affects multiple users.