"No logs yet", possibly due to container update issues?

Product support
1

We have two devices that are online in our dashboard, and that are reachable (can login to host and our containers), but that show “No logs yet”, and that don’t seem to be starting the services within our containers.

I’m not sure if this is relevant, but balena logs resin_supervisor (in host terminal) shows the following errors:

Device 25bcadc6e609f1a3d9491cc3b57d672f:

[2019-01-31T00:41:13.343Z] Event: Image cleanup error {“error”:{“message”:"(HTTP code 409) conflict - conflict: unable to delete 29d883db5067 (cannot be forced) - image has dependent child images ",“stack”:“Error: (HTTP code 409) conflict - conflict: unable to delete 29d883db5067 (cannot be forced) - image has dependent child images \n at /usr/src/app/dist/app.js:575:87425\n at /usr/src/app/dist/app.js:575:87388\n at m.buildPayload (/usr/src/app/dist/app.js:575:87398)\n at IncomingMessage. (/usr/src/app/dist/app.js:575:86898)\n at emitNone (events.js:91:20)\n at IncomingMessage.emit (events.js:185:7)\n at endReadableNT (_stream_readable.js:974:12)\n at _combinedTickCallback (internal/process/next_tick.js:80:11)\n at process._tickCallback (internal/process/next_tick.js:104:9)”}}
[2019-01-31T00:41:14.965Z] Finished applying target state

Device 2d7d675156570832554a868b7d328d4b:

[2019-01-31T00:25:39.342Z] Scheduling another update attempt due to failure: 2000 { Error: (HTTP code 404) no such container - No such image: registry2.balena-cloud.com/v2/7fc9d171c574cb28343c495f831faec4@sha256:4d7c9669c684591f4b02b91dc9de9e8829ae1caf9a0b56d128dfafad1f53cdb6
at /usr/src/app/dist/app.js:575:87425
at /usr/src/app/dist/app.js:575:87388
at m.buildPayload (/usr/src/app/dist/app.js:575:87398)
at IncomingMessage. (/usr/src/app/dist/app.js:575:86898)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
reason: ‘no such container’,
statusCode: 404,
json: { message: ‘No such image: registry2.balena-cloud.com/v2/7fc9d171c574cb28343c495f831faec4@sha256:4d7c9669c684591f4b02b91dc9de9e8829ae1caf9a0b56d128dfafad1f53cdb6’ } }
[2019-01-31T00:25:39.354Z] Apply error Error: (HTTP code 404) no such container - No such image: registry2.balena-cloud.com/v2/7fc9d171c574cb28343c495f831faec4@sha256:4d7c9669c684591f4b02b91dc9de9e8829ae1caf9a0b56d128dfafad1f53cdb6

4

Hi tendr. Thank you for reporting these issues. There were potentially three issues here:

  • Regarding “No logs yet”, we have a background task that safely patches the balena supervisor of old devices in relation to a logging feature, and our fleet ops team have reported to me that the task has updated the devices for the UUIDs you’ve mentioned in the past few hours.

  • Regarding the “Image cleanup error”, this is less certain but the fleet ops team again report that this is something that was likely patched in the past 24 hours.

  • The “(HTTP code 404) no such container - No such image” error may be related to an occasional git push or balena push error by which the live push logs include “unknown blob” messages, and which can be worked around by pushing again - so please try pushing again, and keep an eye on any push log error messages. We are currently working on a fix for this issue.

If the issues persist, could you please confirm the balenaOS version and the balena supervisor version? (These are shown on the device’s web dashboard.) Also, have these devices been recently moved between applications?

In addition to the “balena logs resin_supervisor” command you mentioned, another command that reports additional information is “journalctl -n 1000 -fu resin-supervisor” (host OS terminal).

Let us know how it goes.

1 Like
5

'Looks like these devices are now working as expected. Thank you!