This might perhaps be useful: http://www.linuxfromscratch.org/clfs/view/clfs-2.0/arm/cross-tools/glibc.html

Next try:

I edited /lib/systemd/system/boinc-client.service to include the Environment parameter (as the error points to locales).

[Unit]
Description=Berkeley Open Infrastructure Network Computing Client
Documentation=man:boinc(1)
After=network-online.target

[Service]
*Added line to test whether inclusion of the Environment parameter helps
Environment=LC_ALL=C
ProtectHome=true
Type=simple
Nice=10
User=boinc
WorkingDirectory=/var/lib/boinc
ExecStart=/usr/bin/boinc
ExecStop=/usr/bin/boinccmd --quit
ExecReload=/usr/bin/boinccmd --read_cc_config
ExecStopPost=/bin/rm -f lockfile
IOSchedulingClass=idle

Unfortunately I can't test this solution, as it seems the project has run out of WUs...

Tasks should now be available.
Can you check your suggestion on how to solve the problem?

It runs at the moment on a Cortex-A7 Raspberry Pi 2, with normal behaviour of the progress bar (in the past it jumped to 100% within a minute)
It promises to be ready in about 40 minutes from now.

Edit: After 25 minutes it is at 54% and wants another 22 minutes

Finished and validated: https://root.ithena.net/usr/result.php?resultid=101638

I can confirm that the 'Environment=LC_ALL=C' solution as described above/below (depending on your sorting) seems to work on the Models 3 and 4 too, WUs are being processsed.

with a picture Manjaro raspberry PI 4 it works properly

BCM2835 0.00 0 7.14.2 ARM
BCM2835 [Impl 0x41 Arch 8 Variant 0x0 Part 0xd08 Rev 3]
(4 processeurs) --- Linux Manjaro-ARM
Manjaro ARM Linux [4.19.83-1-MANJARO-ARM|libc 2.29 (GNU libc)]

16 Nov 2019, 11:57:43 UTC 16 Nov 2019, 12:32:59 UTC Terminé et validé 2,094.40 4.50 0.00 iThena CNode v1.17
aarch64-unknown-linux-gnu

Hi guys is the method mentioned by Dirk still the only way to get Raspberry pi's to run correctly here?
Mine just ran & ran without end until I aborted them.

Looking in the slot directory there was a file called check.dat being constantly created deleted & created again over & over every second.

I'd like to be sure this is still the correct course of action. So I presume you'd have to shut down the boinc client then edit boinc-client.service with Environment=LC_ALL=C is there any other steps involved for those of us new to the world of sudo? (ie: lacking linux skills)

Or is this perhaps a different problem? Any help would be greatly appreciated.

For those interested when I didn't get a reply from the admin I eventually went ahead and tried it out for myself & the answer is yes this method still works.
Using the information in Dirk Broer's post (message 103) I was able to get two raspberry pi 3's and four Pi 4's working here.

Thanks Dirk.

135UT / 135valids on my RPI :) (v1.17)

No mods: https://root.ithena.net/usr/results.php?hostid=465

FWIW

As mentioned by Dirk the hack is OS & Region dependant. In other words depending on what region you live in and OS you use you may or may not get this problem. Obviously this fix for those who "do" have the problem described above. The fix in my case worked a treat.

Funny observation:
On my 64-bit OS equipped ARM SBC's the only WU's that are failing appeared to be 32-bit WUs that landed there because i had added <alt_platform> lines to the cc_config.xml in order to run WCG.
I have added the line Environment=LC_ALL=C to /lib/systemd/system/boinc-client.service there now too.

---

135UT / 135valids on my RPI :) (v1.17)

No mods: https://root.ithena.net/usr/results.php?hostid=465

FWIW

Just a hunch:
You gave as Country France (or a French-speaking country), with language French, and choose for a French keyboard.
I gave as country the Netherlands, with language English and choose keyboard US -I hate keyboard NL layout, don't have them.

---

Just had a similar problem on my Raspberry Pi 3B+ and A+, seems to be correlated to locales and timezone as specified previously.

I was able to find quite a neat solution before stumbling upon this thread, if you are using systemd you can patch them in place (without modifying the original file) by creating a file named `/etc/systemd/system/boinc-client.service.d/environment.conf` with the following content:

[Service]
Environment=LANG=C
Environment=LC_ALL=C
Environment=TZ=UTC

This will force both the language to be the standard "C" locale and the timezone to be set to UTC (I needed all of that for some reason).

You can then just run

systemctl daemon-reload
systemctl restart boinc-client

and you should be able to run iThena WU fine.

It still kinda seems weird to me that I had to patch this system as I have a system set to UTC with the default en_us.UTF-8 locale set but whatever everything seems to work fine with that now.

If I may Dirk, I am currently in the process of moving some of my PIs to ARM64, do you have any input on how running arm32 and arm64 WU on the same host has been so far, any gotchas ? I'm thinking about running Universe@Home (arm32), WCG and LHC@Home on some of them.

---

If I may Dirk, I am currently in the process of moving some of my PIs to ARM64, do you have any input on how running arm32 and arm64 WU on the same host has been so far, any gotchas ? I'm thinking about running Universe@Home (arm32), WCG and LHC@Home on some of them.

The gotchas:
After adding to the cc_config.xml these lines:

<options>
   <alt_platform>arm-unknown-linux-gnueabihf</alt_platform>
   <alt_platform>armv7l-unknown-linux-gnueabihf</alt_platform>
</options>

and

sudo dpkg --add-architecture armhf
sudo apt update --fix-missing
sudo apt dist-upgrade
sudo apt install libc6:armhf libstdc++6:armhf zlib1g:armhf libfuse2:armhf

to be sure 32-bit libs are there when needed and, voilá: Boinc starts getting work for 32-bit apps.

Optional
Because I was unhappy with the memory assigned to the GPU in the case of a Jetson Nano (a mere 99MB) when using the default 5GB swapdisk I installed and configured ZRAM via

sudo apt install zram-config

and rebooted
Jetson-Nano2GB
Starting BOINC client version 7.9.3 for aarch64-unknown-linux-gnu *so no need to have this as alternate platform*
log flags: file_xfer, sched_ops, task
Libraries: libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Data directory: /var/lib/boinc-client
CUDA: NVIDIA GPU 0: NVIDIA Tegra X1 (driver version unknown, CUDA version 10.2, compute capability 5.3, 1979MB, 1343MB available, 236 GFLOPS peak) *CUDA! and enough RAM!**
OpenCL CPU: pthread-cortex-a57 (OpenCL driver vendor: The pocl project, driver version 1.1, device version OpenCL 1.2 pocl HSTR: pthread-aarch64-unknown-linux-gnu-GENERIC)
[libc detection] gathered: 2.27, Ubuntu GLIBC 2.27-3ubuntu1.4
Host name: Jetson-Nano2GB
Processor: 4 ARM ARMv8 Processor rev 1 (v8l) [Impl 0x41 Arch 8 Variant 0x1 Part 0xd07 Rev 1]
Processor features: fp asimd evtstrm aes pmull sha1 sha2 crc32
OS: Linux Ubuntu: Ubuntu 18.04.5 LTS [4.9.201-tegra|libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1.4)]
Memory: 1.93 GB physical, 4.97 GB virtual *ZRAM can deliver enough GB's here too*
Disk: 58.41 GB total, 12.05 GB free *This from a 64GB SD card and a somewhat bloated kernel -installed Debian Science, ALL*

---