Unable to update with blue Balena button #230
Comments
|
@serviceman77 this is an issue on balena side which we have reported to them here - https://forums.balena.io/t/deploy-with-balena-buttons-not-working/372853 |
|
Checking in to see if there is an update to this. Wingbits is sending their geosigners out. What is the workaround to update? Appreciate any suggestions |
|
@serviceman77 unfortunately the fix is out of our control - it is an issue on balena side with their backend. For now, the only way is to push it manually using the instructions here using the balena cli (points 12 to 17 in the list): |
|
Thanks! I'm new to programming like this. I guess it's time to learn. Any pointers on this process using windows? |
|
I can't give many tips for windows as I've never done this via windows I'm afraid. Only via Linux and Mac. But the following should work. Download the balenaCLI from here: https://github.com/balena-io/balena-cli/blob/master/INSTALL-WINDOWS.md Then download the zip file of the repo from the main page:
Then unzip it, and from the CMD prompt, go into that folder (using Ref: @serviceman77 let me know if you get stuck and I'll try to help where I can |
|
Amazing directions! Thank you very much for the assist. |
|
Sorry to piggyback on this but just to clarify, is an update to Balena/Wingbits required for the Geosigner to be recognized and used? How do we check if it's being found? I've been trying to follow the instructions on wingbits.com to test with the wingbits binary but I tried opening a shell session to the Wingbits container in the Balena panel but can't find it anywhere. |
|
@jayscovill yes that's correct you need to update to the latest version to pick up the new Wingbits client (unless you have updated already within the last 2 weeks) The binary is either at You can run the command I'll add this to the readme soon |
|
Thanks for the quick reply. I have the variables set for autoupdate so may have the latest version already: HUP_CHECK_INTERVAL=1d but: All I have in /etc/wingbits is a file called "version". /usr/local/bin/wingbits doesn't exist. Is |
|
@jayscovill that auto update stuff relates to the HostOS. It will not update the application containers themselves, just the version of the balenaOS that runs on the device. Try EDIT: actually, according to this it does work but you need an ssh key set up with GitHub https://github.com/orgs/community/discussions/40388 |
|
Excellent, But: When I run: the output looks ok but: Maybe that command doesn't work in the dockerized version as it looks like it may be looking for systemctl which may not exist? If I run: it seems to see it but not sure it's actually being used. And if I try to |
|
@jayscovill yes correct, You don't need to do the flash thing. It will happen automatically. Just reboot the Pi and leave the GeoSigner plugged in for half an hour or so and it'll do it. |
|
Thanks again for your help! |
|
Just FYI @jayscovill I redacted the GeoSigner serial and your lat/lon from the GPS output above just for security. Probably doesn't matter too much but just in case 🙏 |
|
@jayscovill actually I'm not sure why Unless perhaps it was already running. I don't suppose you have the error output you saw? And if you run Thanks |
|
I rebooted the Pi and it's trying to install the firmware update but failing with the same error as when I tried manually. It just repeats the update loop over and over again with the below error at the end. Version still shows 0.0.0.0. |
|
@jayscovill very strange! Which version of raspberry pi hardware is this on? Is it a raspberry pi 2 or 3? |
|
Pi 3. |
From the error output, I'm guessing you are using a 32 bit version of the OS as well @jayscovill ? Not the Raspberry Pi 3 (64 bit OS) option in balena? I think basically it's missing the python wheels for this architecture, and it is also missing a compiler for C code which means it can't then build the package locally itself. If you go to the Wingbits container terminal and issue this command Otherwise I'll have to do some more digging. |
|
Actually @jayscovill if you haven't already done the GCC thing above, you might be better to try this first: |
|
It appears indeed that I'm running a 32bit OS: Running And: |
|
@jayscovill try just this then: Otherwise I'm likely going to have to add something to the dockerfile in an update. |
|
Sorry, try Results in the similar error but some different info as well: Again, appreciate the effort to help me out. |
|
@jayscovill getting somewhere as it's found the cryptography package now at least! Next thing to try: |
|
That seemed to go off without a hitch: But: |
|
Hmm that's very odd. I'm really not sure where to go from here and it is 2.30 am here so I'm going to go to sleep and come back to this tomorrow. And maybe try to reproduce it locally. One way that will definitely work to fix it is if you use a new fleet on balena with device type Raspberry Pi 3 (64 bit OS). But obviously that would mean entirely re-flashing your device and setting up all the device variables again and stuff so is a bit of a faff. But if you are eager to get it working ASAP this is probably going to be the quickest way. |
|
Please get some rest :) If there is no danger of losing my feeder status since it's DIY by rebuilding with a 64-bit OS I'm game for that. You're right, it'll be a bit of work since it's been so long since I set it up I'll have to re-learn the process. But it is probably the right long term solution. |
|
You will have a little bit of downtime on the station whilst you swap to new fleet (if you use a different SD card to existing one with raspi3 32 bit on it it'll be less - and has the add bonus of meaning you have a backup to revert to just by changing SD card if anything goes wrong!). But apart from that, you won't lose your ability to do DIY or connect the GeoSigner or anything. I'll still try and get this fixed in any case, but I'm away ATM and not sure if I have a raspberry pi 3 that I can access remotely to test with 😂 which is the main reason it'll take a while. Anyway let me know if you get stuck on anything and I'll be happy to help more tomorrow |
|
Following because I'm in the exact same scenario as @jayscovill . Funny enough I was even thinking of re-doing everything in 64 bit, but also its been forever since I originally set it up, so I haven't decided yet. Edit: Actually, it says I'm on Raspberry Pi 4 (using 64bit OS) root@3adff70fd946:/tmp# uname -m And perhaps I do have a different error running flash: |
Welp, I've redeployed with a 64-bit OS, set all my env variables and deployed the packages but for some reason most of my services, including the important ones like tar90 and wingbits don't want to start. tar90 is stuck in "Downloaded" and wingbits is stuck in "Installed" but won't start with a "Network request failed". I can access the BalenaOS docker container no problem. I can open a new issue for this if you prefer. Cheers |
I'm pretty sure my issue now is that my Geosigner is no longer being recognized as it looks to be failing on connecting to it via USB serial: |
Have you tried disconnecting all USB receivers except for the Geosigner? I didn't need to do that, but just something to try. |
|
Ya, no dice...same result :( |
|
@schubydoo so yours worked now? @jayscovill what power supply are you using? I'm still thinking it could be a power / undervoltage issue |
|
Well, tried again and got further this time but it's still crapping out in the during the flashing process. I have no other devices connected to the Pi so if this is a power problem and it won't work with a 5v 3A p/s then I don't know what else to try. |
|
@jayscovill can you post output of |
|
5v 3a should be ok... But it could still be undervoltage. Is it a RasPi official branded power supply or something else? The RasPi ones are actually rated at 5.25 volts because then with the voltage drop it usually sits at around 5v. The weirdness and changing nature of the connection issue suggests to me an issue with undervoltage (esp32 can be a bit temperamental with even slight power issues) however it's a bit hard to say. |
|
Not official RasPi. Tried several variations of different power sources all rated at least 3A but still no dice. Will hunt around for an official one. |
Yeah, if you can find one that's rated at 5.25v or even 5.15v it may solve the issue. My guess is the 5v bus on the USB on the raspberry pi is dropping too low. Hard to say for sure though, unless you have a USB power meter to hand? |
|
Also try these commands as well, might give some clues #230 (comment) |
Guessing the "USB JTAG/serial debug unit" may be the Geosigner. |
|
@shawaj Yes I'm all set! Using this exact command on a fresh container reboot allowed me to proceed to flashing with no issues.
|
|
@schubydoo fantastic good to know @jayscovill I'm going to add an idling mechanism to the container so that it can keep the container up without starting the wingbits client. To make it easier to do the manual flashing |
- add mechanism for idling container to allow for manually flashing geosigner - add mechanism for override of release hash to check for errors in new releases or force a dev release for example - print architecture - change version check to suit new client Relates-to: #230
- add mechanism for idling container to allow for manually flashing geosigner - add mechanism for override of release hash to check for errors in new releases or force a dev release for example - print architecture - change version check to suit new client Relates-to: #230
|
On raspi 4, I get: Still not sure why @schubydoo you saw different on same device |
|
And this was after the manual flash... |
|
Could it be another permissions type issue because I deployed via Windows? Can't think of much else that would be different... |
I don't see how it can be that. The things you changed here don't have any effect from permissions #230 (comment) There's really nothing I can see that would cause it to have not worked on a Pi4 (or any raspi on 64 bit os for that matter) |
|
@jayscovill how's things with yours? |
I gave up on it for the time being :P I haven't bothered to find an official power supply to test the theory it's power related with. But I'll likely have a Pi 4 soonish that I plan to try with. |
|
@jayscovill it might be worth trying with the most up to date version I just pushed. It now has the ability to idle the container for manually flashing the geosigner. And the auto-flash mechanism also has the ability to retry the process several times. I think it might work ok now for you. |
|
Still no dice unfortunately. Will see what happens when I rebuild with the Pi 4 once it's in my hands. |
|
Cool. Let us know how it goes. 🤞 |
|
Don't have my Pi 4 yet but I was able to fire up balena-adsb on a pizza box PC I have kicking around and update the Geosigner finally. Put it back on the Pi 3 and after a few reboots it finally synced up with Wingbits! Will forklift it all over to the Pi 4 when I get it. Thanks for all the help! |
|
@jayscovill ah that's great news. Glad you got it working eventually! |
|
@serviceman77 just FYI the blue deploy with balena button is working again now |
|
Closing as this has now been fixed by balena |
I receive an error when using the blue button to update. Any ideas what is causing this?
The text was updated successfully, but these errors were encountered: