Hi,
One of my machines is having a problem.
The container is delivering me this message on console:
Connecting to 34cd626fbb74abdc863f5704d14323aa...
Spawning shell...
sh: line 1: F: command not found Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
SSH session disconnected
I did some further digging on the HostOS and seems that there is a problem with balena supervisor and balena. Not sure how can I solve this remotely, I tried restarting balena-supervisor and balena without luck.
Not sure how to address this issue, any ideas?
=============================================================
Welcome to balenaOS
root@34cd626:~# systemctl restart balena-supervisor
Job for balena-supervisor.service failed because the control process exited with error code.
See “systemctl status balena-supervisor.service” and “journalctl -xeu balena-supervisor.service” for details.
root@34cd626:~# systemctl status balena-supervisor.service
● balena-supervisor.service - Balena supervisor
Loaded: loaded (/lib/systemd/system/balena-supervisor.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/balena-supervisor.service.d
└─balena-supervisor-conf.conf
Active: activating (auto-restart) (Result: exit-code) since Thu 2025-10-16 16:42:06 UTC; 6s ago
Process: 14741 ExecStartPre=/usr/bin/balena stop resin_supervisor (code=exited, status=1/FAILURE)
Process: 14756 ExecStartPre=/usr/bin/balena stop balena_supervisor (code=exited, status=1/FAILURE)
Process: 14775 ExecStartPre=/bin/systemctl is-active balena.service (code=exited, status=3)
root@34cd626:~# journalctl -xeu balena-supervisor.service
Oct 16 16:41:38 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:41:38 34cd626 systemd[1]: Failed to start Balena supervisor.
Oct 16 16:41:50 34cd626 balena-supervisor[14342]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:41:53 34cd626 balena-supervisor[14360]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:41:53 34cd626 balena-supervisor[14415]: activating
Oct 16 16:41:53 34cd626 systemd[1]: balena-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 16 16:41:53 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:41:53 34cd626 systemd[1]: Failed to start Balena supervisor.
Oct 16 16:42:06 34cd626 balena-supervisor[14741]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:42:06 34cd626 balena-supervisor[14756]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:42:06 34cd626 balena-supervisor[14775]: activating
Oct 16 16:42:06 34cd626 systemd[1]: balena-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 16 16:42:06 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:42:06 34cd626 systemd[1]: Failed to start Balena supervisor.
Oct 16 16:42:19 34cd626 balena-supervisor[15099]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:42:21 34cd626 balena-supervisor[15119]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:42:21 34cd626 balena-supervisor[15171]: activating
Oct 16 16:42:21 34cd626 systemd[1]: balena-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 16 16:42:21 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:42:21 34cd626 systemd[1]: Failed to start Balena supervisor.
Oct 16 16:42:32 34cd626 balena-supervisor[15449]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:42:34 34cd626 balena-supervisor[15467]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:42:34 34cd626 balena-supervisor[15530]: activating
Oct 16 16:42:34 34cd626 systemd[1]: balena-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 16 16:42:34 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:42:34 34cd626 systemd[1]: Failed to start Balena supervisor.
Oct 16 16:42:45 34cd626 balena-supervisor[15800]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:42:47 34cd626 balena-supervisor[15819]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:42:47 34cd626 balena-supervisor[15881]: activating
Oct 16 16:42:47 34cd626 systemd[1]: balena-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 16 16:42:47 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:42:47 34cd626 systemd[1]: Failed to start Balena supervisor.
Oct 16 16:42:58 34cd626 balena-supervisor[16155]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:42:58 34cd626 balena-supervisor[16166]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:42:59 34cd626 balena-supervisor[16185]: activating
Oct 16 16:42:59 34cd626 systemd[1]: balena-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 16 16:42:59 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:42:59 34cd626 systemd[1]: Failed to start Balena supervisor.
root@34cd626:~# systemctl restart balena
Job for balena.service failed because the control process exited with error code.
See “systemctl status balena.service” and “journalctl -xeu balena.service” for details.
root@34cd626:~# systemctl status balena.service
● balena.service - Balena Application Container Engine
Loaded: loaded (/lib/systemd/system/balena.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/balena.service.d
└─storagemigration.conf
Active: activating (start) since Thu 2025-10-16 16:43:59 UTC; 739ms ago
TriggeredBy: ● balena-engine.socket
Docs:
Main PID: 17805 (balenad)
Tasks: 86 (limit: 2124)
Memory: 74.9M
CGroup: /system.slice/balena.service
├─ 13031 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13030
├─ 13089 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13088
├─ 13170 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13157
├─ 13258 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13257
├─ 13317 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13316
├─ 13387 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13385
├─ 13443 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13442
├─ 13512 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13511
├─ 13586 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13579
├─ 13644 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13643
├─ 13728 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13726
├─ 13792 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13791
├─ 13859 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13854
├─ 13935 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 13928
├─ 14017 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 14010
├─ 14082 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 14081
├─ 14138 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 14137
├─ 14194 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 14193
├─ 14279 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 14274
├─ 14350 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 14349
├─ 14417 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 14416
├─ 14480 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 14479
├─ 14538 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 14537
├─ 14600 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 14599
├─ 14673 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 14662
├─ 14762 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 14755
├─ 14824 /proc/self/exe --healthcheck /usr/lib/balena/balena-healthcheck --pid 14822
root@34cd626:~#
root@34cd626:~# journalctl -xeu balena.service
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 17090 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 17156 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 17216 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 17311 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 17387 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 17451 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 17512 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 17571 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 17678 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 17740 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 17806 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 17868 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 17956 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 18039 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 18103 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:14 34cd626 systemd[1]: balena.service: Found left-over process 18167 (exe) in control group while starting unit. Ignoring.
Oct 16 16:44:14 34cd626 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 16 16:44:15 34cd626 balenad[18232]: time=“2025-10-16T16:44:15.178557451Z” level=info msg=“Starting up”
Oct 16 16:44:15 34cd626 balenad[18232]: time=“2025-10-16T16:44:15.178774482Z” level=warning msg=“Running experimental build”
Oct 16 16:44:15 34cd626 balenad[18232]: time=“2025-10-16T16:44:15.187715732Z” level=info msg=“libcontainerd: started new balena-engine-containerd process” pid=18255
Oct 16 16:44:15 34cd626 balenad[18255]: time=“2025-10-16T16:44:15Z” level=warning msg="containerd config version 1 has been deprecated and will be removed in containerd v2.0, please switch to versio>
Oct 16 16:44:15 34cd626 balenad[18255]: time=“2025-10-16T16:44:15.445735211Z” level=info msg=“starting containerd” revision= version=1.6.6+unknown
root@34cd626:~# systemctl restart balena-supervisor
Job for balena-supervisor.service failed because the control process exited with error code.
See “systemctl status balena-supervisor.service” and “journalctl -xeu balena-supervisor.service” for details.
root@34cd626:~# systemctl status balena-supervisor.service
● balena-supervisor.service - Balena supervisor
Loaded: loaded (/lib/systemd/system/balena-supervisor.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/balena-supervisor.service.d
└─balena-supervisor-conf.conf
Active: activating (auto-restart) (Result: exit-code) since Thu 2025-10-16 16:44:44 UTC; 6s ago
Process: 19034 ExecStartPre=/usr/bin/balena stop resin_supervisor (code=exited, status=1/FAILURE)
Process: 19042 ExecStartPre=/usr/bin/balena stop balena_supervisor (code=exited, status=1/FAILURE)
Process: 19059 ExecStartPre=/bin/systemctl is-active balena.service (code=exited, status=3)
Oct 16 16:44:44 34cd626 systemd[1]: Failed to start Balena supervisor.
root@34cd626:~# journalctl -xeu balena-supervisor.service
Oct 16 16:43:42 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:43:42 34cd626 systemd[1]: Failed to start Balena supervisor.
Oct 16 16:43:53 34cd626 balena-supervisor[17645]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:43:53 34cd626 balena-supervisor[17670]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:43:54 34cd626 balena-supervisor[17691]: activating
Oct 16 16:43:54 34cd626 systemd[1]: balena-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 16 16:43:54 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:43:54 34cd626 systemd[1]: Failed to start Balena supervisor.
Oct 16 16:44:07 34cd626 balena-supervisor[18022]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:44:07 34cd626 balena-supervisor[18033]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:44:07 34cd626 balena-supervisor[18052]: activating
Oct 16 16:44:07 34cd626 systemd[1]: balena-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 16 16:44:07 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:44:07 34cd626 systemd[1]: Failed to start Balena supervisor.
Oct 16 16:44:20 34cd626 balena-supervisor[18377]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:44:22 34cd626 balena-supervisor[18387]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:44:22 34cd626 balena-supervisor[18459]: activating
Oct 16 16:44:22 34cd626 systemd[1]: balena-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 16 16:44:22 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:44:22 34cd626 systemd[1]: Failed to start Balena supervisor.
Oct 16 16:44:33 34cd626 balena-supervisor[18736]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:44:33 34cd626 balena-supervisor[18746]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:44:33 34cd626 balena-supervisor[18765]: activating
Oct 16 16:44:33 34cd626 systemd[1]: balena-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 16 16:44:33 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:44:33 34cd626 systemd[1]: Failed to start Balena supervisor.
Oct 16 16:44:44 34cd626 balena-supervisor[19034]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:44:44 34cd626 balena-supervisor[19042]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:44:44 34cd626 balena-supervisor[19059]: activating
Oct 16 16:44:44 34cd626 systemd[1]: balena-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 16 16:44:44 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:44:44 34cd626 systemd[1]: Failed to start Balena supervisor.
Oct 16 16:44:57 34cd626 balena-supervisor[19386]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:44:57 34cd626 balena-supervisor[19405]: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Oct 16 16:44:58 34cd626 balena-supervisor[19432]: activating
Oct 16 16:44:58 34cd626 systemd[1]: balena-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 16 16:44:58 34cd626 systemd[1]: balena-supervisor.service: Failed with result ‘exit-code’.
Oct 16 16:44:58 34cd626 systemd[1]: Failed to start Balena supervisor.
I added Support access to the device with BalenaUUID 34cd626fbb74abdc863f5704d14323aa in case support might want to give me a hand.
Thank you in advance