Skip to content
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

sound-supervisor standard_init_linux.go:219: exec user process caused: exec format error #637

Open
Galster opened this issue Apr 6, 2023 · 6 comments

Comments

@Galster
Copy link

Galster commented Apr 6, 2023

Hello!

I deployed with balena on my raspi2 and sound-supervisor container wasn't start.

Log:

 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 sound-supervisor  standard_init_linux.go:219: exec user process caused: exec format error
Restarting service 'sound-supervisor sha256:cb53f3535194f84bd5b0e004983544009d8f7c14e01964a9332d8e32d60e2e90'
Service exited 'sound-supervisor sha256:cb53f3535194f84bd5b0e004983544009d8f7c14e01964a9332d8e32d60e2e90'
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80

Device health check:

check_service_sound-supervisor 
 Failed	User service 'sound-supervisor' is restarting unexpectedly, count: 224

How can I fix it?

@ruebe5w
Copy link

ruebe5w commented Apr 7, 2023

Exactly the same problem here with Raspberry 3

@ruebe5w
Copy link

ruebe5w commented Apr 7, 2023

I think #634 (comment) is also the same problem

@Galster
Copy link
Author

Galster commented Apr 8, 2023

I managed to make it work by changing line #14 in balena-sound/core/sound-supervisor/Dockerfile.template to

FROM balenalib/%%BALENA_ARCH%%-alpine-node:14

RichardPatterson added a commit to RichardPatterson/balena-sound that referenced this issue Apr 23, 2023
@adsoccer5
Copy link

I understand but how does one do this on windows using the terminal host OS (On balenca cloud /dashboard). I having trouble finding these folders?

@ghost
Copy link

ghost commented May 18, 2023

@adsoccer5 Just figured this out. I don't really have any experience with balena-cloud or GitHub but got there in the end. Hopefully this helps.

  • Download BalenaCLI - Google it, I can't link straight to the .exe
  • Download the balena-sound-master branch that RichardPatterson submitted the fix to. Click the 'Update Dockerfile.template' link above, click 'Browse files' in the top right, click the green 'Code' button and 'Download ZIP'.
  • Install balenaCLI and extract the balena-sound-master.zip file
  • Open a cmd prompt and run 'balena login', web browser launches and takes you to the balenaCloud Login
  • cd to the balena-sound-master folder that you extracted previously, probably 'cd C:\Users<username>\Downloads\balena-sound-master
  • Run 'balena push <balenaCloud_username>/balena-sound'
  • Wait for the compile to complete, it should then be pushed to your balenaOS device automatically.

@alanb128
Copy link
Contributor

alanb128 commented Jun 5, 2023

This should now be fixed...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants