System failed

[oliverhavrila]

Description

Not able to update balena OS from 5.0.8 to 5.2.2, it shows:
Operation failed with: Request error: Device is busy: configuring

It is also not possible to update supervisor version from 16.1.2 to 16.1.9

Status stuck at:
Reboot in progress

Basically nothing works, neither via CLI.

Device health hecks shows:
An error occurred while querying checks data: 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?

Device diagnostics:
device_diagnostics.txt

Supervisor state:
Network request failed

Any suggestion how to solve this problem?

I manage this device and it is roughly 80km away, so a very uncomfortable situation.

Additional information you deem important (e.g. issue happens only occasionally):

Output of balena-engine version:

Client:
 Version:           v20.10.42
 API version:       1.41
 Go version:        go1.16.2
 Git commit:        65d57057985ff817892d01293c1883b1b5ade469
 Built:             Tue Dec 19 19:09:03 2023
 OS/Arch:           linux/arm64
 Context:           default
 Experimental:      true
Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?

Output of balena-engine info:

Client:
 Context:    default
 Debug Mode: false

Server:
ERROR: Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
errors pretty printing info

Additional environment details (device type, OS, etc.):

Device type: Raspberry Pi 4 (using 64bit OS)
OS version: 5.0.8
Supervisor version: 16.1.2

Thank you

[lmbarros]

Hi @oliverhavrila , thanks for reporting this! This error message

Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?

indicates that balenaEngine is not running on the device, but this could be happening for many different reasons. I'd suggest you to look into the system logs (using journalctl) to try to get some clues about the underlying cause. For example, run journalctl -au balena-engine and try to understand if the Engine is crash-looping at startup and for what reason.

Also, at this point it is not clear whether this is a balenaEngine issue or of the root cause lies somewhere else (for example, the OS, or even a hardware failure), so I'd say balena's support channels (like the forums) would be a better fit at this stage.