Balena Sound not initialising on Rpi 3B+

Product support
1

I’ve flashed 2.53.9r1 onto a 3B+ and while it seemingly boots and connects to the VPN without any issues (even displaying the Balena logo on the LCD) the logs never move past the following:

24.08.20 18:59:06 (+0100) Supervisor starting
24.08.20 18:59:06 (+0100) Applying configuration change 
{"SUPERVISOR_POLL_INTERVAL":"900000","SUPERVISOR_DELTA_VERSION":"3"}
24.08.20 18:59:06 (+0100) Applied configuration change 
{"SUPERVISOR_POLL_INTERVAL":"900000","SUPERVISOR_DELTA_VERSION":"3"}
24.08.20 18:59:07 (+0100) Creating network 'default'
24.08.20 18:59:07 (+0100) Applying configuration change {"SUPERVISOR_DELTA":"1"}
24.08.20 18:59:07 (+0100) Applied configuration change {"SUPERVISOR_DELTA":"1"}

Rebooting yields the following

24.08.20 19:37:34 (+0100) Rebooting
27.07.20 14:02:20 (+0100) Supervisor starting

No services download. Please can someone suggest what I might be doing wrong?
Thanks in advance!

4

Hey @infonut it sounds like the supervisor is not running correctly. Can you run the device diagnostic on this device and see what it shows? Also pulling logs from the supervisor by opening a webterminal to hostOS and running journalctl -u resin-supervisor --no-pager will also help debugging.

6

Hi @shaunmulligan thanks for responding!

Jul 27 13:02:12 7e8013e resin-supervisor[1701]: resin_supervisor
Jul 27 13:02:12 7e8013e resin-supervisor[1728]: active
Jul 27 13:02:14 7e8013e resin-supervisor[1731]: REGISTRY_ENDPOINT has changed!
Jul 27 13:02:14 7e8013e resin-supervisor[1731]: Container config has changed!
Jul 27 13:02:14 7e8013e resin-supervisor[1731]: resin_supervisor
Jul 27 13:02:20 7e8013e resin-supervisor[1731]: [info]    Supervisor v11.9.9 starting up...
Jul 27 13:02:20 7e8013e resin-supervisor[1731]: [info]    Setting host to discoverable
Jul 27 13:02:20 7e8013e resin-supervisor[1731]: [warn]    Invalid firewall mode: . Reverting to state: off
Jul 27 13:02:20 7e8013e resin-supervisor[1731]: [info]    🔥 Applying firewall mode: off
Jul 27 13:02:20 7e8013e resin-supervisor[1731]: [debug]   Starting logging infrastructure
Jul 27 13:02:20 7e8013e resin-supervisor[1731]: [info]    Starting firewall
Jul 27 13:02:20 7e8013e resin-supervisor[1731]: [success] 🔥 Firewall mode applied
Jul 27 13:02:20 7e8013e resin-supervisor[1731]: [debug]   Starting api binder
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [event]   Event: Supervisor start {}
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [debug]   Performing database cleanup for container log timestamps
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [info]    Previous engine snapshot was not stored. Skipping cleanup.
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [debug]   Handling of local mode switch is completed
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [debug]   Connectivity check enabled: true
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [debug]   Starting periodic check for IP addresses
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [info]    Reporting initial state, supervisor version and API info
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: (node:1) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [info]    Waiting for connectivity...
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [debug]   Skipping preloading
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [info]    Starting API server
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [info]    Supervisor API successfully started on port 48484
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [info]    Applying target state
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [debug]   Ensuring device is provisioned
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [debug]   Starting current state report
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [debug]   Starting target state poll
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [debug]   Finished applying target state
Jul 27 13:02:21 7e8013e resin-supervisor[1731]: [success] Device state apply success
Jul 27 13:02:22 7e8013e resin-supervisor[1731]: [info]    Applying target state
Jul 27 13:02:22 7e8013e resin-supervisor[1731]: [debug]   Finished applying target state
Jul 27 13:02:22 7e8013e resin-supervisor[1731]: [success] Device state apply success
Aug 24 18:38:33 7e8013e resin-supervisor[1731]: [info]    Internet Connectivity: OK
Aug 24 18:38:43 7e8013e resin-supervisor[1731]: [info]    Waiting for connectivity...
Aug 24 18:38:53 7e8013e resin-supervisor[1731]: [info]    Internet Connectivity: OK
Aug 24 18:43:18 7e8013e resin-supervisor[1731]: [api]     GET /v1/healthy 200 - 18.955 ms
Aug 24 18:48:19 7e8013e resin-supervisor[1731]: [api]     GET /v1/healthy 200 - 6.380 ms
Aug 24 18:48:21 7e8013e resin-supervisor[1731]: [debug]   Attempting container log timestamp flush...
Aug 24 18:48:21 7e8013e resin-supervisor[1731]: [debug]   Container log timestamp flush complete
7

That all looks correct and seems to be running fine. Are there any images on the device? run balena-engine images . Additionally from the diagnostics page change you paste both the target and current supervisor config

8

Thanks for your help.
Here’s balena-engine images

REPOSITORY                  TAG                 IMAGE ID            CREATED             SIZE
balena/armv7hf-supervisor   v11.9.9             c3a05ab1b257        4 weeks ago         62.7MB
balena-healthcheck-image    latest              851163c78e4a        7 months ago        4.85kB

status

{
  "api_port": 48484,
  "ip_address": "192.168.0.94",
  "os_version": "balenaOS 2.53.9+rev1",
  "mac_address": "",
  "supervisor_version": "11.9.9",
  "update_pending": false,
  "update_failed": false,
  "update_downloaded": false
}

and target state

{
  "local": {
    "name": "damp-sky",
    "config": {
      "RESIN_SUPERVISOR_DELTA_VERSION": "3",
      "RESIN_SUPERVISOR_NATIVE_LOGGER": "true",
      "RESIN_HOST_CONFIG_avoid_warnings": "1",
      "RESIN_HOST_CONFIG_disable_splash": "1",
      "RESIN_HOST_CONFIG_dtparam": "\"i2c_arm=on\",\"spi=on\",\"audio=on\"",
      "RESIN_HOST_CONFIG_gpu_mem": "16",
      "RESIN_HOST_FIREWALL_MODE": "",
      "RESIN_SUPERVISOR_DELTA": "1",
      "RESIN_SUPERVISOR_POLL_INTERVAL": "900000"
    },
    "apps": {
      "1725186": {
        "name": "forest",
        "services": {},
        "volumes": {},
        "networks": {}
      }
    }
  },
  "dependent": {
    "apps": {},
    "devices": {}
  }
}

Running a Device health check it mentions the following error, may be relevant?:

check_networking
Some networking issues detected: 
test_balena_registry: Could not communicate with  for authentication
9

Do you have any releases built for balenaSound? It should appear under the “Releases” dashboard section, for this app…

10

Thanks for replying. I realised after reading it that I was trying to start from scratch rather than loading the release at this link. Problem solved, thanks very much!

11

No worries!

1 Like