Avahi daemon won't start

snap
1 
$ journalctl -u snap.avahi.daemon.service
Dec 14 04:26:59 pineview systemd[1]: Started Service for snap application avahi.daemon.
Dec 14 04:26:59 pineview avahi.daemon[8304]: mkdir("/run/avahi-daemon/"): Permission denied
Dec 14 04:26:59 pineview systemd[1]: snap.avahi.daemon.service: Main process exited, code=exited, status=255/n/a
Dec 14 04:26:59 pineview systemd[1]: snap.avahi.daemon.service: Failed with result 'exit-code'.
Dec 14 04:26:59 pineview systemd[1]: snap.avahi.daemon.service: Service hold-off time over, scheduling restart.
Dec 14 04:26:59 pineview systemd[1]: snap.avahi.daemon.service: Scheduled restart job, restart counter is at 5.
Dec 14 04:26:59 pineview systemd[1]: Stopped Service for snap application avahi.daemon.
Dec 14 04:26:59 pineview systemd[1]: snap.avahi.daemon.service: Start request repeated too quickly.
Dec 14 04:26:59 pineview systemd[1]: snap.avahi.daemon.service: Failed with result 'exit-code'.
Dec 14 04:26:59 pineview systemd[1]: Failed to start Service for snap application avahi.daemon.

Ubuntu 18.04.1 LTS

What do I do from here? Thanks for the help.

2

@ondra would you shed some light on this one?

3

@Lin-Buo-RenI have now created pull request to fix this,
https://github.com/snapcore/snapd/pull/6325
let’s see if it goes through

1 Like
4

I am experiencing the exact same problem, but on Ubuntu Core 18. The GitHub PR linked above seems to target “classic systems”. I assume that does not include Ubuntu Core 18?

5

That snap works fine on UbuntuCore18 but does not on my Desktop. That is problematic since I have a snap that needs to depend on avahi snap to broadcast and has to work on both UbuntuCore and classic.

Is there a way I can bundle avahi in my project and make it write the sock in a “snap safe” location ?

@ondra, any hints here would help.