Not sure if all of this was getting sent out as notices or not. That has happened in the past. Apologies if it was, I've turned that off now.

I'm not getting the "feeder down" message any more but I'm not getting any WU either. Just "Scheduler request completed: got 0 new tasks"
I suppose it will pick up in a bit.

I was able to finally upload some completed WU's though. So that's a plus.

Thanks again!

Glad to hear it, that means that something is going right, at least. I'll keep monitoring things just in case.

I actually did get some work units on all 4 of my computers

---

@ Tom:

Okay, I've restarted things. Is the feeder still down for you?

Sorry for the delay.
Things are working now.
Many thanks - good work!

Another area of confusion for who was looking where. Here is the current Time Stamp from the bottom of the Server Status page... showing yesterdays date and status.

Another process to restart

Upstream server release: 1.0.4
Database schema version: 27028
Task data as of 27 Mar 2022, 18:54:47 UTC

Thanks
Bill F
Dallas TX

---

In October of 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

anyone getting any resends? I'm only getting _0 WUs. I'm not complaining, I'm so happy to be getting WUs again.

Thank you Tom!

And I spoke too soon. I'm not getting any WUs now. doesn't seem to be an error, just that there are no WUs to send.

@ Bill:

Another process to restart

Upstream server release: 1.0.4
Database schema version: 27028
Task data as of 27 Mar 2022, 18:54:47 UTC

Thanks
Bill F
Dallas TX

Seems to be fixed!
It is now 29 Mar 2022, 2:23:27 UTC

AND Backlog is 0.00

@ Tom:

Glad to hear it, that means that something is going right, at least. I'll keep monitoring things just in case.

... back to the workbench ...

Good work Tom, but
I'm not able to get new work.
Well, not quite, two of eight rigs got work, but the six others have not - no matter what I do.
There is enough work to be sent.

The task page takes very long to react, but when it does, it shows that tasks numbers are changing/moving.

It would be nice to have the "Project status" updated every hour. Was that not the way it used to be?

@ Tom,

Same here :

29/03/2022 09:21:30 | Milkyway@Home | Sending scheduler request: To fetch work.
29/03/2022 09:21:30 | Milkyway@Home | Requesting new tasks for AMD/ATI GPU
29/03/2022 09:21:32 | Milkyway@Home | Scheduler request completed: got 0 new tasks
29/03/2022 09:21:32 | Milkyway@Home | Project requested delay of 91 seconds

Yes, unfortunately, something is still not quite right with the server. I can confirm that none of my hosts are getting work (as per the two previous posts). Yesterday, after a lot of manual requests I got a handful of WUs (far less than the max amount per host) and that was it. No work since then.

All 4 of my computes are getting new work units on a regular basis so it seems to be fine with me.I wish the work units were validated a little faster then they are now but at least we are making progress on getting the work units to be validated

---

Doesnt want to send me any work. Says no tasks available for Separation when there is nearly 5 Million. Machine has been waiting for nearly an hour.

Still not getting work:

3/29/2022 1:12:07 PM | Milkyway@Home | Sending scheduler request: To fetch work.
3/29/2022 1:12:07 PM | Milkyway@Home | Requesting new tasks for NVIDIA GPU
3/29/2022 1:12:09 PM | Milkyway@Home | Scheduler request completed: got 0 new tasks
3/29/2022 1:12:09 PM | Milkyway@Home | Project requested delay of 91 seconds
3/29/2022 1:16:57 PM | Milkyway@Home | work fetch suspended by user
3/29/2022 1:17:06 PM | Milkyway@Home | work fetch resumed by user
3/29/2022 1:18:01 PM | Milkyway@Home | update requested by user
3/29/2022 1:18:05 PM | Milkyway@Home | Sending scheduler request: Requested by user.
3/29/2022 1:18:05 PM | Milkyway@Home | Requesting new tasks for NVIDIA GPU
3/29/2022 1:18:07 PM | Milkyway@Home | Scheduler request completed: got 0 new tasks
3/29/2022 1:18:07 PM | Milkyway@Home | Project requested delay of 91 seconds

Very strange ...

EDIT:
Now I am getting
3/29/2022 1:44:59 PM | Milkyway@Home | work fetch resumed by user
3/29/2022 1:45:00 PM | Milkyway@Home | Sending scheduler request: To fetch work.
3/29/2022 1:45:00 PM | Milkyway@Home | Requesting new tasks for NVIDIA GPU
3/29/2022 1:45:01 PM | Milkyway@Home | Scheduler request completed: got 0 new tasks
3/29/2022 1:45:01 PM | Milkyway@Home | No work available
3/29/2022 1:45:01 PM | Milkyway@Home | Project requested delay of 91 seconds
NO WORK AVAILABLE ??

Doesnt want to send me any work. Says no tasks available for Separation when there is nearly 5 Million. Machine has been waiting for nearly an hour.

Still nothing through.

I am finding the same as San Fernando Valley did all those things still nothing.

It says 600 in progress:
State: All (82650) · In progress (600) · Validation pending (28154) · Validation inconclusive (8569) · Valid (45223) · Invalid (0) · Error (104)
Application: All (82650) · Milkyway@home N-Body Simulation (0) · Milkyway@home Separation (82650)
I wish I could find out where they are.
None of my rigs show any tasks.

Stopped BOINC on all rigs (aka PC).
Restarted my rigs.
Started BOINC on all rigs.
NOTHING!!

After requesting work the Event Log either says that there is no work available or just no work gotten.

Hope Tom will get to his office early.

Something is wrong.

Same situation here, my stats say 622 tasks in progress, although none of my machines has received a single WU in the last 16hrs. The WU request either gets 0 tasks or a message saying no work is available.

@ Tom:

My stats say 600 tasks in progress:
State: All (82650) · In progress (600) · Validation pending (28154) · Validation inconclusive (8569) · Valid (45223) · Invalid (0) · Error (104)
Application: All (82650) · Milkyway@home N-Body Simulation (0) · Milkyway@home Separation (82650)
I wish I could find out where they are.
None of my rigs show any tasks.
...

It looks like those 600 tasks in progress, but nowhere to be seen in BOINC Manager, are tasks solely with a minimum quorum of one.

Hmm. That's really strange. I hope that things didn't get "desynced" with the DB when the drive failed. I'm not sure exactly what that would mean in terms of tech, but if the server thinks that there are 1.6M WUs that are ready to be sent out, but they are actually stuck somewhere, then it probably wouldn't make more WUs that could actually get sent out.

Maybe I can clear out the WUs that are waiting in the queue somehow. I suppose this could also happen with the WUs in the validation queue, which could explain the huge amount of WUs waiting for validation that apparently aren't getting sent out either.

I'll have to dig around. If I end up purging everything I'll have to figure out a way to give out the proper credits to everyone who has WUs that have been crunched and are sitting in limbo.

Today is busy for me, I have to train students on our observatory telescope, have several meetings, and am about to teach class. But I'll try to look into things when I get a chance.