I ran an Update of Rasbian on my raspberry pi with the soma-connect-Image.
This is what happened afterwards:
`
[LOG] Example app listening on port 3000!
[ERROR] (node:4079) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
[WARN] raven@2.6.2 alert: failed to send exception to sentry: connect ECONNREFUSED 0.0.0.0:443
[ERROR] Error: EBUSY, Device or resource busy
at Hci.init (/snapshot/src/node_modules/noble/lib/hci-socket/hci.js)
at NobleBindings.init (/snapshot/src/node_modules/noble/lib/hci-socket/bindings.js:83:13)
at Noble. (/snapshot/src/node_modules/noble/lib/noble.js:58:24)
at processTicksAndRejections (internal/process/task_queues.js:79:11)
at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:66:3)
at Function.Module.runMain (pkg/prelude/bootstrap.js:1376:13)
at internal/main/run_main_module.js:18:47
soma-connect.service: Main process exited, code=exited, status=1/FAILURE
soma-connect.service: Failed with result 'exit-code'.
soma-connect.service: Service RestartSec=1s expired, scheduling restart.
soma-connect.service: Scheduled restart job, restart counter is at 3.
Stopped SOMA Connect.
soma-connect.service: Start request repeated too quickly.
soma-connect.service: Failed with result 'exit-code'.
Failed to start SOMA Connect.
`
It would be nice if the Image wasn't that outdated in the first place, but at least I want be able to run some updates.
I ran an Update of Rasbian on my raspberry pi with the soma-connect-Image.
This is what happened afterwards:
` [LOG] Example app listening on port 3000! [ERROR] (node:4079) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated [WARN] raven@2.6.2 alert: failed to send exception to sentry: connect ECONNREFUSED 0.0.0.0:443 [ERROR] Error: EBUSY, Device or resource busy at Hci.init (/snapshot/src/node_modules/noble/lib/hci-socket/hci.js) at NobleBindings.init (/snapshot/src/node_modules/noble/lib/hci-socket/bindings.js:83:13) at Noble. (/snapshot/src/node_modules/noble/lib/noble.js:58:24)
at processTicksAndRejections (internal/process/task_queues.js:79:11)
at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:66:3)
at Function.Module.runMain (pkg/prelude/bootstrap.js:1376:13)
at internal/main/run_main_module.js:18:47
soma-connect.service: Main process exited, code=exited, status=1/FAILURE
soma-connect.service: Failed with result 'exit-code'.
soma-connect.service: Service RestartSec=1s expired, scheduling restart.
soma-connect.service: Scheduled restart job, restart counter is at 3.
Stopped SOMA Connect.
soma-connect.service: Start request repeated too quickly.
soma-connect.service: Failed with result 'exit-code'.
Failed to start SOMA Connect.
`
It would be nice if the Image wasn't that outdated in the first place, but at least I want be able to run some updates.
Also your Repo "deb http://soma-dev-repo.s3.amazonaws.com/id/e4:5f:01:1e:b9:89/apt/raspbian buster main" is not signed OR Reachable.
Please fix this and clean up the image.