we may indeed go out with a bang!

Where is the kaboom? It's suppose to be a kaboom!

The new WU is flow without restrictions, the size of the DB WU count is >20MM and there are no problems t all.

Did they finally find the fix for the DB size problem? Just now when the curtains are ready to close?

I am not sure I fully agree with you as the replica database is 2116 seconds behind. On a bright note though it is good that work is flowing and I have even had a couple of BLC 35 _3 tasks passed through my system so resends are getting through hopefully we will start to see some bloat disappear soon. This will happen for sure when tasks are not been sent out anymore

---

By SSP All unstarted tapes has been removed. The beginning of the end?

. . I had noticed that the eternally non-starting tapes (2 x Blc22, 2 x Blc34 plus 1 x Blc62) had been removed and thought ... Yay! But I had not noticed that ALL unstarted tapes had gone ...

. . I am guessing you are right, this is the beginning of the shut down ...

Stephen

? ?
(mixed feelings, mostly sad)

I'll accept 16mr20af as automation, but I think 16se11ab must have been manually chosen.

. . +1

Stephen

. .

Clearing out the shelves just like toilet paper during a pandemic! :)

---

we may indeed go out with a bang!

Where is the kaboom? It's suppose to be a kaboom!
The new WU is flow without restrictions, the size of the DB WU count is >20MM and there are no problems t all.
Did they finally find the fix for the DB size problem? Just now when the curtains are ready to close?

. . Of course, that would be according to Murphy's Law. Just like I have been waiting for a couple of years for the faster NBN connection to come and it arrived on Tuesday with just 2 weeks of SETI left ... mummble fritz whagaadang ....

Stephen

<throwing arms up in the air>

I am not sure I fully agree with you as the replica database is 2116 seconds behind. On a bright note though it is good that work is flowing and I have even had a couple of BLC 35 _3 tasks passed through my system so resends are getting through hopefully we will start to see some bloat disappear soon. This will happen for sure when tasks are not been sent out anymore

. . it would happen faster if they would chop all task deadlines to the bone and force resends to machines that would actually complete them in the remaining time.

Stephen

? ?

Yes I agree it certainly would have quicker Steven if deadlines were cut. It will be interesting to see what happens. It will be interesting to see how long the 1573 remaining channels of BLC of work take to process. I have no Intel but I am wondering whether or not they are doing this is a test run to see how long it takes to complete X number of channels then they will add X number to last us through until the end of the month. Simply speculation nothing more nothing less

---

Something just happened...

Uploading is working ATM, but reporting is stuck.

---

Well, the Web site is back, but the forums i would describe as barely functional- over 5 minutes just to get to this point of being able to make a post (fingers crossed it'll go though and not vanish in to the ether).
And the Scheduler is still MIA.

---

Grant
Darwin NT

Well, the Web site is back, but the forums i would describe as barely functional- over 5 minutes just to get to this point of being able to make a post (fingers crossed it'll go though and not vanish in to the ether).
And the Scheduler is still MIA.

+1
it is messed up and not working... in technical terms :-)

it is messed up and not working... in technical terms :-)

Yep. It's borked.
Well and truly borked.

---

Grant
Darwin NT

It looks as if the issues started about 4am (GMT), and have just got worse since then.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

It looks as if the issues started about 4am (GMT), and have just got worse since then.

My last successful scheduler request happened at 05:05:43 UTC and the last one that got new work at 04:58:37 UTC.

There were a couple of very short failures around 04:00, but then the general failure kicked in about 90 minutes later - which ties in with your observations.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

SSP displays negative result creation rate for AstroPulse!

Current result creation rate **	0/sec	-0.0500/sec	0.2214/sec	3m

I noticed that too.

Well, they can't have my AP's back 'til I'm done with them. ;^)

---

Member of the 20 Year Club

Feels like we're going through the typical 'slow recovery from cold boot', that we've become familiar with at this time of day for the last three months.

No response from server (can't connect)
Bad response from server (internal error, http service unavailable)
Slow response from server - report only, small is better
Partial response from server - a few dribs and drabs of new work (I got nine tasks just now, on one machine only)

And so it progresses. Fingers crossed, we might be up and running in another couple of hours.

My last good contact was,

19/03/2020 04:59:26 | SETI@home | Requesting new tasks for NVIDIA GPU
19/03/2020 04:59:29 | SETI@home | Scheduler request completed: got 0 new tasks
19/03/2020 04:59:29 | SETI@home | Project has no tasks available
19/03/2020 05:02:02 | SETI@home | Computation for task 06ap10ab.9042.9478.14.41.80_0 finished
19/03/2020 05:02:02 | SETI@home | Starting task 16mr20ae.21582.2112.3.30.61_0
19/03/2020 05:02:04 | SETI@home | Started upload of 06ap10ab.9042.9478.14.41.80_0_r319936499_0
19/03/2020 05:02:08 | SETI@home | Finished upload of 06ap10ab.9042.9478.14.41.80_0_r319936499_0
19/03/2020 05:04:34 | SETI@home | Sending scheduler request: To fetch work.
19/03/2020 05:04:34 | SETI@home | Reporting 1 completed tasks
19/03/2020 05:04:34 | SETI@home | Requesting new tasks for NVIDIA GPU
19/03/2020 05:04:56 | SETI@home | Scheduler request failed: Couldn't connect to server
19/03/2020 05:04:58 |  | Project communication failed: attempting access to reference site

But I have just got this, partial progress

19/03/2020 09:07:16 | SETI@home | Fetching scheduler list
19/03/2020 09:07:18 | SETI@home | Master file download succeeded
19/03/2020 09:07:23 | SETI@home | Sending scheduler request: To report completed tasks.
19/03/2020 09:07:23 | SETI@home | Reporting 62 completed tasks
19/03/2020 09:07:23 | SETI@home | Requesting new tasks for NVIDIA GPU
19/03/2020 09:07:27 | SETI@home | Scheduler request completed: got 0 new tasks
19/03/2020 09:07:27 | SETI@home | Project has no tasks available

Times are GMT.

It's starting to wake up and smell the coffee.

19/03/2020 09:18:47 | SETI@home | Sending scheduler request: To report completed tasks.
19/03/2020 09:18:47 | SETI@home | Reporting 128 completed tasks
19/03/2020 09:18:47 | SETI@home | Requesting new tasks for NVIDIA GPU
19/03/2020 09:18:47 | SETI@home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
19/03/2020 09:18:47 | SETI@home | [sched_op] NVIDIA GPU work request: 74310.46 seconds; 0.00 devices
19/03/2020 09:18:56 | SETI@home | Scheduler request completed: got 61 new tasks

Scheduler is awake and responding, but so far the response is "Project has no tasks available".
At least the forums are responsive again. No waiting 5 min for the thread to load, then another 5 min for the post to go through...


Edit- and of course posting about it gets results. One of my systems managed to pick up some work. But of course we're now in the "can't actually download anything" stage of the recovery. Everything's gone in to backoff mode.
A few retries later and most of them have managed to eventually download.


Edit- other system has picked up work, but no amount of retrying will get it to download (nor suspending and re-enabling network access).

Edit-
Seriously- the Scheduler & Download servers have to be tied in with the forum software somehow. Almost 15 min of retries, no joy. Post about it, work starts downloading 30 sec later.

---

Grant
Darwin NT