Failed to start Balena Application Container Engine.

Product support balenaOS
1

Hi,

I have a problem with device which is Online (VPN only).
After executing command

journalctl -xe

I get following information:

Jul 21 13:50:25 210a963 balenad[19624]: github.com/docker/docker/vendor/github.com/containerd/containerd/diff/walking.init()
Jul 21 13:50:25 210a963 balenad[19624]: :1 +0x92 fp=0x1a345fbc sp=0x1a345fb8 pc=0x8430992
Jul 21 13:50:25 210a963 balenad[19624]: github.com/docker/docker/vendor/github.com/containerd/containerd/cmd/containerd.init()
Jul 21 13:50:25 210a963 balenad[19624]: :1 +0x38 fp=0x1a345fc0 sp=0x1a345fbc pc=0x862d178
Jul 21 13:50:25 210a963 balenad[19624]: main.init()
Jul 21 13:50:25 210a963 balenad[19624]: :1 +0x39 fp=0x1a345fc4 sp=0x1a345fc0 pc=0x8ceb6b9
Jul 21 13:50:25 210a963 balenad[19624]: runtime.main()
Jul 21 13:50:25 210a963 balenad[19624]: /usr/lib/go/src/runtime/proc.go:183 +0x1d9 fp=0x1a345ff0 sp=0x1a345fc4 pc=0x8074cd9
Jul 21 13:50:25 210a963 balenad[19624]: runtime.goexit()
Jul 21 13:50:25 210a963 balenad[19624]: /usr/lib/go/src/runtime/asm_386.s:1635 +0x1 fp=0x1a345ff4 sp=0x1a345ff0 pc=0x809e0b1
Jul 21 13:50:25 210a963 systemd[1]: balena.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 21 13:50:25 210a963 systemd[1]: balena.service: Failed with result ‘exit-code’.
Jul 21 13:50:25 210a963 systemd[1]: Failed to start Balena Application Container Engine.
Jul 21 13:50:25 210a963 systemd[1]: balena.service: Service hold-off time over, scheduling restart.
Jul 21 13:50:25 210a963 systemd[1]: balena.service: Scheduled restart job, restart counter is at 41835.
Jul 21 13:50:25 210a963 systemd[1]: Stopped Balena Application Container Engine.
Jul 21 13:50:25 210a963 systemd[1]: Closed Docker Socket for the API.
Jul 21 13:50:25 210a963 systemd[1]: Stopping Docker Socket for the API.
Jul 21 13:50:25 210a963 systemd[1]: balena-engine.socket: Start request repeated too quickly.
Jul 21 13:50:25 210a963 systemd[1]: balena-engine.socket: Failed with result ‘start-limit-hit’.
Jul 21 13:50:25 210a963 systemd[1]: Failed to listen on Docker Socket for the API.
Jul 21 13:50:25 210a963 systemd[1]: Dependency failed for Balena Application Container Engine.
Jul 21 13:50:25 210a963 systemd[1]: balena.service: Job balena.service/start failed with result ‘dependency’.

Can some one help me push this issue?

2

Hello @FredTheMachine first of all welcome to the balena community!

Could you please confirm what device type are you using for your fleet? On the other hand, could you please confirm that the application that you are trying to deploy is compatible with that device type?

Let us know more details please! Thanks

4

Hi @mpous thank you for your interest.
Sorry for late reply, I’m very busy last time.
Yes device type is Intel Edison and the application used to work properly for very long time. Suddenly it just stopped working.

5

Has anything changed recently, for instance have you recently updated the OS? Which version of the OS are you on?

6

Hi Robert, the Intel Edison is a discontinued device type running an unmaintained version of balenaOS - it will probably need some manual intervention to recover. If the device is balenaCloud managed, you could allow support access and provide us with its UUID so we can attempt a manual recovery.