search

linuxserver / docker-daapd

GNU General Public License v3.0
107 stars 36 forks source link

Log fills with mdns / avahi messages media lib greyed out on Apple Remote (iOS) #47

Closed GerdBlomb closed 3 years ago

GerdBlomb commented 3 years ago

linuxserver.io

Expected Behavior

iPad Remote App should make use of the media libary after succesful pairing

Current Behavior

Pairing with daapd works fine, after that the Icon for the Lib is greyed out in the iPad Apple Remote App and can not be used

Steps to Reproduce

  1. Add Libary on iPad, App seaches for available Libs
  2. daapd raises pairing dialog to input connect numbers
  3. Connection / Pairing works
  4. Libs Icon displayed on iPad, but greyed out and not touchable

Environment

OS: Rapsi Buster latest arm64 CPU arm64 How docker service was installed: Official repos

Command used to create docker container (run/create/compose/screenshot)

s. attached yaml file forked-daapd.zip

docker-compose.zip

Docker logs

s. attached log file zip archiv

Server Version 27.4

The logfile files fills up with the following messags in a 20 sec. schedule:

[2021-04-08 08:52:01] [DEBUG] web: notify callback reason: 11 [2021-04-08 08:52:01] [ LOG] mdns: Avahi state change: Client collision [2021-04-08 08:52:01] [ LOG] mdns: Avahi state change: Client registering [2021-04-08 08:52:22] [ LOG] mdns: Avahi state change: Client collision [2021-04-08 08:52:22] [ LOG] mdns: Avahi state change: Client registering

I've also paired my iPad with Apple Remote App to forked-daapd succesfull with the handshake code, but the lib ist grayed out on the iPad in the list of media libaries. I suppose a relation between this two issues.

The messages appears also in the same sequenz if iPad ist not paired.

avahi service on the host has been disabled (was active, same picture). No difference.

forked-dappd is installed as docker container with host network.

Everything else works fine. I can playback from the webinterface to all my Airplay speakers. All speakers are in place.

Doc G*ggle does not help.

Any hints or tips?

Copied from: https://github.com/owntone/owntone-server/issues/1223

github-actions[bot] commented 3 years ago

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

GerdBlomb commented 3 years ago

After I noticed that the daapd Docker file had grown to over 500 MB, I tried again to analyze what wasn't working.

I found out that I set the host name in docker-compose.yaml.

This led to daapd trying to integrate it again and again. If that doesn't work for daapd, a number to the host name is added and the next attempt is made:

Trying: hostname hostname-1 hostname-2 ... hostname-189

I deleted the hostname entry in the docker-compose.yaml and restarted it via "docker-compose down" / "docker-compose up -d".

The messages disappeared.

EDIT: I would like to suggest to add the information that one should not add a hostname to the docker run or the docker-compose.yaml. I've read that some tools do so in their GUI (on Synology e. g.).

Closed.