For some time now, each of my PCs has been getting exactly the number of new jobs as it reported completed. So, not filling the caches, but at least holding stable...for now.

They have filled their caches. The cache limit is just lower now.

It's 2:30 am here but I can't go to bed before my computers can get work at the rate they can crunch it. Can't sleep if the fans start and stop randomly :(

I'll just go do some crunching on other stuff :-) Can't really complain, in almost 21 years this has been the first really extended outage i've had.

Kind of disheartening for me, because as a newbie I went out with excitement to recommend the SETI stuff to my group of friends to get them involved, only to have it go down. Most of them sent me emails saying things like, "sorry, not worth my time if it cannot stay up" or, "It's broken, not gonna waste my time." I'll give it another day, but after that, I'll move on.

I haven't been able to report my completed work from yesterday, even with NNT set and report limit reduced to 20. either hits a timeout or HTTP internal error

I just restarted using SETI again after many years, and the program is new to me. I downloaded it on my laptops, and tasks started running, but the tasks finished, and the program now says no work available to process.
I thought this would automatically upload the old work that had finished, and receive new work.
Do I need to do something, I am not sure what to do now?

the communication from the guys running the show to us is pretty lacking to say the least.

Probably my biggest frustration with this project. Business as usual, I'm afraid.

Yep, every host in scheduler backoff due to "internal server error". Can't report work and caches falling.

I would recommend always using the sched_op_debug logging flag for the Event Log. That way at each scheduler connection you will get a printout of how many seconds of cpu work and gpu work you are requesting. If you don't ask for any seconds of cpu work, then you need to figure out why. Probably a configuration problem where you turned off the cpu for the host or the location venue.

Wed 25 Dec 2019 07:24:59 PM EST | SETI@home | [sched_op] Starting scheduler request
Wed 25 Dec 2019 07:24:59 PM EST | SETI@home | Sending scheduler request: To fetch work.
Wed 25 Dec 2019 07:24:59 PM EST | SETI@home | Reporting 15 completed tasks
Wed 25 Dec 2019 07:24:59 PM EST | SETI@home | Requesting new tasks for NVIDIA GPU
Wed 25 Dec 2019 07:24:59 PM EST | SETI@home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
Wed 25 Dec 2019 07:24:59 PM EST | SETI@home | [sched_op] NVIDIA GPU work request: 4629217.31 seconds; 0.00 devices
Wed 25 Dec 2019 07:25:02 PM EST | SETI@home | Scheduler request completed: got 15 new tasks
Wed 25 Dec 2019 07:25:02 PM EST | SETI@home | [sched_op] Server version 709
Wed 25 Dec 2019 07:25:02 PM EST | SETI@home | Project requested delay of 303 seconds
Wed 25 Dec 2019 07:25:03 PM EST | SETI@home | [sched_op] estimated total CPU task duration: 0 seconds
Wed 25 Dec 2019 07:25:03 PM EST | SETI@home | [sched_op] estimated total NVIDIA GPU task duration: 1482 seconds

I have two of my rigs back on the special sauce app, a cuda90 version. One of them has both GPU and CPU tasks (T5810-Ubuntu) and the other only has GPU after quite a while (T3500-Ubuntu). All I did was restore the backed up setiathome.berkely.com folder. Before the server software issues, both were getting both GPU and CPU tasks. Any idea what I should check? Is is just not long enough for the server to make some CPU tasks?

Thanks and happy holidays!

Roger

I always find on my hosts that the gpu caches are always refilled first. Something to do with the APR of the apps and what the scheduler thinks is fastest. So wait until your gpu cache is fully filled before panicking on if your cpu cache is still not getting filled.