I'm running one machine that can do 3 MCM WUs every 40 minutes. I'm definitely doing more WUs than they validate. Once they catch up I should get my 2 yr badge easily. It will be fun to finally see how much I have done and get that number. How close am I to 3 years (no badge)?

According to the last update they have working validators that they will run this coming week to work through all the WUs we have been returning. I decided to make it a challenge for them to see how much I could stack up. I think the newer WUs are validating quickly once 2 results are returned.

I've just spotted an odd WU, it's In Progress but the OS is recorded as :-

Linux wsl: Failed to start the systemd user session for 'boinc'. See journalctl for more details.

I guess I'll just have to wait until it times out before I get a matching pair.

https://www.worldcommunitygrid.org/contribution/workunit/787683452

We're back to an old problem again "Another scheduler instance is running for this host"

Of course, that means no new tasks will be sent, and finished tasks can't be reported.

Edit, added: I reported the issue to the WCG team.

Looks like we are back to normal. that was a quick outage. Thanks for the quick reports from Grumpy Swede and bfmorse. We are the status app until they get the official one working.

Regarding misidentified Operating Systems...

As Bryn Mawr may have seen by now, the WU highlighted in that post has ended up in PVal jail with one Windows run (the oddity) and one legitimate Linux run -- it's a good job Homogeneous Redundancy (HR) isn't a big issue for MCM1 :-)

That is just one of many different cases that the WCG folks will have to be able to recognize somehow if they try to retain *true* Homogeneous Redundancy (essential for ARP1...) -- looking back through the posts here since the start of December, there has been quite a bit of discussion on this.

WCG are probably well aware of many of these variants, as they can periodically sift the hosts table looking at the os_name and os_version fields for items that don't match up to certain expected patterns[*1] -- unfortunately, the BOINC scheduler seems to trust what it is told so it doesn't reject stuff that doesn't actually make sense.

I have seen quite a few variants amongst my wingmen -- I tried to post some samples to show what WCG (and other BOINC sites) are up against, but invariably got told I was Forbidden -- sighs of relief from readers

However, I also see some wingmen reporting WSL2 that have run a Linux executable, so if someone is trying to run a Linux client on Windows it can be made to work (WSL2 only?) -- I suspect the issue here is folks who've followed Berkeley's "advice" and installed a Docker variant

Cheers - Al.

*1 Properly set up hosts return os_name and os_version in consistent formats that are easy to parse