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.

Had a hard time reporting tasks until I set max_tasks_reported to 64, before that change the connection would just time out. Now I get good connections but the dreaded Project has no tasks available.

Yes, after Jimbocous reported he was able to report tasks, I figured the old problem of asking for work at the same time as reporting had reared its head. Setting to 64 or even less never works for me. I just set NNT on all the hosts so they can report work. Nobody is getting any work anyway so NNT is a moot point. Finally starting to unload all the work on the hosts.

---

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

A proud member of the OFA (Old Farts Association)

I'm only seeing this on one computer (out of 4). Perhaps this one computer just 'got ahead' and some issue is causing no new work to be available?

I've checked every setting possible (and compared those settings to the other computers).

Thanks,

-ldl-

---

Hmm, not sure what changed but after some number of hours (or more), it just got new work and is chewing away. So--ignore me I reckon :)

---

Yes, after Jimbocous reported he was able to report tasks, I figured the old problem of asking for work at the same time as reporting had reared its head. Setting to 64 or even less never works for me. I just set NNT on all the hosts so they can report work. Nobody is getting any work anyway so NNT is a moot point. Finally starting to unload all the work on the hosts.

FWIW, my hosts were set to 100,200 and 300 max to report, respectively. Just the luck of the draw on that one, I think ...
Good point on the NNT, will have to try that permutation one of these times. Thanks ...

---

I normally run with a max_report value of 100. Wasn't doing anything other than generating scheduler contact errors and multi-hour backoffs. I have tried as low as 40 before and it never works for me. But soon as I set NNT, the very first contact sent my 100 tasks right off and then I was finally back on the standard 305 second scheduler timer. I have reported everything except for the dedicated Seti Xeon server that I had powered off earlier in the day since it was just burning idle power doing nothing. My other hosts have concurrent alternate projects so at least they kept the gpus busy.

Still not getting any work on request.

---

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

A proud member of the OFA (Old Farts Association)

Still not getting any work on request.

Finally started getting some about an hour ago.

---

I got some, but still no working downloads for me.

---

Still not getting any work on request.

Finally started getting some about an hour ago.

. . Well I am getting work now nd it comes through on the first 2 machines back in service but on this beastie nothing will download, it says cannot connect with server.

:(

Stephen

:(

and the million odd tasks are now all gone. stuck waiting for new ones.

still had over 200 GPU tasks to process but was out of CPU tasks for about 5 hours. these newer multi core CPU's chew through a heap of WU compared to even a mid range GPU

---

Well, a whole bunch of downloads waiting to download when I got home. Lots of clicking later they eventually downloaded, but the Scheduler isn't issuing any new work & the splitters aren't producing any anyway. And then there's still the issue of downloading them if you're lucky enough to score any...
I'm wondering if whatever broke before the outage didn't get sorted, or is just having an excessive impact on the after outage recovery?

---

Grant
Darwin NT

Tuesday (in the US) is when they have a weekly outage for database maintenance.
Most days it only last a few hours (although sometimes it can take 8 or more), and today there were some issues going in to the outage, and the recovery from the outage is showing signs of problems as well.

So getting work could be spotty for the next day or so.

---

Grant
Darwin NT

Found other things to do

Discovered that Einstein on my GTX l1060 class miner runs 32c to 37c temps. Far lower than SETI.

MY other mining system, mix of 1660ti, p102-100, 1070 has somehow snagged 4 gpugrid tasks. Temps are significantly higher though both are in the same location in the garage and a box fan is blowing. 58c to 73c

All on risers and seem to be chugging along fairly well. Looks like the gpugrid will finish in about 5 hours, about what they do on my desktop in a fujl slot with the same class of cards

MY other mining system, mix of 1660ti, p102-100, 1070 has somehow snagged 4 gpugrid tasks. Temps are significantly higher though both are in the same location in the garage and a box fan is blowing. 58c to 73c

GPUGrid does love to cook those GPUs. Made me rethink my cooling the first time I got some work there ... I'd kill for temps that low, however. My SETI crunchers keep their 980s at 75-80c, external on risers. Ugh ...

---

Maybe if the Assimilators & Deleters could clear their backlog, then the Purgers could clear their backlog, and then maybe the splitters could produce some work?

---

Grant
Darwin NT

I don't think 77/sec is too bad, under the circumstances. I'm getting work, hot from the oven.

... Setting to 64 or even less never works for me. I just set NNT on all the hosts so they can report work ...

Wish I had thought of that, NNT is easier and more efficient for me than editing the config files. Learned something new for next time, for now things went back to mostly normal when I stopped staring at the screen :)