- This topic has 27 replies, 6 voices, and was last updated 4 years, 11 months ago by
.
-
OK done that, exactly same result. Shareport is not in use anyway at the moment but may be needed when box is deployed so I will test with Squeezelite and Shareport on Auto Start after we resolve the Spotify Connect alone. Any other info that would be helpful ?
===============================================================================================================================================
DEBUG information after boot
———————————————————————————————————————————————–
#### Librespot Output ####
INFO:librespot: librespot cc9dba8 (2017-03-26). Built on 2017-07-17. Build ID: 8zQE3Bpb
WARN:librespot::apresolve: Failed to resolve Access Point: HTTP error
WARN:librespot::apresolve: Using fallback „ap.spotify.com:80“
INFO:librespot::session: Connecting to AP „ap.spotify.com:80“
thread ‚main‘ panicked at ‚calledResult::unwrap()on anErrvalue: Error { repr: Custom(Custom { kind: Other, error: StringError(„failed to lookup address information: Name or service not known“) }) }‘, /checkout/src/libcore/result.rs:859
note: Run withRUST_BACKTRACE=1for a backtrace.#### Librespot Command Line Options ####
error: Required option ’name‘ missing.
Usage: /opt/spotifyconnect/librespot [options]
———————————————————————————————————————————————–FYI DEBUG Information when manually started, still not started Squeezelite at this point although there have been no problems manually starting Spotify Connect when Squeezelite running in the past
===============================================================================================================================================
DEBUG Information
———————————————————————————————————————————————–
#### Librespot Output ####
INFO:librespot: librespot cc9dba8 (2017-03-26). Built on 2017-07-17. Build ID: 8zQE3Bpb
INFO:librespot::session: Connecting to AP „lon6-accesspoint-a29.ap.spotify.com:4070“
INFO:librespot::session: Authenticated as „theonlyfoz“ !
INFO:librespot::audio_backend::alsa: Using alsa sink
INFO:librespot::session: Country: „GB“#### Librespot Command Line Options ####
error: Required option ’name‘ missing.
Usage: /opt/spotifyconnect/librespot [options]
———————————————————————————————————————————————–I did a complete rebuild from recently downloaded image from Max2Play. I think I need to do more testing. I had a scenario all tagged out, which I had detailed here, which has just been shown to be wrong when I rebooted again. Will post when I am more confident of repeatable results.
Thanks
Hmmmm, I’ve not been aware of the service falling over once running except as per my posting re if another device already has control of the sound card when you start to send from spotify (Spotify Connect service crashes if used when Squeezelite player not paused), but then I have not been using it heavily. Out of interest, and not wishing to interfere with the process of the guys here, does the Spotify Connect page say the service has stopped running when you say it stops working and if so does the DEBUG information on the Spotify Connect page tell you anything AFTER the service has crashed ?
I have not been massively pushing the Auto Start testing but have had no failures since disabling Activate WPS on Boot on the WiFi/LAN page, even on a Pi 2 which has no wifi dongle attached.
You must be logged in to reply to this topic.