In reply to dskagcommunity's message of 24 Apr 2026:

I have tried, id failed so hard i had to detach fully from the project and reattach cos boinc manager still said "Download stalled" and thinking the files are still not there. no matter what i was doin. restart client etc. So i think that status on live files is stored anywhere.

You did shut down BOINC totally before you copied the files I hope. If you still had BOINC running, it still will think that the files are missing, and try to download them. Apart form the .exe files, you also have to copy the MCM data file e55b6bdba4ed0b4b6e315c6767d68e3f.txt Also of course while BOINC is shut down.

Tasks finished,ready to report but message says Unable to Open Database. An early start to the weekend I think.

I keep getting

Turin 9755 EPYC 128c
1355 World Community Grid 4/24/2026 8:16:07 PM Scheduler request to https://scheduler.worldcommunitygrid.org/boinc/wcg_cgi/fcgi failed: HTTP service unavailable

I have 1393 tasks in this mode.

At the moment it's basically broke. The last time it came awake long enough for me to upload a bunch of tasks, how many I can't say.
Oh, and don't believe that BSRAC (whatever that means exactly) their software played an April Fools prank on me and credited me with an extra 85,000,000 credits. Then took them away a day later...but they hung around long enough to skew that number.

---

Don't know what WCG is doing but its definitely BROKEN with no new information.on what they are doing.

Yesterday I had received 3 tasks, ran to completion & couldn't upload. Overnight, the WCG servers woke up and cancelled my tasks before I could upload them.

In reply to Dr Who Fan's message of 25 Apr 2026:

Don't know what WCG is doing but its definitely BROKEN with no new information.on what they are doing.

Yesterday I had received 3 tasks, ran to completion & couldn't upload. Overnight, the WCG servers woke up and cancelled my tasks before I could upload them.

I had 60 tasks, waiting to upload, and during the night when the WCG server woke up, they were uploaded and reported. They are not possible to see though, on the Results page, because the legacy server (MariaDB), is no longer the production DB. The production DB is now a PostgreSQL database, and it is not yet in sync with the old legacy BOINC MariaDB, from where all the stats data comes. We're all waiting for the MariaDB to be in sync withe the production PostgreSQL database.

The one task I had waiting to report seems to have done so according to the event log around 930 this morning (UCT)

I see my 2 Android phones have received several _2 & _3 (resend) tasks in last few hours. Cross our fingers and toes the database and servers stay connected and working for the weekend.

My Project Contribution stats have altered by some eight days and I notice that Free-DC stats have been updated as well and the 3 tasks I had waiting to report have gone as well. Long may it continue.

WCG website as of now:

System error
World Community Grid is currently experiencing an unexpected error. Please check Facebook or Twitter for more information.

Edit: Back, but the Results Page is just spinning its wheels, showing nothing. Not that the Results Page is synced with the production DB, but.....

Well, that did not last. The website have been down for a pretty long time now, and all validations seems to have stopped.
BOINC connections works though, and no problems to upload, report, and request new tasks.

WCG is still a Yo-Yo project, no doubt about that.

Still seems to be doing something over 46000 in the last 24 hours. No update on Free-DC as far as I can tell.

I had to rebuild one of my crunchers the other day. It fails downloading the same 11 files needed. All the .tga, wcgrid_mcm1_gfx_7.61_windows_x86_64 and wcgrid_mcm1_map_7.61_windows_x86_64

In reply to just1vet's message of 27 Apr 2026:

I had to rebuild one of my crunchers the other day. It fails downloading the same 11 files needed. All the .tga, wcgrid_mcm1_gfx_7.61_windows_x86_64 and wcgrid_mcm1_map_7.61_windows_x86_64

You can copy the files from another machine of the same architecture.

Tried that for about 2 hours in everyway that I thought it might work last night. Kept getting a message of download stuck.

In reply to Hadrian's message of 27 Apr 2026:

No update on Free-DC as far as I can tell.

Just lucky I guess. I've shown updates for the last 3 days. Based on the amounts, 1-1.4M per day, they're doing something with the backlog. Or they're gonna prank me again.

In reply to just1vet's message of 27 Apr 2026:

Tried that for about 2 hours in everyway that I thought it might work last night. Kept getting a message of download stuck.

Go figure. I just went and tried that copy over again, and it worked.

---

The validators are running again. Credits increasing as expected in BOINC. Very good. Lots of work available, still mostly resends though.

Hi hello.. I am haveing the same problem with HTTP errors and stalled down load messages.. To only fail at trying to fix this, I have updated boinc, and reset the project.. but right know all I know... WCG isn't working.. As of 4/29/2026 for me..

Update on https://www.cs.toronto.edu/~juris/jlab/wcg.html
April 29, 2026
BOINC traffic resumed around 12:30 UTC on April 25th, 2026 and cluster is currently stable as of this writing (18:00 UTC on April 29th, 2026) - the issues at the data center was resolved, recovery was successful and the issues causing large numbers of 404s on download and 503s on upload unrelated to the issue at the data center were both resolved as well. We implemented backpressure for the validators, juggled some services like the backfill validations off the database cluster nodes to other nodes in the cluster, further tuned postgres for our workload, and modified some BOINC components to harden the cluster against future outages.
BOINC stats export to https://download.worldcommunitygrid.org/boinc/stats resumed - server status page will follow once ARP1 and MAM1 are up and running again.
IN_PROGRESS results do not display on the website - until the credit_flusher batch upserts those rows into the legacy MariaDB database after validation, these workunits are not visible to the website APIs. We are working to add to the Results API a fetch and cache from the new BOINC database postgres cluster so that these IN_PROGRESS results can be seen on the website and retrieved from the APIs. Likely, this fix will conincide with improvements to allow users with Result sets large enough to timeout the API to see or at least download their results, and fixes and tooltips for the new Summary feature on the Results page.
Data Sharing radio button does not work - thank you for the report, working to fix this.
403 Forbidden - frustrating forum users - when we fixed the team challenge registration, the issue causing 403 Forbidden on that page was the updated mod-security rules for apache2 on the load balancer server. We will start there and look at the mod-security rules from load balancer through to the container that hosts the website behind HAProxy which also has it's own set of rules, and hopefully provide relief soon.
When will ARP1 be released? - current blocker is the geographical split with overlapping edges between regions to match our partitioned backend, so that downloads and uploads will be routed to a mostly contiguous geographic region of the overall sub-Saharan region for which the project is predicting the weather. As this involves fetching ARP1 results across boundaries of those mostly contiguous regions so that "halo" domains can have their next generations of workunit inputs generated from the completed work of all their neighbours within, and the neighbours across the partition border, it requires more devleopment and testing. Now that we are seeing stability in the new architecture, this is a priority and we will update as we get a better sense for the exact timing. We may release workunits that are completely within a geographic partition to test the ARP1 BOINC components in general, before we can announce that the project is back up and running.
When will MAM1 and the GPU build "MAMG" workunits be released? - while MAM1 and the corresponding beta30 project are up to date with the MCM1 pipeline and could have work issued at any time, we are exploring the options afforded to us by upgrading our BOINC build such as the BOINC Universal Docker App "BUDA" (https://github.com/BOINC/boinc/wiki/BUDA-overview), and also using Mojo with the existing LibTorch support within the application to run on newer AMD and NVIDIA GPUs https://docs.modular.com/max/develop/custom-kernels-pytorch). We expect to start sending out batches of MAM1 workunits for the mt CPU build through the beta30 app and possibly the MAM1_9999900+ testing range this week, barring some new blocker, and will update on GPU support as we release new builds through the beta30 application.

---

Paul.