-
Notifications
You must be signed in to change notification settings - Fork 651
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Librespot mDNS-related error on machine startup #1404
Comments
Just to be sure: This is |
As far as I know, yes. I didn't add any additional parameters to the command. (Sorry, I'm not familiar with the Rust toolchain.) When I'd run that command, it seemed to do a full compile every time. It failed a few times until I'd installed the pkg-config and libasound2-dev packages, then it succeeded. From there I had to copy the binary to Also I forgot to mention the Ubuntu version is 24.04. |
Ok, then this should be using the This seems to be the same as librespot-org/libmdns#50, i.e. some kind of network-not-yet-available issue. Someone would need to investigate what exactly is going on here... Similar to spotifyd, we might also implement a retry feature. What kind of system are you running this on? If it has an MDNS responder running (e.g. Avahi on Linux), you could try building with one of the other zerconf backends, see also https://github.com/librespot-org/librespot/blob/dev/COMPILING.md#zeroconf-library-dependencies # Linux only, no additional dependencies, needs Avahi to be running
cargo build --features with-avahi librespot or # Should work on more systems, requires dns_sd to be available
cargo build --features with-dns-sd librespot |
I have encountered the same issue. |
The linked PR should cause librespot to exit due to this error. That leaves the question open of where the actual issue is coming from, but that is already tracked in librespot-org/libmdns#50. |
Description
Librespot appears to be throwing an mDNS-related error on machine startup when run as a systemd service. This doesn't kill the service, but leaves mDNS broken (so it's not visible in the Spotify app as a playback device).
If I restart the service after startup there is no error, and if I add a 30 sec delay (using
ExecStartPre=/bin/sleep 30
in the service file), it also starts up without an issue.I'm wondering if there's another service dependency that needs to be added to the service file. Or is it possible to have librespot internally retry whatever failed?
Version
0.6.0 - built using
cargo install librespot
Host:
Systemd service file
Log
From
journalctl -u librespot.service
:The text was updated successfully, but these errors were encountered: