Raspberry Pi stopped receiving 64 bit jobs... or any jobs.
25 Mar 2022 0:27:11 UTC
Topic 227262
(moderation:
I have two almost identical RPis.
# One only has 4GB of ram and is running the Raspbian Buster.
# Two has 8GB of ram and is running the newly available (non-beta) AARCH64/ARM64 bit version. (Bullseye).
After getting 28, 404 bricks #Two stopped receiving any jobs. I have subsequently deleted and reinstalled BOINC and signed up for Einstein@Home, and still no jobs.
Pi #1 with Buster is still merrily chucking away, but once the Bullseye Pi finished all of its jobs it hasn't been issued any new ones.
I am pretty sure the AARCH64 one could run 32 bit or 64bit jobs but isn't receiving either. (I would prefer ones that use the 64bit ALU and all the registers).
Ronald McNichol wrote: I
)
Did you check the box to receive Beta tasks?
BETA SETTINGS
Run test applications?:
YES
NO
Because if not you won't get any tasks for your RPi's, they upgraded the app as the old one was failing on the newer RPi's and the newer one is still being tweaked. You may also need to reset the Project, you will lose any existing Einstein tasks on the machines you do this on, but it will also force the Project to send you the newer app.
Thanks for your prompt
)
Thanks for your prompt reply.
My Pi 4 with the 32 bit OS is still merrily chugging away and receiving new tasks.
My Pi 4 with the 64 bit OS is the one no longer receiving tasks but is still getting new credits as pending results are validated.
The 64-bit one stopped receiving new tasks about 3 days ago now but finished all that had been sent before it went quiet.
I made the changes you suggested, and the 64 bit one is still not being utilized.
As far as I know, the 64-bit one can still run 32-bit jobs, basically, the same jobs as the 32-bit OS one.
Both CPUs are identical except for the OS and an additional 4GB of memory in the one that isn't chugging away.
Keep hitting update on that
)
Keep hitting update on that host. Do you have other projects hogging the resource so Einstein can't get a shot?
What does sched_op_debug flag in Event Log options show?
What does work_fetch_debug flag show?
When they deprecated the 1.60 app and I set beta I immediately got the 1.61 beta app. I have 3 in progress sent today.
Before it quit getting new
)
Before it quit getting new jobs it did 169 of these, starting on Feb 9 'til 3 days ago.
Binary Radio Pulsar Search (Arecibo) v1.60 aarch64-unknown-linux-gnu
Note the aarch64. The 32-bit Pi does the same job except for the 64 bit part.
I started this because my 3 Pis are on 24/7 and only my file server had a job.
As I stated earlier,
)
As I stated earlier, that Binary Radio Pulsar Search (Arecibo) v1.60 aarch64-unknown-linux-gnu app is no more.
No more work will be sent for that app. This is the current app:
Binary Radio Pulsar Search (Arecibo) v1.61 aarch64-unknown-linux-gnu
If you want to crunch BRP4 on your Pi4 you need to toggle use beta applications in your Project Preferences for the venue/location that the Pi4 is on.
Project Preferences - Combined venues
Check that the Pi4 is actually in the location that you think you toggled beta applications. I'd wager it isn't and the reason you are not getting any work.
I also enabled beta today and
)
I had set beta, but apparently, it didn't stick. I set it again. And also unchecked use for new computers, which I guess I didn't understand when I checked it. It is NOW DLing a bunch of jobs to crunch. Thanks for your help.
Ronald McNichol wrote:I had
)
Happy crunching!!
Now if I could get my ChromeBook to crunch that would be helpful too, I will have to recheck my own settings!!
edit...yup a couple of wonky settings so hopefully by noon my time today it will br crunching some tasks!!
3 tasks are now running on my Chromebook, I forgot it needed to be plugged in to run but that too is now fixed