search

balena-io-experimental / balena-cncjs

An example of running CNC.js on the Balena platform.
8 stars 4 forks source link

Services not starting on Fin #2

Open ghost opened 4 years ago

ghost commented 4 years ago

I just tried this project on a Fin(CM3) and the services do not start, except mjpg-streamer, but that reports no camera detected even though I have a pi-cam plugged in.

cncjs - Installed - ea91cda mdns - Downloaded - ea91cda mjpg-streamer - Running - ea91cda proxy - Downloaded - ea91cda

The cncjs service just keeps trying to start, but when getting a shell to the host and looking at containers, only the camera service and the supervisor service are present. While in the host, I tried to manually create a container from the cncjs image, but the container never created. A container ID was output from the command, but a ps showed no new containers.

I'm just going to try the same on an RPi 3, which I have a feeling will work, and that this is an issue with CM3 in this instance.

I'll let you know.

Paul

ghost commented 4 years ago

No, unfortunately this did not load on RPi3 either. Looking at the logs of the supervisor I saw this, right after a couple of API error blocks, and after the images downloaded:

[event] Event: Image download error {"error":{"message":"(HTTP code 404) no such image - no such image: registry2.balena-cloud.com/v2/bd98545428d083661950e5e3f63bc957@sha256:b8a7dff9e8700ef1562f3a391e08d8b2725186e10766f190018fe750180d076a: No such image: registry2.balena-cloud.com/v2/bd98545428d083661950e5e3f63bc957@sha256:b8a7dff9e8700ef1562f3a391e08d8b2725186e10766f190018fe750180d076a ","stack":"Error: (HTTP code 404) no such image - no such image: registry2.balena-cloud.com/v2/bd98545428d083661950e5e3f63bc957@sha256:b8a7dff9e8700ef1562f3a391e08d8b2725186e10766f190018fe750180d076a: No such image: registry2.balena-cloud.com/v2/bd98545428d083661950e5e3f63bc957@sha256:b8a7dff9e8700ef1562f3a391e08d8b2725186e10766f190018fe750180d076a \n at /usr/src/app/dist/app.js:727:42130\n at /usr/src/app/dist/app.js:727:42093\n at m.buildPayload (/usr/src/app/dist/app.js:727:42103)\n at IncomingMessage. (/usr/src/app/dist/app.js:727:41603)\n at IncomingMessage.emit (events.js:194:15)\n at endReadableNT (_stream_readable.js:1125:12)\n at process._tickCallback (internal/process/next_tick.js:63:19)"},"image":{"name":"registry2.balena-cloud.com/v2/bd98545428d083661950e5e3f63bc957@sha256:b8a7dff9e8700ef1562f3a391e08d8b2725186e10766f190018fe750180d076a","appId":1569149,"serviceId":408716,"serviceName":"mdns","imageId":1865311,"releaseId":1220722,"dependent":0,"dockerImageId":null}}

Here is the full supervisor log: Starting system message bus: dbus.

grykom commented 3 years ago

@webtop did you manage to solve this? I have exactly the same on rpi4

pallsopp commented 3 years ago

Unfortunately no. I ended up giving up on it, just due to some time constraints I had at the time. I believe it is a missing docker image that is part of the build, or simply a mis-labeled path.

It's worth surfacing this in the forums though, as you're more likely to get a community member that has this working.

autonoma-official commented 1 year ago

is also got this error message.

device is in one fleet with 3 containers using the networkmode host.

then i move per balena api the device to another fleet with 3 containers using an bridged network.

then the error will occour. supervisor will not be able to download the new containers

`Sep 13 09:02:23 9609aea 99ad3d31c10d[1819]: [debug] {"aliases":["health"]}

Sep 13 09:02:23 9609aea 99ad3d31c10d[1819]: [debug] Replacing container for service health because of config changes:

Sep 13 09:02:23 9609aea 99ad3d31c10d[1819]: [debug] Network changes detected

Sep 13 09:02:23 9609aea balena-supervisor[18442]: [debug] Replacing container for service health because of config changes:

Sep 13 09:02:23 9609aea balena-supervisor[18442]: [debug] Network changes detected

Sep 13 09:02:23 9609aea balena-supervisor[18442]: [error] Scheduling another update attempt in 512000ms due to failure: Error: Failed to apply state transition steps. Steps:["noop","fetch"]

Sep 13 09:02:23 9609aea balena-supervisor[18442]: [error] at fn (/usr/src/app/dist/app.js:6:8745)

Sep 13 09:02:23 9609aea 99ad3d31c10d[1819]: [error] Scheduling another update attempt in 512000ms due to failure: Error: Failed to apply state transition steps. Steps:["noop","fetch"]

Sep 13 09:02:23 9609aea 99ad3d31c10d[1819]: [error] at fn (/usr/src/app/dist/app.js:6:8745)

Sep 13 09:02:23 9609aea 99ad3d31c10d[1819]: [error] Device state apply error Error: Failed to apply state transition steps. Steps:["noop","fetch"]

Sep 13 09:02:23 9609aea balena-supervisor[18442]: [error] Device state apply error Error: Failed to apply state transition steps. Steps:["noop","fetch"]

Sep 13 09:02:23 9609aea balena-supervisor[18442]: [error] at fn (/usr/src/app/dist/app.js:6:8745)

Sep 13 09:02:23 9609aea 99ad3d31c10d[1819]: [error] at fn (/usr/src/app/dist/app.js:6:8745)

Sep 13 09:03:13 9609aea 99ad3d31c10d[1819]: [error] LogBackend: server responded with status code: 504

Sep 13 09:03:13 9609aea balena-supervisor[18442]: [error] LogBackend: server responded with status code: 504

Sep 13 09:03:20 9609aea 99ad3d31c10d[1819]: [api] GET /v1/healthy 200 - 9.324 ms

`