Thread 'All workunits failed.'
Message boards : Number crunching : All workunits failed.
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 4 Apr 23 Posts: 17 Credit: 168,279 RAC: 0 |
I was surprised to see BOINC Central had downloaded a set of work units. All of them failed quickly however, so no new tasks set. >>> 1 (0x00000001) Unknown error code |
|
Send message Joined: 4 Apr 23 Posts: 17 Credit: 168,279 RAC: 0 |
I re enabled downloads yesterday evening, and since then, work units have run normally. Dodgy batch perhaps? |
|
Send message Joined: 14 Oct 25 Posts: 1 Credit: 25,763 RAC: 0 |
I got this message: https://boinc.berkeley.edu/central/result.php?resultid=949188 <core_client_version>8.2.4</core_client_version> <![CDATA[ <message> exceeded elapsed time limit 50217.18 (371520.00G/7.40G)</message> <stderr_txt> no job.toml config file Using WSL distro boinc-buda-runner Using podman got quit/abort from client </stderr_txt> ]]> Running Podman version 5.6.1 No tasks survived 😢 |
|
Send message Joined: 21 Sep 25 Posts: 1 Credit: 0 RAC: 0 |
Same here. Deleted the open tasks and set to "no new tasks" until it is clearly resolved. |
|
Send message Joined: 10 Jun 25 Posts: 3 Credit: 50,956 RAC: 0 |
Admins. Your new app version for Windows has a error. All workunits fail. |
 Send message Joined: 26 Nov 21 Posts: 52 Credit: 1,827 RAC: 0 |
Folks, thank you for reporting this issue. Could you please specify if you are using our 'boinc-buda-runner' image ? Could you please also run this installer that will install (or update existing one to) the latest version of 'boinc-buda-runner' image? Also, it would be awesome if you could also test the latest 8.2.7 alpha release of BOINC that contains some improvements that might affect running docker tasks in a positive way. This will help us idenrifyng and fixing the issue. Thank you in advance. BOINC maintainer. For any insight, check my BOINC Development Blog. |
|
Send message Joined: 10 Jun 25 Posts: 3 Credit: 50,956 RAC: 0 |
In reply to Vitalii Koshura's message of 14 Nov 2025: Folks, thank you for reporting this issue. I was already running the boinc-buda-image. I have now installed the new version of that image as suggested and with that new version I don't have anymore a immediate failure, so things are beter. I will let you know if it will finish and validate. PS. It is not a very good way of software management if you upgrade a application that has a dependence without any kind of warning. |
|
Send message Joined: 10 Jun 25 Posts: 3 Credit: 50,956 RAC: 0 |
In reply to Henk Haneveld's message of 14 Nov 2025: In reply to Vitalii Koshura's message of 14 Nov 2025: Update: The result has endend with success and is validated. I suggest you post a general warning in the notices tab for all Windows users to install the new boinc-buda-runner image. |
|
Send message Joined: 26 Nov 21 Posts: 52 Credit: 1,827 RAC: 0 |
In reply to Henk Haneveld's message of 14 Nov 2025: In reply to Vitalii Koshura's message of 14 Nov 2025: This was not supposed to be a breaking change. And I even don't really know what can go wrong since the changes were trivial. Thank you for testing this. BOINC maintainer. For any insight, check my BOINC Development Blog. |
 Contact Send message Joined: 19 Feb 23 Posts: 16 Credit: 332,725 RAC: 0 |
BOINC 8.2.7 has magically fixed all my hosts on BOINC Central. I had to re-run the very intelligent new buda installer on one host for BOINC to recognize that WSL. The installer removed the old WSL image and reinstalled. BOINC then saw a usable WSL and downloaded and completed valid BOINC Central tasks again. All other hosts just started downloading BOINC Central tasks and returned valid results again. During testing of 8.2.6 all my hosts started to return invalid results or no usable WSL and I couldn't fix that. Re-running the new installer with BOINC 8.2.6 (and even after reverting back to 8.2.4) still returned invalid results or no usable WSL, even though everything looked great. I have no clue why that is. |
