Instead of complaining here about the lack of stats update, take it up with the WCG Administrators on the WCG project forums.

November 21, 2025

We are testing required changes to the scheduler and feeder to resolve the corrupt/truncated "os_name" and "os_version" entries such as "W"/"W" for some hosts, as reported by users in the forums, and to resolve frequent "stuck" feeder states where "No tasks available for platform" is logically incorrect by hr_class, yet the tasks populating the feeder shared memory segment remain unassigned by the scheduler passes and manual intervention is required to get work flowing again.
Passes through uploaded results that have not been credited by the new system will begin next week, to backfill missing credits. We have been performing dry runs to establish correctness. As a precaution, we will be running the program in multiple passes starting with the oldest uploads, to the most recent.
Volunteers have reported that the API sometimes shows an invalid state for multiple results, where only one result is marked valid, which should be impossible. Preliminary investigation points to the new MCM1 assimilation procedure interacting with the transitioner. The new MCM1 assimilation procedure acts to validate and credit all in progress results for a workunit as soon as it has consumed any pair/quorum of files, whether original 0 and 1 results or resends 2 and up, that have passed validation. We will review this issue in full and report our findings, whether a bug in the assimilator, or poorly modeled interaction between assimilator transactions and the transitioner, which is where we expect to find an explanation.
https://www.cs.toronto.edu/~juris/jlab/wcg.html

---

Paul.

Server error: feeder not running.
That's been going on now for at least 8 hours.

So, no new work is available, and reporting is not possible.

In reply to Grumpy Swede's message of 23 Nov 2025:

Server error: feeder not running.
That's been going on now for at least 8 hours.

That seems to be fixed now.

So, no new work is available, and reporting is not possible.

That is not yet fixed.

---

A few hours later....

All stalled tasks reported, and new ones arrived.
Not checked on the pile of unvalidated tasks that were up there doing nothing.

Not checked on the pile of unvalidated tasks that were up there doing nothing.

Just checked.
Quite a few of my older tasks have now validated. I notice quite a lot of my android tasks are down as errors. However, if I were doing more than a minimal amount of crunching for WCG the number of unvalidated tasks would be growing fast.

In reply to Jean-David's message of 24 Nov 2025:

Server error: feeder not running.
That's been going on now for at least 8 hours.

Just to show my ignorance. Where do I find the current status of the servers? I just brought up a, new, simple little computer and it has nothing to do.

---

Just to show my ignorance. Where do I find the current status of the servers? I just brought up a, new, simple little computer and it has nothing to do.

WCG does not have a BOINC or other Server Status Web Page... It's something they mentioned several weeks ago they are 'working on implementing for the "future."

The closest we have is a forum by one of the volunteers titled Project Status (First Post Updated). View the First Post for a rough idea what type of work has been sent out in the last 24 hours.

I notice, I am not getting any work for my Linux host. Only for Android and my Windows VM.

WCG does not have a BOINC or other Server Status Web Page... It's something they mentioned several weeks ago they are 'working on implementing for the "future."

Sadly, back in the IBM days, lost in the mists of time, they customised the BOINC server code out of all recognition. I suspect there are many who think they should have converted back to vanilla boinc server when IBM stopped hosting and funding them.

In reply to Dave's message of 26 Nov 2025:

WCG does not have a BOINC or other Server Status Web Page... It's something they mentioned several weeks ago they are 'working on implementing for the "future."

Sadly, back in the IBM days, lost in the mists of time, they customised the BOINC server code out of all recognition. I suspect there are many who think they should have converted back to vanilla boinc server when IBM stopped hosting and funding them.

I would be in that group. It's the only project where you cannot find a host by the most recent contact between host and server.

This is new?
Wed 26 Nov 2025 07:50:36 PM MST | World Community Grid | This computer has finished a daily quota of 5 tasks

---

I'm another one of those think that many of WCG's problems today reside in the IBM demolition of BOINC. Everything from the user interface to the underlying database has been affected.

In reply to bill's message of 27 Nov 2025:

This is new?
Wed 26 Nov 2025 07:50:36 PM MST | World Community Grid | This computer has finished a daily quota of 5 tasks

That is a message, I normally associate with a machine that is failing all tasks. I can't remember if it resets at midnight local or UTC. (Currently the same for me.)

Thanks I guess? :-) I spotted it on a computer I'd just done the install/boot/add stuff to. The message(s) has/have gone away and the computer seems to be puttering along fine at it's own pace. I'll watch it for a few days and then do the OS upgrade on it, it's fated to become my year-round test bed/summer frequent traveler.

Bear in mind that WCG started with United Devices before BOINC.
The system had to cope with that so was customized more than most.

---

Paul.

In reply to PMH_UK's message of 27 Nov 2025:

Bear in mind that WCG started with United Devices before BOINC.
The system had to cope with that so was customized more than most.

I had to look up the Wikipedia entry for United Devices. Porting another system onto the BOINC server software goes a long way to explaining why their setup is so different from all the others I have looked at.

In reply to PMH_UK's message of 27 Nov 2025:

Bear in mind that WCG started with United Devices before BOINC.

SETI existed before BOINC too. That's not an excuse

The United Devices client was nothing like WCG or BOINC and has been dead for decades. Several other projects do not use the standard BOINC server setup but are not has bad.

WCG is suffering from the Sahara and Atacama disease once again.
The disease broke out Sunday morning at about 06:45 UTC.
Antibiotics did not help.

A specialist doctor will visit the patient Monday December 1:st.

New work was sent out at 2025-12-01 20:52 UTC. I got 120 tasks for one already running computer, but when I started another computer it's just "no tasks are available".

Either the same issue came back almost immediately, or every empty computer is trying to get new work at the same time.