search

balena-io-experimental / balena-sound

Build a single or multi-room streamer for an existing audio device using a Raspberry Pi! Supports Bluetooth, Airplay and Spotify Connect
https://balena.io/blog/turn-your-old-speakers-or-hi-fi-into-bluetooth-receivers-using-only-a-raspberry-pi/
MIT License
2.39k stars 427 forks source link

Audio service won't update to new release #571

Closed jflann closed 2 years ago

jflann commented 2 years ago

My balenaSound Pi 3 has ceased working again, having issues with the audio service. I've updated to the latest balena OS and pushed a new release from my forked repository which should be even with balena-sound master, the only difference being my docker-compose.yml omits the bluetooth service and enables the upnp service.

multi-room-client repeatedly throws this error: 09.04.22 21:32:55 (-0500) multiroom-client 2022-04-10 02-32-55.644 [Error] (Controller) Error: Connection refused 09.04.22 21:32:55 (-0500) multiroom-client 2022-04-10 02-32-55.644 [Error] (Connection) Error in socket shutdown: Socket not connected 09.04.22 21:32:56 (-0500) multiroom-client 2022-04-10 02-32-56.646 [Error] (Connection) Failed to connect to host '192.168.1.18', error: Connection refused

I believe it's failing to download the audio service image: 09.04.22 21:20:45 (-0500) Downloading delta for image 'registry2.balena-cloud.com/v2/827b932e05af238516a4b213d7bc290e@sha256:7ea17d47cdb90a71a8460c295740070fd5ede841068389f075e3334fbf40d44d' 09.04.22 21:20:45 (-0500) Failed to download image 'registry2.balena-cloud.com/v2/827b932e05af238516a4b213d7bc290e@sha256:7ea17d47cdb90a71a8460c295740070fd5ede841068389f075e3334fbf40d44d' due to '(HTTP code 500) server error - stat /var/lib/docker/overlay2/72f42aacca5fcf99338ff57df90a94d9583295e9924435d56e205a4643d14a67: no such file or directory '

Services eventually settle into this state: image

jflann commented 2 years ago

One more note - when I updated balenaOS, it forced an update to the supervisor. I didn't think to update this separately until today. Updating to 13.0.3 seems to allow all the services to download and update as they should. This seems to have completely resolved the issue.