Page 1 of 1

WU's 19421 exceed timeout on a Rasperry Pi

Posted: Mon Apr 24, 2023 12:24 pm
by ETA_2025
WU 19421 is exceeding the timeout of 2 days, on my Raspberry Pi hardware. It's taking about 2 days and 6.5 hours for the Pi's to complete these WUs.

The very first of these WUs was issued on April 21 @ 0:45.

Is this a problem or not?

Re: WU's 19421 exceed timeout on a Rasperry Pi

Posted: Mon Apr 24, 2023 6:24 pm
by JimboPalmer
The minimum Raspberry pi is version 4. If you are on a lower version, it is unsupported.

Re: WU's 19421 exceed timeout on a Rasperry Pi

Posted: Tue Apr 25, 2023 9:37 am
by ETA_2025
JimboPalmer wrote: Mon Apr 24, 2023 6:24 pm The minimum Raspberry pi is version 4. If you are on a lower version, it is unsupported.
Jimbo, had you looked at my Hardware configuration, you would have noticed that I have 10 BCM2711 processors. The Raspberry Pi 4 is the only Pi to use these processors!

Re: WU's 19421 exceed timeout on a Rasperry Pi

Posted: Tue Apr 25, 2023 12:48 pm
by JimboPalmer
Unless you post your log, no one can look at your hardware configuration. We can only give advice based on information you provide.

Re: WU's 19421 exceed timeout on a Rasperry Pi

Posted: Tue Apr 25, 2023 1:45 pm
by Joe_H
ETA_2024 wrote: Tue Apr 25, 2023 9:37 am
JimboPalmer wrote: Mon Apr 24, 2023 6:24 pm The minimum Raspberry pi is version 4. If you are on a lower version, it is unsupported.
Jimbo, had you looked at my Hardware configuration, you would have noticed that I have 10 BCM2711 processors. The Raspberry Pi 4 is the only Pi to use these processors!
Yes, that info is there. But posted in the most obtuse manner possible.

Re: WU's 19421 exceed timeout on a Rasperry Pi

Posted: Tue Apr 25, 2023 3:10 pm
by ETA_2025
Joe_H wrote: Tue Apr 25, 2023 1:45 pm
ETA_2024 wrote: Tue Apr 25, 2023 9:37 am
JimboPalmer wrote: Mon Apr 24, 2023 6:24 pm The minimum Raspberry pi is version 4. If you are on a lower version, it is unsupported.
Jimbo, had you looked at my Hardware configuration, you would have noticed that I have 10 BCM2711 processors. The Raspberry Pi 4 is the only Pi to use these processors!
Yes, that info is there. But posted in the most obtuse manner possible.
Fixed Joe.

And, I'm still waiting for an answer to my question!

Re: WU's 19421 exceed timeout on a Rasperry Pi

Posted: Mon May 01, 2023 8:33 am
by ETA_2025
Will someone please answer my question in the first post.

Re: WU's 19421 exceed timeout on a Rasperry Pi

Posted: Mon May 01, 2023 6:21 pm
by toTOW
I notified the researcher ...

There are so many projects that shouldn't assign on RPi ... :roll:

Re: WU's 19421 exceed timeout on a Rasperry Pi

Posted: Mon May 01, 2023 6:34 pm
by ayanb73
We have added a constraint on the project to prevent this from happening. Thank you for bringing it to our attention.

Re: WU's 19421 exceed timeout on a Rasperry Pi

Posted: Tue May 02, 2023 8:40 am
by ETA_2025
toTOW wrote: Mon May 01, 2023 6:21 pm I notified the researcher ...
ayanb73 wrote: Mon May 01, 2023 6:34 pm We have added a constraint on the project to prevent this from happening. Thank you for bringing it to our attention.
I assume WUs that exceed the timeout are a problem.

Thanks toTOW and ayanb73 for fixing that problem.

Re: WU's 19421 exceed timeout on a Rasperry Pi

Posted: Tue May 02, 2023 4:05 pm
by toTOW
ETA_2024 wrote: Tue May 02, 2023 8:40 am I assume WUs that exceed the timeout are a problem.
They slow down the science and waste some power since the work unit will be computed twice ...

Re: WU's 19421 exceed timeout on a Rasperry Pi

Posted: Mon May 08, 2023 10:22 am
by ETA_2025
toTOW wrote: Mon May 01, 2023 6:21 pm I notified the researcher ...

There are so many projects that shouldn't assign on RPi ... :roll:
ayanb73 wrote: Mon May 01, 2023 6:34 pm We have added a constraint on the project to prevent this from happening. Thank you for bringing it to our attention.
Should my Raspberry Pi's still be getting these WUs?

The last WU was assigned on May 7 @ 23:27Z

Re: WU's 19421 exceed timeout on a Rasperry Pi

Posted: Mon May 08, 2023 6:15 pm
by ayanb73
We have updated our constraint to exclude ARM and ARM64. Hopefully this should now fix the issue