Now back to how things were with the previous Scheduler version- extended Scheduler response times, with occasional errors instead of a valid response.


It would be rather disappointing if they've gone to all the effort to revert the Scheduler, and it doesn't fix the problem (as the bug that stops Anonymous platforms from getting work could have been in this Scheduler version as well, it's only the recent issue resulting in extended Scheduler responses that has made it more apparent).

Any Stock hosts getting work? Is Resend lost tasks still on?

the bug seems fixed since I have received new work on an Anonymous Platform host.

https://setiathome.berkeley.edu/results.php?hostid=8796013

check the timestamps of the most recent tasks.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

the bug seems fixed since I have received new work on an Anonymous Platform host.

Well that's good.
Now they just need to fix the underlying issue- WTF is causing the slow Scheduler responses resulting in "Project has no tasks available" messages, or a Scheduler error?
25/12/2019 13:11:35 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
25/12/2019 13:13:18 | SETI@home | Scheduler request failed: HTTP service unavailable
25/12/2019 13:14:24 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
25/12/2019 13:15:18 | SETI@home | Project has no tasks available
25/12/2019 13:24:25 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
25/12/2019 13:24:47 | SETI@home | Scheduler request failed: Couldn't connect to server
25/12/2019 13:26:03 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
25/12/2019 13:27:39 | SETI@home | Scheduler request failed: HTTP service unavailable
25/12/2019 13:30:35 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
25/12/2019 13:31:30 | SETI@home | Project has no tasks available


Every so often there is 2-3 second response of "Project has no tasks available." These are probably valid responses, the Feeder being out of work at the time. As for the others, the Feeder probably has work, but by the time the Scheduler gets around to respond the work has gone & then it's a "Project has no tasks available" message, or the Scheduler just errors out before even getting that far.


I think most of us will be waiting till after Christmas before we see much if any work.
Time for Eric & Co to take a break & come at it fresh after a rest.

---

Grant
Darwin NT

Any Stock hosts getting work? Is Resend lost tasks still on?

I have tried to get work for both anonymous and stock for an hour or two now without success. Reporting completed jobs works as long as I don't try to report more than 50 at a time. 50 Takes about a minute and trying more results in a timeout. Requesting work without reporting gives 'Project has no tasks available' repeatedly and consistently and this response comes in a couple of seconds.

Server status page says the 'Ready to send' buffer is so full that the splitters are being throttled to almost zero. So it looks like very few people are getting anything.

Resend was never on at least for me. My hosts have accumulated hundreds of ghosts during this disaster and those ghosts have stayed as ghosts. I even tried the manual ghost recovery ritual without success! I guess some people have observed resends because the manual 'ritual' is using an interrupted scheduler request, so these timeouts may trigger it spontaneously. So the slow server response is causing the resends, not the other way around.

---

I guess some people have observed resends because the manual 'ritual' is using an interrupted scheduler request, so these timeouts may trigger it spontaneously. So the slow server response is causing the resends, not the other way around.

Ah, interesting observation. A very plausible possibility.
Although if it were on that would be better, as turning it off would then fix the Scheduler delays. If it's not on, then something else is at fault.

---

Grant
Darwin NT

Reinstalled Lunatics, and now getting tasks.

Somehow I managed to pickup 4 on one of my systems. Should keep it amused for a little while.
Still, at least it means work is possible (as is wining the lottery, just not very likely).

---

Grant
Darwin NT

No joy! Back to "Project has no tasks available"

Yep, but the response times are back to 3-4 sec & no Scheduler errors. Though it would be nice if we could get quick response times and work.

---

Grant
Darwin NT

30 SoGs on the Win box, nothing on either Linux box.

---

30 SoGs on the Win box, nothing on either Linux box.

Dribs & drabs on both. Getting some work, maybe every 40-60min or so?

---

Grant
Darwin NT

+1 - it feels good - thanks to the seti-staff

+1 - it feels good - thanks to the seti-staff

+1

---

Both stock Windows machines getting work slowly, downloads stalling.

Will wait a day or two before starting up the Linux machine

I don't know where you're getting the idea that returning to stock was a waste of time. I did it reasonably soon after the problem was identified and after a few attempts to get tasks and get back to crunching, all has gone as one would expect. There was a drop off in performance as the system had to go through the questionable decision which are the best apps. Once that was decided as being the "SETI@home v8 8.22 windows_intelx86 (opencl_nvidia_SoG)" for my GPU, I admit I aborted the remaining CUDA tasks and it has run the SoG app without breaks ever since. My cache is full and performance only down by ~15% as judged by RAC. And some of that might be because the computer has only grabbed one AP task in this period. This for Windows, obviously special sauce Linux performance is a different matter.

. . When I returned the Windows rig to stock I received work AOK, but when I set two Linux boxes to "stock" that stopped and I was not getting any work on any machine, all just got 'no tasks available'.

. . But strangely (perhaps purely coincidence) when I later turned off the 2 Linux machines the Windows box started getting work again. Go figure. And, now, after days of having my rigs shut down and an outage that was supposed to restore everything, I am again getting "no tasks" on the one rig still running, the Windows box.

. . I am starting to wonder if it's time to find something else to do ... :(

Stephen

:(

Starting to get dribs and drabs of work. But all downloads are stalling out and backing off 5 hours.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

the bug seems fixed since I have received new work on an Anonymous Platform host.
https://setiathome.berkeley.edu/results.php?hostid=8796013
ok the timestamps of the most recent tasks.

. . The difference a few hours makes, I just checked that link and see a machine with 0 (zero) tasks in progress, so I am saying "NOT FIXED"

Stephen

:(

Starting to get dribs and drabs of work. But all downloads are stalling out and backing off 5 hours.

Yep, instant timeouts on Linux system downloads now. Windows system (hosts file used) they don't time out instantly, just count away with no download activity, then timeout after a few seconds or a minute or so.
It's probably a good thing we can't download any work, as the splitters aren't actually producing any to replace what's already gone from the Ready-to-send buffer.

Things are still very, very broken.

---

Grant
Darwin NT

Starting to get dribs and drabs of work. But all downloads are stalling out and backing off 5 hours.

Keith...why are you up?? hahaha

---

After many hours and dozens of "no tasks available", I did the trick for resending lost tasks (even though there weren't any), and the scheduler requests started giving me small handfuls of them. Most of which are--as others have also reported--having transfer issues.

But at least the scheduler is giving work out again.

Thank you, staff.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

But at least the scheduler is giving work out again.

I wish that were so.
For those brief periods where downloads are considered to be downloading, the Scheduler response to a work request is "Project has no tasks available."

---

Grant
Darwin NT

Downloads have started again, but "Project has no tasks available" seems the be the current response for work as the Ready-to-send is 0 & splitters aren't.

---

Grant
Darwin NT

Much the same here, except it slowly appears to be easing off and getting back to normal - both work fetch and downloads seem to be getting easier.