Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

AudioBlock startup failure

See original GitHub issue

[nitish] The user is facing issue with audioblock failing to start. Following an excerpt from logs:

Started service 'multiroom-client sha256:87956ab6cef7877439717364cd3d809a19a7021f9414bd88ae6b72cc6d8e7278'
<airplay> Waiting for audioblock to start...
<audio> Waiting for sound supervisor to start
<upnp> Ready for rendering.
<multiroom-client> Starting multi-room client...
<multiroom-client> snapclient v0.23.0
<multiroom-client> Mode: STANDALONE
<multiroom-client> Target snapcast server: 192.168.1.100
<multiroom-client> Multi-room client disabled. Exiting...
<audio> Waiting for sound supervisor to start
<airplay> Waiting for audioblock to start...
Started service 'multiroom-server sha256:3e042c47699c6a8384144164602cd9e2f6a419f74407a483ed74c336f3cd8183'
<multiroom-server> Multi-room server blacklisted for raspberry-pi. Exiting...
<sound-supervisor> Error connecting to audio block - Retry failed: connect ECONNREFUSED 192.168.1.100:4317
<audio> Waiting for sound supervisor to start
<airplay> Waiting for audioblock to start...
Service exited 'multiroom-client sha256:87956ab6cef7877439717364cd3d809a19a7021f9414bd88ae6b72cc6d8e7278'
<audio> Waiting for sound supervisor to start
<airplay> Waiting for audioblock to start...
Service exited 'multiroom-server sha256:3e042c47699c6a8384144164602cd9e2f6a419f74407a483ed74c336f3cd8183'
<audio> Waiting for sound supervisor to start
<airplay> Waiting for audioblock to start...
<audio> Waiting for sound supervisor to start
<airplay> Waiting for audioblock to start...

Issue Analytics

State:
Created 2 years ago
Comments:8 (2 by maintainers)

Top GitHub Comments

1reaction

jwissercommented, Aug 3, 2021

This still occurs on Raspberry Pi 3 (using 64bit OS) with the latest release.

1reaction

tmigonecommented, Apr 20, 2021

This was a bug that has been fixed now (see https://github.com/balenablocks/audio/issues/62 and https://github.com/balenalabs/balena-sound/issues/429).

Anyone reading this, to fix it you’ll need to re-deploy balenaSound to your device, you can do so by clicking the “Deploy with balena” button on this page. Make sure you deploy it to your existing balenaSound application where your device is and not to a newly created application.

Top Results From Across the Web

AudioBlock startup failure · Issue #431 · balena-labs ... - GitHub

[nitish] The user is facing issue with audioblock failing to start. Following an excerpt from logs: Started service 'multiroom-client ...

RPi 3B+ no audio from 3.5mm jack - balena Forums

Here are my logs after a clean boot and trying to play something via ... sound-supervisor Error connecting to audio block - Retry...

Why Startups Fail by Tom Eisenmann - Audiobook - Audible.com

Why Startups Fail ; By: Tom Eisenmann ; Narrated by: Robert Fass ; Critic Reviews. “Launching and scaling a startup is like a...

M-Class Quick Startup Guide - SAS [Sierra Automated Systems]

M-Class Startup Guide ... failure caused beyond the control of Sierra Automated Systems & Engineering Corporation ... to Audio Block 1 Right side,...

dQC - River Thames Conditions

Thrilling spine coaster star, Droidbox imx6 problems, Adobe illustrator brush pack, ... Caryn elementary lunch menu, Brewery startup, Rozhovor s bohom csfd, ...