Yeah, already did and got it working.
Thanks!
Yeah, already did and got it working.
Thanks!
Hmm, no preloaded image doesnât communicate with my openBalena server:
Here is a log of supervisor:
root@yokoso:~# balena ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6e5af6ad869e balena/rpi-supervisor:v11.12.4 "/usr/src/app/entry.âŠ" 6 minutes ago Up 6 minutes (healthy) resin_supervisor
aca145dae1ab 9699d4ae6e16 "/usr/bin/entry.sh bâŠ" 2 months ago Up 10 hours yokoso_5_5
root@yokoso:~# balena logs 6
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
Warning: Ignoring extra certs from `/etc/ssl/certs/balenaRootCA.pem`, load failed: error:02001002:system library:fopen:No such file or directory
[info] Supervisor v11.12.4 starting up...
[info] Setting host to discoverable
[warn] Invalid firewall mode: . Reverting to state: off
[info] đ„ Applying firewall mode: of
[debug] Starting logging infrastructure
[info] Starting firewall
[success] đ„ Firewall mode applie
[debug] Starting api binder
[event] Event: Supervisor start {}
[error] LogBackend: unexpected error: Error: self signed certificate in certificate chain
[error] at TLSSocket.onConnectSecure (_tls_wrap.js:1474:34)
[error] at TLSSocket.emit (events.js:310:20)
[error] at TLSSocket._finishInit (_tls_wrap.js:917:8)
[error] at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:687:12)
[debug] Performing database cleanup for container log timestamps
[info] Previous engine snapshot was not stored. Skipping cleanup.
[debug] Handling of local mode switch is completed
[debug] Connectivity check enabled: true
[debug] Starting periodic check for IP addresses
[info] Reporting initial state, supervisor version and API info
[debug] VPN status path exists.
[info] VPN connection is not active.
(node:1) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[info] Waiting for connectivity...
[info] Attempting to load any preloaded applications
[success] Preloading complete
[info] Starting API server
[info] Supervisor API successfully started on port 48484
[info] Applying target state
[debug] Ensuring device is provisioned
[event] Event: Device bootstrap {}
[info] New device detected. Provisioning...
[error] LogBackend: unexpected error: Error: self signed certificate in certificate chain
[error] at TLSSocket.onConnectSecure (_tls_wrap.js:1474:34)
[error] at TLSSocket.emit (events.js:310:20)
[error] at TLSSocket._finishInit (_tls_wrap.js:917:8)
[error] at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:687:12)
[event] Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":""}}
[debug] Finished applying target state
[success] Device state apply success
[event] Event: Device bootstrap {}
[info] New device detected. Provisioning...
[event] Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":""}}
[event] Event: Device bootstrap {}
[info] New device detected. Provisioning...
[event] Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":""}}
[event] Event: Device bootstrap {}
[info] New device detected. Provisioning...
[event] Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":""}}
[event] Event: Device bootstrap {}
[info] New device detected. Provisioning...
[event] Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":""}}
[event] Event: Device bootstrap {}
[info] New device detected. Provisioning...
[event] Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":""}}
[event] Event: Device bootstrap {}
[info] New device detected. Provisioning...
[event] Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":""}}
[event] Event: Device bootstrap {}
[info] New device detected. Provisioning...
[event] Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":""}}
[event] Event: Device bootstrap {}
[info] New device detected. Provisioning...
[event] Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":""}}
[event] Event: Device bootstrap {}
[info] New device detected. Provisioning...
[event] Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":""}}
[api] GET /v1/healthy 200 - 182.323 ms
[event] Event: Device bootstrap {}
[info] New device detected. Provisioning...
[event] Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":""}}
[event] Event: Device bootstrap {}
[info] New device detected. Provisioning...
[event] Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":""}}
[event] Event: Device bootstrap {}
[info] New device detected. Provisioning...
[event] Event: Device bootstrap failed, retrying {"delay":30000,"error":{"message":""}}
Is there any other thing I should check? Seems certification issue?
Here are commmands I had used to preload the image file:
balena os configure balena.img --app yokosoApp
balena preload balena.img --add-certificate <OPENBALENA CERT FILE> --app yokosoApp --commit current --splash-image my_splash.png
Thanks!
Hi Wester, we just updated openBalena components and documentation. Please have a look at the updated getting started guide to make sure you have your openBalena installation setup as described there. Hopefully that fixes your issue. https://www.balena.io/open/docs/getting-started/ Once your all updated let us know if your issue persists.
Also check out the README to find the new requirements https://github.com/balena-io/open-balena
"The current release of openBalena has the following minimum version requirements:
balenaOS v2.58.3
balena CLI v12.23.4
If you are updating from previous openBalena versions, ensure you update the balena CLI and reprovision any devices to at least the minimum required versions in order for them to be fully compatible with this release, as some features may not work."
I see the latest image for PiZero is BalenaOS 2.54.2+rev1 ( https://www.balena.io/os/#download) give that a try with an upgraded openBalena, and I will ask my colleagues about compatibility for devices that donât have the new OS version yet.
Would be better to wait for the updated version? Seems waste of time?
Ok if you would prefer not to risk it. I will update you when I hear back from my colleagues. In the mean time with your certificate issue I noticed âWARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
Warning: Ignoring extra certs from /etc/ssl/certs/balenaRootCA.pem
, load failed: error:02001002:system library:fopen:No such file or directoryâ can you confirm that the --add-certificate <OPENBALENA CERT FILE>
file path is correct.
Yes, without that parameter, balena preload
command didnât work. See this link - https://github.com/balena-io/balena-cli/issues/2068#issuecomment-713178034
Ok so, version 2.58.6 for pi-zero is available on staging (finally testing before release) you can download it using the following. BALENARC_BALENA_URL="balena-staging.com" balena os download raspberrypi --version=2.58.6+rev4 -o rapsberrypi-2.58.6+rev4.img
Are you setting export NODE_EXTRA_CA_CERTS='/path/to/ca.crt'
before running CLI?
Of course, yes
And you have completed these steps âInstall self-signed certificates on the local machineâ https://www.balena.io/open/docs/getting-started/#Install-self-signed-certificates-on-the-local-machine
Dude, I have been using balenaOS for over a year! lol
Just checking since I thought those steps might have changed with the new update.
Will try the new version once the image is ready. Thanks!
I will ask my colleagues who are involved in preload and openBalena development if they know the solution to the certificate issue on the version you are running.
Hi, @codewithcheese
Any update here?
Wester,
We need to reproduce this to see whatâs causing the certificate to not be expanded at runtime into the correct FS locations. You can see this yourself in the start-resin-supervisor
script but I am not sure why your process has resulted in the failure.
To confirm, you have preloaded successfully and wifi-connect
ran on boot. Then you connected to the internet and the API comms in the Supervisor is failing. Is that correct?
Could you also, for the sake of clarity, confirm the versions of:
Thanks.
HI, @richbayliss
Yes, preloaded successfully, but wifi-connect
wasnât executed as my app didnât launch automatically.
Does the resin-supervisor
need internet connection to start the containers at the booting time?
Versions I have used:
Please check my original question to see why I had to select these versionsâŠ