Well I just got 25 tasks on my main rig so maybe things are looking up.

Cheers.

No tasks yet, but finally getting at least some work reported. I've been seeing a shorty storm of old Aricebo stuff here, wonder if that was contributing to this?

---

And we're back!

---

It is not letting me report but I did get a new message saying

server error, feeder not running

---

Results ready to send 0 1,305 1,060,082

WoW!!!

---

Greetings,

I have a BOAT load of tasks to report and I am getting this message:

Tue 17 Dec 2019 04:00:21 PM CST | SETI@home | Scheduler request failed: HTTP internal server error
Tue 17 Dec 2019 04:00:21 PM CST | SETI@home | [sched_op] Deferring communication for 02:58:02
Tue 17 Dec 2019 04:00:21 PM CST | SETI@home | [sched_op] Reason: Scheduler request failed

I then used this command in terminal to clear the DNS cache:

sudo /etc/init.d/dns-clean start

I still get the above message in Event Log. Is the command above the proper one to use? I looked it up on the Internet and found it. Deferring for 3 hours!? I'll never get these tasks reported and will run out of work shortly.

[edit]
I just found this command and used it to no avail:

sudo systemd-resolve --flush-caches

[/edit]

[edit2]
In just over an hour I will be out of GPU WUs to run. I'll be out of CPU WUs tomorrow morning unless something here changes overnight.
[/edit2]

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Results ready to send 0 1,305 1,060,082

WoW!!!

That must be why I keep getting Project has no tasks available?

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Results ready to send 0 1,305 1,060,082

WoW!!!

I would be happy to receive some of them...

---

. . I am getting http: internal server error on all attempts to report work ...........

Stephen

:(

. . I am getting http: internal server error on all attempts to report work ...........

Stephen

:(

Yep, there is a distinct possibility something got "fixed" during the 8hr maintenance, that's the polite way to say something is fubar.

---

None of my PCs can get through either. :(

---

getting ready to shut down the project for a few hours. Maybe this mess will be sorted by then.

---

getting ready to shut down the project for a few hours. Maybe this mess will be sorted by then.

. . It's approaching that point ... 2 machines completely OOW, one is my slowest machine which should have lasted over 24 hours with the new limits except for 127 noise bombs. Almost all are VLAR tasks from 13feb16. :(

Stephen

:(

Yep, there is a distinct possibility something got "fixed" during the 8hr maintenance, that's the polite way to say something is fubar.

I'm betting on a restriction on the bad Navi platform getting work. Any time I try to help out with something like this, chaos and backfiring are the inevitable results. :^p

---

I think they turned on Ghost Recovery
Got a lot off this
12/18/19 01:28:37 | SETI@home | Didn't resend lost task 27no19aa.24812.8656.3.30.135_2 (expired)
I guess that make the server kind of grumpy
//Lazy

All I can get tonight is "No work available to process".
I've been working on seti (only) for about 2 years and
have not seen this message for more than a few minutes-
up until now...

Can anyone enlighten me on this? Thanks. Joe

I'm now able to report completed work, but am getting "Project has no tasks available." Strange as there are over 1,000,000 ready to send. Guess they are still working on something.

---

I still have not had any luck in contacting the servers.

---

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

A proud member of the OFA (Old Farts Association)

All work now completed and reported. No difficulties establishing Scheduler connections, but consistently "Project has no tasks available" even though SSP shows (over)full RTS, database with low load, and backup db caught up.
So, in other words, about how it was 15 hours ago during the pre-outage crash.

---

I managed to report my completed WUs and I am not requesting any new WUs (I'm good for another day) out of the kindness of my heart as I know my slow machine always manages to get WUs before your fast ones (why?). Good luck and may the WUs flow soon.