[SOLVED] Avahi daemon isn't starting on a fresh install

[Patatra]

Hi,

On a fresh install of archlinux, system updated and installing xbmc-rbp which install avahi.
But avahi ins't starting on reboot :
$this->bbcode_second_pass_code('', '# systemctl status avahi-daemon
avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled)
Active: failed (Result: start-limit) since jeu. 1970-01-01 01:00:39 CET; 43 years 10 months ago
Process: 205 ExecStart=/usr/bin/avahi-daemon -s (code=exited, status=255)
Main PID: 205 (code=exited, status=255)
Status: "avahi-daemon 0.6.31 exiting."
CGroup: /system.slice/avahi-daemon.service

janv. 01 01:00:39 alarmpi systemd[1]: Started Avahi mDNS/DNS-SD Stack.
janv. 01 01:00:39 alarmpi systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
janv. 01 01:00:39 alarmpi systemd[1]: avahi-daemon.service: main process exited, code=exited, status=255/n/a
janv. 01 01:00:39 alarmpi systemd[1]: Unit avahi-daemon.service entered failed state.
janv. 01 01:00:39 alarmpi systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
janv. 01 01:00:39 alarmpi systemd[1]: avahi-daemon.service start request repeated too quickly, refusing to start.
janv. 01 01:00:39 alarmpi systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
janv. 01 01:00:39 alarmpi systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
janv. 01 01:00:39 alarmpi systemd[1]: avahi-daemon.service start request repeated too quickly, refusing to start.
janv. 01 01:00:39 alarmpi systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
')

$this->bbcode_second_pass_code('', 'nov. 11 13:50:56 alarmpi avahi-daemon[534]: Found user 'avahi' (UID 84) and group 'avahi' (GID 84).
nov. 11 13:50:56 alarmpi avahi-daemon[534]: Successfully dropped root privileges.
nov. 11 13:50:56 alarmpi avahi-daemon[534]: avahi-daemon 0.6.31 starting up.
nov. 11 13:50:56 alarmpi dbus[159]: [system] Successfully activated service 'org.freedesktop.Avahi'
nov. 11 13:50:56 alarmpi avahi-daemon[534]: Successfully called chroot().
nov. 11 13:50:56 alarmpi avahi-daemon[534]: Successfully dropped remaining capabilities.
nov. 11 13:50:56 alarmpi avahi-daemon[534]: Loading service file /services/sftp-ssh.service.
nov. 11 13:50:56 alarmpi avahi-daemon[534]: Loading service file /services/ssh.service.
nov. 11 13:50:57 alarmpi avahi-daemon[534]: Loading service file /services/udisks.service.
nov. 11 13:50:57 alarmpi avahi-daemon[534]: SO_REUSEPORT failed: Protocol not available
nov. 11 13:50:57 alarmpi avahi-daemon[534]: Failed to create server: No suitable network protocol available
nov. 11 13:50:57 alarmpi avahi-daemon[534]: avahi-daemon 0.6.31 exiting.
nov. 11 13:50:57 alarmpi dbus[159]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
nov. 11 13:50:57 alarmpi systemd[1]: Started Avahi mDNS/DNS-SD Stack.
nov. 11 13:50:57 alarmpi systemd[1]: avahi-daemon.service: main process exited, code=exited, status=255/n/a
nov. 11 13:50:57 alarmpi systemd[1]: Unit avahi-daemon.service entered failed state.
nov. 11 13:50:57 alarmpi systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
nov. 11 13:50:57 alarmpi systemd[1]: avahi-daemon.service start request repeated too quickly, refusing to start.
nov. 11 13:50:57 alarmpi systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
nov. 11 13:50:57 alarmpi dbus-daemon[159]: dbus[159]: [system] Successfully activated service 'org.freedesktop.Avahi'
nov. 11 13:50:57 alarmpi dbus-daemon[159]: dbus[159]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
nov. 11 13:50:57 alarmpi avahi-daemon[531]: Process 528 died: No such process; trying to remove PID file. (/var/run/avahi-daemon//pid)')

What's wrong here?

[WarheadsSE]

https://github.com/archlinuxarm/PKGBUILDs/issues/606

[Patatra]

Thanks.
So the workaround is (could be usefull for others) :

$this->bbcode_second_pass_quote('', 'G')o edit /etc/avahi/avahi-daemon.conf

Find the line:
"#disallow-other-stacks=no"
and change to
"disallow-other-stacks=yes"
This flag is apparently what now causes avahi to attempt to use SO_REUSEPORT (and turning it to yes disables this new behavior.) The docs indicate this is some mechanism to accomodate nasty setups with more than one mdns handler on them at the same time.