Problems with WCG today. It started with a BOINC problem "Another scheduler instance is running for this host"
Several users posted about that issue on the forum.

Now the entire Website is "ERR_CONNECTION_TIMED_OUT"

Now the entire Website is "ERR_CONNECTION_TIMED_OUT"

Though I am getting work at the moment. I will take that as a win even if I can't look at the website!

Edit: Website is back up.

In reply to Dave's message of 16 May 2025:

Now the entire Website is "ERR_CONNECTION_TIMED_OUT"

Though I am getting work at the moment. I will take that as a win even if I can't look at the website!

Edit: Website is back up.

Yeah, it's all back. However getting new tasks is a bit of a hit and miss. Mostly due to the ongoing BOINC Pentathlon 2025 marathon challenge.

Yeah, it's all back. However getting new tasks is a bit of a hit and miss. Mostly due to the ongoing BOINC Pentathlon 2025 marathon challenge.

Not sure I can tell the difference. Using four in one here which helps grab tasks. Host machine 25.04, 3 VM's Tiny10, 25.04 and 25.10beta.

And no one getting anything bar the occasional resend of MCM tasks. I will need to find another use for all that free electricity from my roof.

And now I have one task trying to download but all downloads failing. Website also dead when I try and go to fora.

Fora have returned. I now have an MCM task with stuck downloads as well as an ARP one. About 5 of the ARP downoads did get through before everything stalled again.

And a few more just made it through. I suspect congestion as everyone tries to complete their downlods is happening.

Another scheduler instance is running for this host <---<<<

Is it you, or is it me?

This is when it started and has been like this ever since.

Thu 19 Jun 2025 04:34:17 AM EDT | World Community Grid | Sending scheduler request: To fetch work.
Thu 19 Jun 2025 04:34:17 AM EDT | World Community Grid | Requesting new tasks for CPU
Thu 19 Jun 2025 04:34:18 AM EDT | World Community Grid | Scheduler request completed: got 0 new tasks
Thu 19 Jun 2025 04:34:18 AM EDT | World Community Grid | No tasks sent
Thu 19 Jun 2025 04:34:18 AM EDT | World Community Grid | No tasks are available for OpenPandemics - COVID 19
Thu 19 Jun 2025 04:34:18 AM EDT | World Community Grid | No tasks are available for OpenPandemics - COVID-19 - GPU
Thu 19 Jun 2025 04:34:18 AM EDT | World Community Grid | No tasks are available for Africa Rainfall Project
Thu 19 Jun 2025 04:34:18 AM EDT | World Community Grid | No tasks are available for Mapping Cancer Markers
Thu 19 Jun 2025 04:34:18 AM EDT | World Community Grid | Tasks for NVIDIA GPU are available, but your preferences are set to not accept them
Thu 19 Jun 2025 04:34:18 AM EDT | World Community Grid | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
Thu 19 Jun 2025 04:34:18 AM EDT | World Community Grid | Tasks for Intel GPU are available, but your preferences are set to not accept them
Thu 19 Jun 2025 04:34:18 AM EDT | World Community Grid | Project requested delay of 121 seconds
Thu 19 Jun 2025 04:54:21 AM EDT | World Community Grid | Starting task MCM1_0238377_3062_0
Thu 19 Jun 2025 05:01:28 AM EDT | World Community Grid | Sending scheduler request: To fetch work.
Thu 19 Jun 2025 05:01:28 AM EDT | World Community Grid | Requesting new tasks for CPU
Thu 19 Jun 2025 05:01:29 AM EDT | World Community Grid | Scheduler request completed: got 0 new tasks
Thu 19 Jun 2025 05:01:29 AM EDT | World Community Grid | Another scheduler instance is running for this host <---<<<
Thu 19 Jun 2025 05:01:29 AM EDT | World Community Grid | Project requested delay of 121 seconds

---

https://www.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=704358

...scheduler requests use a per-host lock file to ensure that there aren't two concurrent requests from one host. The file is created at the start of the request, holds the PID of the scheduler instance, and is deleted at the end of the request.

There are two possible error conditions, one of which is that the lock file can't be acquired in the first place, the other that there is an existing lock. Unfortunately, although the message written to the server log distinguishes the two cases, the message sent to the client does not.

In this case, I suspect the issue is an inability to create the lock file in the first place :-(

---

Paul.

Thank-you.

---

Another scheduler instance is running for this host <---<<<

Same problem... Have seen it before and ...
This is more than likely an issue with the WCG SERVERS.
In fact it happened a little more than 1 month ago Posted: 16 May 2025, 15:16:27 UTC

All you can do is wait for Krembil to fix it on their end.