starred/librespot

Fork 0

mirror of https://github.com/librespot-org/librespot.git synced 2026-04-27 08:15:50 +03:00

[GH-ISSUE #1106] Immediately shutting down discovery server #516

New issue

Closed

opened 2026-02-27 19:31:04 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 19:31:04 +03:00

Owner

Originally created by @juup on GitHub (Jan 21, 2023).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1106

Installed raspotify on a Raspberry Pi4 with osmc based on Debian.

When I launch librespot -n "Librespot Speaker" -b 160 -v zeroconf immediately stops and the device is not discoverable. How can I found out why?

[2023-01-21T08:40:36Z INFO  librespot] librespot 0.4.2 6db2180 (Built on 2023-01-14, Build ID: htFgTqU5, Profile: release)
[2023-01-21T08:40:36Z TRACE librespot] Command line argument(s):
[2023-01-21T08:40:36Z TRACE librespot]          n "Librespot Speaker"
[2023-01-21T08:40:36Z TRACE librespot]          b "160"
[2023-01-21T08:40:36Z TRACE librespot]          v
[2023-01-21T08:40:36Z DEBUG librespot_discovery::server] Zeroconf server listening on 0.0.0.0:34371
[2023-01-21T08:40:36Z DEBUG librespot_discovery::server] Shutting down discovery server

Originally created by @juup on GitHub (Jan 21, 2023). Original GitHub issue: https://github.com/librespot-org/librespot/issues/1106 Installed raspotify on a Raspberry Pi4 with osmc based on Debian. When I launch **librespot -n "Librespot Speaker" -b 160 -v** zeroconf immediately stops and the device is not discoverable. How can I found out why? ``` [2023-01-21T08:40:36Z INFO librespot] librespot 0.4.2 6db2180 (Built on 2023-01-14, Build ID: htFgTqU5, Profile: release) [2023-01-21T08:40:36Z TRACE librespot] Command line argument(s): [2023-01-21T08:40:36Z TRACE librespot] n "Librespot Speaker" [2023-01-21T08:40:36Z TRACE librespot] b "160" [2023-01-21T08:40:36Z TRACE librespot] v [2023-01-21T08:40:36Z DEBUG librespot_discovery::server] Zeroconf server listening on 0.0.0.0:34371 [2023-01-21T08:40:36Z DEBUG librespot_discovery::server] Shutting down discovery server ```

kerem

2026-02-27 19:31:04 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 19:31:05 +03:00

Author

Owner

@kingosticks commented on GitHub (Jan 21, 2023):

That log message is wrong and needs fixing, it prints as soon as the server starts. It does not actually mean the discovery server is shutting down yet!

If you are unable to see librespot in your Spotify client apps then it's a different problem.

@kingosticks commented on GitHub (Jan 21, 2023): That log message is wrong and needs fixing, it prints as soon as the server starts. It does not actually mean the discovery server is shutting down yet! If you are unable to see librespot in your Spotify client apps then it's a different problem.

kerem commented

2026-02-27 19:31:05 +03:00

Author

Owner

@juup commented on GitHub (Jan 21, 2023):

Ok, so how can I find out what's the problem?

If I'm running avahi-browse -at on another PC I get
+ enp38s0 IPv4 raspotify (osmc) _spotify-connect._tcp local
But on the same PC Spotify client doesn't find it.

@juup commented on GitHub (Jan 21, 2023): Ok, so how can I find out what's the problem? If I'm running **avahi-browse -at** on another PC I get `+ enp38s0 IPv4 raspotify (osmc) _spotify-connect._tcp local` But on the same PC Spotify client doesn't find it.

kerem commented

2026-02-27 19:31:05 +03:00

Author

Owner

@juup commented on GitHub (Jan 21, 2023):

Ok, so how can I find out what's the problem?

If I'm running avahi-browse -at on another PC I get
+ enp38s0 IPv4 raspotify (osmc) _spotify-connect._tcp local
But on the same PC the Spotify client doesn't find it.

@juup commented on GitHub (Jan 21, 2023): Ok, so how can I find out what's the problem? If I'm running **avahi-browse -at** on another PC I get `+ enp38s0 IPv4 raspotify (osmc) _spotify-connect._tcp local` But on the same PC the Spotify client doesn't find it.

kerem commented

2026-02-27 19:31:05 +03:00

Author

Owner

@roderickvd commented on GitHub (Jan 21, 2023):

Closing but feel free to continue on the Gitter chat: https://gitter.im/librespot-org/spotify-connect-resources

Other than that cosmetic thing with the erroneous message, this is a network configuration thing and most likely no librespot bug.

@roderickvd commented on GitHub (Jan 21, 2023): Closing but feel free to continue on the Gitter chat: https://gitter.im/librespot-org/spotify-connect-resources Other than that cosmetic thing with the erroneous message, this is a network configuration thing and most likely no librespot bug.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/librespot#516

No description provided.

Rows
Columns