Balena Engine not restarting exited container.

Product support balenaEngine
1

Hi there,

We’re seeing some issue with balena engine not starting up the containers correctly, and some containers are stucked in the exited state.

Any idea on what might be happening?

Thanks.

3

While trying to start the exited service on balenaCloud dashboard, resin-supervisor is throwing error shown below.

The error says the container name is already in used by another container, but that container ID is the exited container that should be running.

Jun 03 00:21:42 4e92d9b resin-supervisor[8867]: [event] Event: Service install {“service”:{“appId”:1791542,“serviceId”:949837,“serviceName”:“acquisition_2”,“releaseId”:1809165}}
Jun 03 00:21:42 4e92d9b resin-supervisor[8867]: [error] Error on POST /v2/applications/1791542/start-service: Error: (HTTP code 409) unexpected - Conflict. The container name “/acquisition_2_3644654_1809165” is already in use by container “7f3f56598d6dd087a63c7b15620d2eb76f47fdd452ebad882d7fd8ef64fd627e”. You have to remove (or rename) that container to be able to reuse that name.
Jun 03 00:21:42 4e92d9b resin-supervisor[8867]: [error] at /usr/src/app/dist/app.js:10:2302933
Jun 03 00:21:42 4e92d9b resin-supervisor[8867]: [error] at /usr/src/app/dist/app.js:10:2302865
Jun 03 00:21:42 4e92d9b resin-supervisor[8867]: [error] at Modem.buildPayload (/usr/src/app/dist/app.js:10:2302885)
Jun 03 00:21:42 4e92d9b resin-supervisor[8867]: [error] at IncomingMessage. (/usr/src/app/dist/app.js:10:2302138)
Jun 03 00:21:42 4e92d9b resin-supervisor[8867]: [error] at IncomingMessage.emit (events.js:322:22)
Jun 03 00:21:42 4e92d9b resin-supervisor[8867]: [error] at endReadableNT (_stream_readable.js:1187:12)
Jun 03 00:21:42 4e92d9b resin-supervisor[8867]: [error] at processTicksAndRejections (internal/process/task_queues.js:84:21)

7

Hey there,

It sounds like this error is happening when the device is attempting to move to a new release. Can you provide some more details about what actions you took that lead to this error? Additionally, the device’s Supervisor version and host OS version would be much appreciated.

Regards,
Christina

12

Hi,

The targeted release and current release was the same as before, there was no update performed on it. There was no action taken which lead to this error, we were using this specific unit as a stability test for our software and it has been running the same release for almost a week.

Here’s the device details:

  • supervisor version: 12.3.5
  • Device type: jetson-nano
  • Host os version: balenaOS 2.69.1+rev1