Installation fails on Pi Zero W at snowpack build

[Gordon-Shumway2]

Hi,

I tried to install openrowingmonitor following the instructions at https://github.com/laberning/openrowingmonitor/blob/main/docs/installation.md. Installation failed when snowpack was being built. Apparently Armv6 is not supported. Apologies for vague error message - I did not write down the exact error message and am now installing on a Pi3 (and a Pi Zero 2 is on the way).

I did read the posting about "Raspberry Pi Zero compatibility" in the Discussion section, but I believe the current installer gets around the issue mentioned there and does indeed succeed in installing node16.

As I am installing on bigger hardware now there is no need to fix the issue (at least not for me). I just wanted to report it in case someone else tries an installation on a Pi zero.

Kind regards,
Michael

[laberning]

Hi Michael,

thanks for the report. Raspberry Pi Zero with its older ARMv6 is quite a beast as there is no official support for Node.js any more.
I mitigated this by adding some installation routines that will install an unofficial node build on these devices from here: https://github.com/nodejs/unofficial-builds, but it's possible that some newer dependencies might cause problems here...

I've just checked with a Raspberry Pi Zero, indeed the snowpack build does not finish:
# Liftoff bailout should not happen. Cause: Armv6 not supported
According to a few reports on the net this seems to be a problem with node 16 WebAssembly not working properly on ARMv6 architecture.

I did a quick fix to the install script so it sticks to Node.js 14 on the armv6l architecture. That seems to fix the issue, should be fine for now since we are not yet using any Node.js 16 features. On the long run this might be call for trouble, so there probably will be a point in time when we drop support for ARMv6.

Please let me know when you've tried it with the Raspi Zero 2 - I assume that this should be a very suitable device for running OpenRowingMonitor... and it has ARMv8 😄.

[Gordon-Shumway2]

Hello Lars,

thanks for the quick feedback!

I will keep you updated on my results with the Zero 2. Might take a while until it is shipped...

Kind regards,
Michael

[roblloyd319]

Not sure if it's related, but I'm having an issue now with my Pi Zero W.

Was working fine until last month; it seems like the SD card got corrupted. I couldn't get it to 'clean' up enough to re-install the OS, so I got a new SD card. OS installs OK, and I can access the Zero by SSH. But, the OpenRowingMonitor install always fails. Always fails downloading updates, it looks like .But, never the same file.

Any ideas?

[Gordon-Shumway2]

Hi, check your swap space. I had issues with installing Jaap's branch of ORM on a Pi Zero 2 due to insufficient RAM. System started to swap and eventually ran out of swap space. Setting swap to 1024 MB made the installation succeed. You can verify the issue by running 'top` or 'htop' during the ORM installation - this should show RAM and swap usage. Edit: this RAM/swap issue showed up when using the 64bit Lite OS. Regards, Michael

[roblloyd319]

I didn't have this issue when I first installed openrowingmonitor.

Previously, I had used a 16Gb sd card. I replaced it with a 32Gb.

I just tried the 1024Mb swpafile. It went further, but still failed. I just increased it to 2048Mb, and still it's failing to complete. It's failing when updating the pi system. For example, it just now failed updating 'firmware-misc-nonfree'. But, it's failed while updating other files, too. I don't think it's file-specific.

I noticed the install was updated in October to allow 64-bit Raspbian OS. Should I now be using 64-bit instead of 32?

EDIT: Looks like Pi Zero W can't run the 64-bit OS...

[Gordon-Shumway2]

Hi Rob, I have a Pi zero here and can try to reproduce it. Which OS are you using? And which branch of ORM are you installing? Have you tried installing the OS and (without trying to install ORM) upgraded/updated the OS? Regards, Michael Am 02.12.2022 um 15:37 schrieb roblloyd319:

…

I didn't have this issue when I first installed openrowingmonitor. Previously, I had used a 16Gb sd card. I replaced it with a 32Gb. I just tried the 1024Mb swpafile. It went further, but still failed. I just increased it to 2048Mb, and still it's failing to complete. It's failing when updating the pi system. For example, it just now failed updating 'firmware-misc-nonfree'. But, it's failed while updating other files, too. I don't think it's file-specific. —

[roblloyd319]

Success!

I used - sudo apt full-upgrade - and that worked.

[roblloyd319]

ORM seems to be installing now.

[roblloyd319]

Well, it's stuck again...

It stopped here -- 21% [11 python3-samba 327 kB/2,311 kB 14%] [7 samba-libs 4,838 kB/4,960 kB 98%] [13 samba-common-bin 0 B/620 kB 0%] [Connecting to raspbian.raspberrypi.org (2a00:1098:0:80:1000:75:0:3)

[Gordon-Shumway2]

Hi Rob,

you are correct, the 64bit OS will not work on a Pi Zero. As the RAM/swap issue was only present on the 64bit OS installation it is most likely not the cause of your issue on 32bit.

The fact that 'apt dist-upgrade' hangs as well shows that this is not really a ORM installation issue but rather a Pi issue.

What is strange in your installation is this line:

[Connecting to raspbian.raspberrypi.org (2a00:1098:0:80:1000:75:0:3)

Apparently this is the output of 'apt' - and it seems to attempt to connect to the IPv6 ip-address of 'raspbian.raspberrypi.org' rather than the IPv4 ip-address. There are some (older) postings on the internet where people experienced delays/hangups in such a scenario:

https://www.itsfullofstars.de/2019/02/apt-get-unable-to-connect-to-ipv6-address/
https://www.reddit.com/r/raspberry_pi/comments/7girsn/aptget_update_taking_forever_ipv6_issue/
https://mansfield-devine.com/speculatrix/2017/12/apt-get-and-the-curse-of-ipv6/

The workaround was to force apt to use IPv4 exclusively by adding

-o Acquire::ForceIPv4=true

to the apt command ie

 sudo apt -o Acquire::ForceIPv4=true dist-upgrade

You might want to try that. Mind you it is only a workaround and will not fix whatever is causing apt to use IPv6 and why that fails.

Cheers,
Michael

[roblloyd319]

The 'apt dist-upgrade' didn't hang. It finished the system upgrade OK.

The hang occurs when ORM is updating the Samba share files. Maybe from this line in the ORM install - 'sudo apt-get -y install samba samba-common-bin smbclient cifs-utils'

I skipped the Samba install (I use EXR --> Strava anyway and don't need the data direct from ORM). Now it finished the install and ORM is up and running again.

[Gordon-Shumway2]

Right, and that SMB file updating is just another apt call which hangs - most likely due to the IPv6 name resolution. Am 05.12.2022 um 20:44 schrieb roblloyd319:

…

The 'apt dist-upgrade' didn't hang. It finished the upgrade OK. The hang occurs when ORM is updating the Samba share files. — Reply to this email directly, view it on GitHub <#32 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASXHKG7L5F3BKJFEZ6AIRNLWLZAYFANCNFSM5J6EYK7A>. You are receiving this because you authored the thread.Message ID: ***@***.***>