Hi. I have a problem with not all services downloads.
airplay, multiroom client and multiroom service is running but audio, blutooth, sound supervisor, spotify and upnp starts downloading but never finish it, instead restarts download over and over again.
Balena ver 2.47.0 rev1. 64 bit OS.
The sd card is a sandisk extreme pro 64GB.
Etcher verified ok.
On this setup, pi + card, I did run another project (not balena) without any problems.
Any idea?
Hi, can you check supervisor logs?
journalctl -f -a -u resin-supervisor --no-pager
root@33e1c06:~# journalctl -f -a -u resin-supervisor --no-pager
– Logs begin at Tue 2020-12-22 07:32:24 UTC. –
Dec 22 08:47:24 33e1c06 systemd[1]: resin-supervisor.service: Killing process 29062 (resin-superviso) with signal SIGABRT.
Dec 22 08:47:24 33e1c06 systemd[1]: resin-supervisor.service: Killing process 29063 (resin-superviso) with signal SIGABRT.
Dec 22 08:47:24 33e1c06 systemd[1]: resin-supervisor.service: Killing process 29064 (balena) with signal SIGABRT.
Dec 22 08:47:24 33e1c06 systemd[1]: resin-supervisor.service: Main process exited, code=killed, status=6/ABRT
Dec 22 08:48:55 33e1c06 systemd[1]: resin-supervisor.service: State ‘stop-final-sigterm’ timed out. Killing.
Dec 22 08:48:55 33e1c06 systemd[1]: resin-supervisor.service: Killing process 28781 (balena) with signal SIGKILL.
Dec 22 08:48:55 33e1c06 systemd[1]: resin-supervisor.service: Failed with result ‘watchdog’.
Dec 22 08:49:28 33e1c06 resin-supervisor[29292]: resin_supervisor
Dec 22 08:49:58 33e1c06 resin-supervisor[29385]: active
Dec 22 08:50:45 33e1c06 resin-supervisor[29423]: error during connect: Get http://%2Fvar%2Frun%2Fbalena-engine.sock/v1.39/images/registry2.balena-cloud.com/v2/beeaf32daff5ac14d8e6e65f9150d636:latest/json: readLoopPeekFailLocked: read unix @->/var/run/balena-engine.sock: read: connection reset by peer
@stenp can you also provide balena engine logs?
journalctl --no-pager -eu balena-engine
root@33e1c06:~# journalctl --no-pager -eu balena-engine
– Logs begin at Tue 2020-12-22 08:27:32 UTC, end at Tue 2020-12-22 09:50:11 UTC. –
– No entries –
root@33e1c06:~#
I saw this in the log window in the dashboard:
22.12.20 10:54:00 (+0100) Warning: Suppressed 405 message(s) due to slow reading
Can that give a clue?
@karaxuna the OS version 2.47.0 seems quite old, is that a problem?
I added another device, an RPi 1, connected ethernet and that did download and activated all service som I will get a new mSD card and try again another day so I will delete this device and report back if it will function with new card. Cheers for now and thanks a lot for help so far.
Hi @stenp, the OS version is old, and although we recommend upgrading whenever possible, it doesn’t necessarily explain the behavior you are seeing. If you still have the device online maybe you can enable support so we can take a look? Thank you
Thanks a lot for your offer to help. I have deleted the application and will try again with another sd card next week. I plan to install bare raspian to check if there is any apparent problem with the pi itself. Let me report to this tread then.
Yes, please let us know of your findings! Thank you!
There was a problem with the SD card. I have now two fresh cards and 2 RPi 3B+ running.
But I get no sound. All devices work and I can connect with Spotify and see in the command window that the track is playing but no sound. I am connected to a pair of B&W MM1 speakers using the AUX input. I have the other connected to a JBL Flip 3 AUX input. It is possible that I have missed something in the setup but I find no clue in the instructions.
Hi @stenp, are both devices under the same application?
To narrow down the problem space, it’d help to start simpler and try out 1 device at a time in the same application (assuming that multi-room feature of balenaSound is causing issues here).
Can you run Device Diagnostics on these devices and note if you see any errors?
As my teammate asked earlier, can you check the supervisor logs again?
journalctl -f -a -u resin-supervisor --no-pager
I had a short powerdown so both RPi:s shut off. I will setup a new app and start fresh with only one device and select 32bit instead of 64bit as I read some info that might be a safer path to go.
Thanks a lot for your assistance, it is much appreciated. The problem is now solved. I set up a new application and a device with 32bit OS on and that did work from start. I then added another device and that did connect automatically as soon as it was updated.