Addon won't start in combination with Home Assistant OS 5.8 #22
Comments
|
I can confirm this issue as I am running into this as well. |
|
I have this aswell |
|
Good catch @Cludch, looks like they removed avahi from the host. That's going to break a whole bunch of stuff .. Ideally I'd say let's just make another addon with avahi-daemon and So I guess that just leaves disabling mdns altogether, I've just pushed a change for that, can someone try rebuilding the addon and see if that helps ? |
|
I just did an uninstall and re-installed the add-on. However, the same issue still comes up. |
|
Right, to pull the new version you need to make sure you run a refresh on the repo page of hassio, or it won't pull the new files. |
|
Yeah, I just remembered that and did a refresh. However, no change. |
|
I just did the reinstall with reload on the add-on's store page and it still seems to be looping |
|
Hello, Just checked that I have the last version, with the |
|
Indeed I see the same behaviour after a rebuild of the addon. Hope you are able to find the cause @Ulrar 💪 |
|
Hi, I'm currently on Home Assistant OS 5.9 and the issue persists. |
|
Unfortunately I'm not sure there's a solution, looks like forked-daapd
depends on avahi even if it's not anouncing itself. I believe it's needed
to discover chromecast and airplay devices so it makes sense.
In any case I don't know what we can do here, I don't think this addon is
possible to fix.
…On Thu 31 Dec 2020, 21:10 Pietro, ***@***.***> wrote:
Hi, I'm currently on Home Assistant OS 5.9 and the issue persists.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGVHTYDZUXTJSEGLYN4UOTSXTSDBANCNFSM4U34QVEA>
.
|
|
Home Assistant OS 5 moved to systemd-resolved to resolve mDNS. Currently it doesn't announce services, but it can act as a DNS-SD responder. So is/was daapd using the hosts AVAHI? |
|
That's correct, forked-daapd has a hard dependency on avahi so it was using
the host's one through dbus.
Unfortunately adding avahi in the container wouldn't help since it'd be
announcing the wrong IP, it has to run on the host.
…On Mon 4 Jan 2021, 23:21 Stefan Agner, ***@***.***> wrote:
Home Assistant OS 5 moved to systemd-resolved to resolve mDNS. Currently
it doesn't announce services, but it can act as a DNS-SD responder. So
is/was daapd using the hosts AVAHI?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGVHT76MG5ZCK5LLDZSCGDSYJEN5ANCNFSM4U34QVEA>
.
|
|
Hi, I don't have hassos anymore so I can't test this, but I've pushed a new |
|
Hey, I just tested the |
|
Looks like you need a special config file on the dbus side (so on the host) to be allowed to register a service, like avahi tries to do on startup. I'm guessing this is what's failing here, hard to be sure without seeing the host logs but that would make sense. So unfortunately short of running something like |
|
Been fighting with this for the past 72 hrs. Wanted to install and control some Airport Express Speakers. Been going mad - now i know why thanks |
Tried what you suggested, no luck. dbus-1 is read only and couldn't figure out how to populate that file. Any chance you can find out how the guys at linuxserver.io did it all in one container?: https://github.com/linuxserver/docker-daapd Thanks for the addon. I wish Hass would have kept the daemon around for legacy apps. |
The linuxserver.io docker forked-daapd container runs ok on hassos, not sure why it would be different than this addon? |
I tried using it on HassOS with the Custom component for the announcements and it didn't seem to work. Maybe I did something wrong? |
|
Hi, I noticed you added an Avahi Daemon Addon to try to solve this issue. Sadly I can't get it to start either: |
|
Yes, the avahi addon won't work because it requires config on the host
dbus, which isn't present.
I'll take a look at the other containers tomorrow, I suspect it just has
avahi in the container itself and doesn't map to the host dbus, and
probably runs on the host network. I suppose that'll work as long as you
have only one addon that requires avahi, not ideal but better than nothing,
we might give that a try
…On Tue 26 Jan 2021, 20:58 Pietro, ***@***.***> wrote:
Hi, I noticed you added an Avahi Daemon Addon to try to solve this issue.
Sadly I can't get it to start either:
[17:56:24] INFO: Starting the avahi daemon...
Found user 'avahi' (UID 102) and group 'avahi' (GID 102).
Successfully dropped root privileges.
avahi-daemon 0.7 starting up.
WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
dbus_bus_get_private(): Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
WARNING: Failed to contact D-Bus daemon.
avahi-daemon 0.7 exiting.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGVHT5NLF43SXJUUUEMGZ3S34UI3ANCNFSM4U34QVEA>
.
|
|
Interesting that addons would have conflict if more than one used avahi. |
|
Homebridge (HomeKit) no longer uses Avahi from what I gather. That's why we're in the situation we are in now. |
|
As I suspected the linuxserver.io container runs on host network mode, and is running avahi and dbus directly. I've also removed the avahi addon since that wasn't working. |
|
Hello, I was asked to install your forked DAAP add on and report my findings over at the HA forums. I received this error message upon installation, but it later seemed to install OK:
With the add-on running I was unable to access the web-ui either through the sidebar (“502: Bad Gateway”) or via http://[ip address]:3688 or via http://[ip address]:3689 (ERR_CONNECTION_REFUSED). Assume the port for the web-ui is set to 3688: I saw this in the add-on log: I am running Home Assistant on core-2021.1.5 and supervisor-2021.01.7. Hope that is useful. Thanks for the add-on. |
|
Hello @Ulrar, finally got some time to test the new version: First it complains about a non existing update and a parse error: Then it fails to start and keeps trying indefinitely: |
|
I did some troubleshooting on this myself and found the following: This was even with changing the add-on to unprotected full access. Command was run from within the container itself. I'm guessing there is some configuration missing for d-bus, but I'm unfamiliar with these system processes and can't be sure. If there is something someone would like me to try, let me know and I'll give it a run. Hope this helps in some way. Look forward to getting it working again. |
|
I have the same forked-daapd: client.c:791: avahi_client_errno: Assertion client' failed.` loop as stated above by @pzuccar and @steveof2620 Willing to do any tests or help out in any way to get this working again. Let me know what you need. System: (amd64 / qemux86-64) Operating System |
|
I have the same trouble as above. Using Raspberry Pi 4 4GB with HassOS 5.8 (will soon update to 5.11) and Core 2021.2.3 This is the startup log of the addon: After that i get the same avahi_client_errno: Assertion client' failed log. This just keeps repeating: |
|
Having exactly same issue |
|
Hi all, Sorry about the delay, I'm quite busy these days and since I don't actually use this addon myself anymore it tends to fall at the bottom of my todo. Can anyone check if dbus and avahi are actually starting with the latest version ? Just docker exec into it and run a thanks |
|
There's no ps in this container. What I could get is this: |
|
Thanks, that's very helpful. So it looks like neither dbus nor avahi are starting, I'll look into why that might be. |
|
Thanks Ulrar I appreciate you looking into this. If there is anything you need tested or other questions please let us know! |
|
Just following up on this issue to see if anyone has found any work arounds or assistance in getting this working. |
|
I don't have a work around for this particular add on, but I do have forked-daapd up and running on home assistant. You'll need to install the docker add-on first though. The instructions are here if you're interested: |
|
Excellent! I`ll give that a shot here in the next day and update. Thanks for the info. |
Yes, this way works! |
Thanks, that works indeed. Not as nice as an addon, but at least forked-daapd works again! |
|
Same issue here, looking forward to a fix :) |
|
Hi all, I have a newborn at home so to be honest I don't expect this getting much attention any time soon, but I'll be happy to merge PRs or even point to another repo if someone wants to take over ! |
Since I upgraded to Home Assistant OS 5.8, the addon can't succesfully start anymore. I hope you can assist, thanks in advance!
[2020-12-15 09:02:28] [ LOG] lib: Library init scan completed in 7 sec (200 changes) [ LOG] lib: Library init scan completed in 7 sec (200 changes) [2020-12-15 09:02:29] [ LOG] main: Cache deinit [ LOG] main: Cache deinit [ LOG] main: Worker deinit [ LOG] main: Database deinit [2020-12-15 09:02:29] [ LOG] main: Worker deinit [2020-12-15 09:02:29] [ LOG] main: Database deinit [2020-12-15 09:02:29] [ LOG] main: mDNS deinit [2020-12-15 09:02:29] [ LOG] main: Exiting. [ LOG] main: mDNS deinit [ LOG] main: Exiting. [09:02:29] INFO: Starting the forked-daapd Server... [2020-12-15 09:02:29] [ LOG] main: Forked Media Server Version 27.2 taking off [2020-12-15 09:02:29] [ LOG] main: Built with: [ LOG] main: Forked Media Server Version 27.2 taking off [2020-12-15 09:02:29] [ LOG] main: - ffmpeg [ LOG] main: Built with: [2020-12-15 09:02:29] [ LOG] main: - iTunes XML [ LOG] main: - ffmpeg [2020-12-15 09:02:29] [ LOG] main: - Spotify [ LOG] main: - iTunes XML [2020-12-15 09:02:29] [ LOG] main: - LastFM [ LOG] main: - Spotify [2020-12-15 09:02:29] [ LOG] main: - Chromecast [ LOG] main: - LastFM [2020-12-15 09:02:29] [ LOG] main: - MPD [ LOG] main: - Chromecast [2020-12-15 09:02:29] [ LOG] main: - Device verification [ LOG] main: - MPD [2020-12-15 09:02:29] [ LOG] main: - Websockets [ LOG] main: - Device verification [2020-12-15 09:02:29] [ LOG] main: - ALSA [ LOG] main: - Websockets [2020-12-15 09:02:29] [ LOG] main: - Pulseaudio [ LOG] main: - ALSA [2020-12-15 09:02:29] [ LOG] main: - Webinterface [ LOG] main: - Pulseaudio [ LOG] main: - Webinterface [ LOG] main: - Regex [2020-12-15 09:02:29] [ LOG] main: - Regex [2020-12-15 09:02:29] [ LOG] main: mDNS init [ LOG] main: mDNS init [ LOG] mdns: Avahi state change: Client connecting [ LOG] db: Configured to use database file '/share/forked-daapd/cache/songs3.db' [2020-12-15 09:02:29] [ LOG] mdns: Avahi state change: Client connecting [2020-12-15 09:02:29] [ LOG] db: Configured to use database file '/share/forked-daapd/cache/songs3.db' [ LOG] db: Now vacuuming database, this may take some time... [2020-12-15 09:02:29] [ LOG] db: Now vacuuming database, this may take some time... [ LOG] db: Database OK with 1001 active files and 6 active playlists [2020-12-15 09:02:30] [ LOG] db: Database OK with 1001 active files and 6 active playlists [ LOG] mdns: Failed to create service browser: Bad state [ LOG] raop: Could not add mDNS browser for AirPlay devices [2020-12-15 09:02:30] [ LOG] mdns: Failed to create service browser: Bad state [2020-12-15 09:02:30] [ LOG] raop: Could not add mDNS browser for AirPlay devices [ LOG] mdns: Failed to create service browser: Bad state [ LOG] cast: Could not add mDNS browser for Chromecast devices [2020-12-15 09:02:30] [ LOG] mdns: Failed to create service browser: Bad state [2020-12-15 09:02:30] [ LOG] cast: Could not add mDNS browser for Chromecast devices [ LOG] scan: Scanned 200 files... [2020-12-15 09:02:30] [ LOG] scan: Scanned 200 files... [ LOG] mdns: Failed to create service browser: Bad state [FATAL] remote: Could not browse for Remote services [FATAL] main: Remote pairing service failed to start [ LOG] main: MPD deinit [2020-12-15 09:02:30] [ LOG] mdns: Failed to create service browser: Bad state [2020-12-15 09:02:30] [FATAL] remote: Could not browse for Remote services [2020-12-15 09:02:30] [FATAL] main: Remote pairing service failed to start [2020-12-15 09:02:30] [ LOG] main: MPD deinit [ LOG] main: HTTPd deinit [2020-12-15 09:02:30] [ LOG] main: HTTPd deinit [ LOG] scan: Scanned 400 files... [2020-12-15 09:02:31] [ LOG] scan: Scanned 400 files... [ LOG] scan: Scanned 600 files... [2020-12-15 09:02:31] [ LOG] scan: Scanned 600 files... [2020-12-15 09:02:31] [ LOG] main: Player deinit [ LOG] main: Player deinit [2020-12-15 09:02:32] [ LOG] scan: Scanned 800 files... [ LOG] scan: Scanned 800 files... [2020-12-15 09:02:32] [ LOG] scan: Scanned 1000 files... [ LOG] scan: Scanned 1000 files... [2020-12-15 09:02:32] [ LOG] main: Library scanner deinit [ LOG] main: Library scanner deinit [2020-12-15 09:02:32] [ LOG] spotify: No spotify refresh token found [ LOG] spotify: No spotify refresh token found [ LOG] spotify: Spotify webapi token refresh failed. In order to use the web api, authorize forked-daapd to access your saved tracks by visiting http://forked-daapd.local:3689 [2020-12-15 09:02:32] [ LOG] spotify: Spotify webapi token refresh failed. In order to use the web api, authorize forked-daapd to access your saved tracks by visiting http://forked-daapd.local:3689 [2020-12-15 09:02:32] [ LOG] lib: Library init scan completed in 2 sec (1 changes) [ LOG] lib: Library init scan completed in 2 sec (1 changes) [ LOG] main: Cache deinit [2020-12-15 09:02:33] [ LOG] main: Cache deinit [2020-12-15 09:02:33] [ LOG] main: Worker deinit [ LOG] main: Worker deinit [2020-12-15 09:02:33] [ LOG] main: Database deinit [ LOG] main: Database deinit [ LOG] main: mDNS deinit [2020-12-15 09:02:33] [ LOG] main: mDNS deinit [2020-12-15 09:02:33] [ LOG] main: Exiting. [ LOG] main: Exiting.And the above seems to repeat itself indefinitely.
The text was updated successfully, but these errors were encountered: