Yes, typical lately of the recent long outages. They let the splitters run rampant with no throttling and don't allow any downloads till the RTS buffer gets filled to over a million ready to send. Then they allow downloads. You should have been able to report all finished work by now by setting NNT and can now unset NNT and just wait for the floodgates to open on tasks going out to all the hungry hosts.

---

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

A proud member of the OFA (Old Farts Association)

NNT doesn't seem to make much difference. For the first couple of hours after the outage when when all my scheduler requests failed, they failed with and without NNT and when they started working, they also worked with and without NNT. I had one computer running with NNT and another without.

Some hosts somewhere seemed to be able to get new work already when I was receiving just timeouts and http errors. There was 852 Astropulse tasks in the RTS queue shortly after the server status page started updating after the outage. Those 852 tasks melted away fast - over half of them were gone by the next SSP update 20 minutes later. But I haven't received any new tasks for any of my computers yet.

---

It does in my case. Everyone's farm and internet connection is different. Yes, the scheduler connection always times out right after the outage finishes and then starts eventually connecting. But in my case if I don't set NNT it does not connect after connections are starting to go through. Set NNT and the connection can finally report finished work.

---

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

A proud member of the OFA (Old Farts Association)

So, has anyone actually been able to get some work?
Not a one here, even after after all completed work returned.

In progress has fallen by 1.5 million, and is still falling. Looks like work is being reported, but nothing is going out.

---

Grant
Darwin NT

Since the recovery I got one task on one of my computers, and three on the other. So not zero, but it's really only a trickle.

---

Gazing at the skies, hoping for contact... Unlikely, but it would be such a fantastic opportunity to learn.

My alternative profile

Replica is 30 minutes behind, so hard to see what is going on.
There were a bunch of APs that went out, I can see that there is an increased return rate for APs, but out in the field (for AP) should be higher, so it is still wonky.
I have a slow machine, so I just did a test ask for some work and it said it had no tasks available. Usually my machine will get tasks before all you fast machines. It is still in recovery mode, hard to tell if it just needs more time, or a swift kick. I'm guessing it will resolve in time when the total results falls below the magic 20 million number. Honestly that is just a wild guess on my part though.

edit: RTS is falling. the dam is broken. I think work is going out

So, has anyone actually been able to get some work?

Across 4 clients, I've gotten 10 total tasks so far :)
But at least with the boinccmd update kluge launched every 15 minutes, I do ask for work rather than sitting there stupid ... once the tasks start flowing, it will be interesting to see if putting stuck transfer retries under the control of boinctasks as previously mentioned benefits that issue.

---

Linux system has managed to score some work on 2 requests. Still nothing on the Windows system.
Looks like it's going to be a very rough recovery.

---

Grant
Darwin NT

The last couple of outages I have not received anything but 1 or 2 tasks after the project comes back and before I go to bed. I awake in the morning with full caches.

Expect the same to occur tonight.

---

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

A proud member of the OFA (Old Farts Association)

Same... I’m hoping by morning I’ll be back up and running.

---

All of this has happened before and will happen again -Battlestar Galactica

Hmm, seem to be getting work every 20 or so requests- Windows system has only picked up a few WUs in total, Linux system out of GPU work again & soon to be out of CPU work again.

---

Grant
Darwin NT

As seems to always be the case, the low producer systems now have work, the workhorses are yet to get anything.

---

Finally, got some work.

I've never seen this before, a split in reporting.
My computer crunched all the 150 tasks during the outage, and as far as the "Events Log" records didn't make contact until 02:41, to report said 150.
But https://setiathome.berkeley.edu/results.php?userid=8083616&offset=120&show_names=0&state=0&appid= says 20 of the tasks were reported at 00:26.

How does that happen.

edit] Those AP's that went out were _2's, I got three.

Finally, got some work.

I've never seen this before, a split in reporting.
My computer crunched all the 150 tasks during the outage, and as far as the "Events Log" records didn't make contact until 02:41, to report said 150.
But https://setiathome.berkeley.edu/results.php?userid=8083616&offset=120&show_names=0&state=0&appid= says 20 of the tasks were reported at 00:26.

How does that happen.

edit] Those AP's that went out were _2's, I got three.

The Events log will be local time, and the results on the server will be in UTC. does that explain it?? or is there some other issue??

Finally, got some work.

I've never seen this before, a split in reporting.
My computer crunched all the 150 tasks during the outage, and as far as the "Events Log" records didn't make contact until 02:41, to report said 150.
But https://setiathome.berkeley.edu/results.php?userid=8083616&offset=120&show_names=0&state=0&appid= says 20 of the tasks were reported at 00:26.

How does that happen.

edit] Those AP's that went out were _2's, I got three.

The Events log will be local time, and the results on the server will be in UTC. does that explain it?? or is there some other issue??

No because I am in the UK and my local winter time is UTC. This is the 02:41 Event log entry. Note it is still saying it is reporting 150 tasks.

19/02/2020 02:41:41 | SETI@home | Sending scheduler request: To report completed tasks.
19/02/2020 02:41:41 | SETI@home | Reporting 150 completed tasks
19/02/2020 02:41:41 | SETI@home | Not requesting tasks: don't need (CPU: ; NVIDIA GPU: job cache full)
19/02/2020 02:41:54 | SETI@home | Scheduler request completed

Both systems are now starting to pick up work.
Usual response is "Project has no tasks available", but every so often it gets work, and more than just a few WUs. Hopefully enough to get through the remainder of the recovery period.


Unfortunately the forums have now slowed to a crawl. Any slower, and they'd be non-functional.

---

Grant
Darwin NT

Downloads stuck, 120 on one machine, 180 on the other. Uploads working OK.
Can't shake them loose. Any suggestions?
WTF?

---

Downloads stuck, 120 on one machine, 180 on the other. Uploads working OK.
Can't shake them loose.

Yep. Sticky downloads seem to be a part of the after outage recovery these days.
Even suspending & enabling network access won't get them to start.
Elapsed time ticks away while nothing actually happens...

Edit- that's on the Windows system with the download server set in the Hosts file. On the Linux system with no Hosts file setting, it's an instant timeout. After a few retries you'll get a download or 2 that becomes sticky while all the others timeout instantly.


At least the forums are back to normal.

---

Grant
Darwin NT

My complaining seems to have shaken both machines loose - they are now d/l the backlogs. BUT at <10% of normal speed. Aaaaarrrrggghhhhh!

---

My complaining seems to have shaken both machines loose - they are now d/l the backlogs. BUT at <10% of normal speed. Aaaaarrrrggghhhhh!

Likewsie.
But at much slower speeds than you.

Posting about a problem is generally the best way to fix it.


Edit- shouldn't be too long now and the Ready-to-send buffer will be empty. Splitters still haven't shown much in the way of output.

---

Grant
Darwin NT