The SSP shows the SETI@home science database Running again. That's the first step. Maybe it won't be much longer.
https://setiathome.berkeley.edu/show_server_status.php

Now it's showing it as Disabled again...oh well.

And it's also after 3:30 pm Berkley time, on a Friday afternoon. Wonder if there's going to be some OT this weekend, or if it'll have to wait till sometime Monday (hopefully at the latest) for a resolution?

---

Back up projects sir.... Back up projects...

---

Back up projects sir.... Back up projects...

For the kitties, there are no backup projects.
Fur there is no reason to have them except for pity,.]
IN my small estimation, there is no other reason to spend the electricty that I do,.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Back up projects sir.... Back up projects...

Or a chance to reduce the power bill slightly.

To each their own.

---

Grant
Darwin NT

Back up projects sir.... Back up projects...

Einstein it is ...

---

My clients have hundreds of completed units to report, and are almost out of work units to process.
"Project is temporarily shut down for maintenance"

Any idea when this issue might be corrected?

---

My clients have hundreds of completed units to report, and are almost out of work units to process.
"Project is temporarily shut down for maintenance"

Any idea when this issue might be corrected?

Nope.
Major database issues.

I wouldn't expect it back up till sometime next week; Monday afternoon would be the most likely earliest possible time. Later in the week is more likely.
Any earlier would be a bonus.

---

Grant
Darwin NT

My clients have hundreds of completed units to report, and are almost out of work units to process.
"Project is temporarily shut down for maintenance"

Any idea when this issue might be corrected?

There's a bulletin and link to ongoing message area on the home page ...

---

The SSP shows the SETI@home science database Running again. That's the first step. Maybe it won't be much longer.
https://setiathome.berkeley.edu/show_server_status.php

Now it's showing it as Disabled again...oh well.

And it's also after 3:30 pm Berkley time, on a Friday afternoon. Wonder if there's going to be some OT this weekend, or if it'll have to wait till sometime Monday (hopefully at the latest) for a resolution?

. . In the meantime E@H is getting a big bonus of lots of tasks getting crunched above their normal returns :)

Stephen

:)

My clients have hundreds of completed units to report, and are almost out of work units to process.
"Project is temporarily shut down for maintenance"

Any idea when this issue might be corrected?

. . Only almost out of work? Lucky you.

. . My rigs have been out of work for more than a day, even the slowest of them ran out last night at 8:30pm Friday AEDT.

. . Just smile and go along for the ride.

Stephen

<shrug>

My clients have hundreds of completed units to report, and are almost out of work units to process.
"Project is temporarily shut down for maintenance"

Any idea when this issue might be corrected?

Nope.
Major database issues.

I wouldn't expect it back up till sometime next week; Monday afternoon would be the most likely earliest possible time. Later in the week is more likely.
Any earlier would be a bonus.

. . Way to keep expectations low there Grant LOL

. . I prefer to remain optimistic until circumstances prove otherwise.

Stephen

:)

Fur there is no reason to have them except for pity,.]

Mark I call BS, Seti owes Einstein a whole lota love. Have you forgotten Nebula?

---

It looks like we are back in business!

3/31/2017 11:39:48 PM	SETI@home	Reporting 100 completed tasks
3/31/2017 11:39:48 PM	SETI@home	Requesting new tasks for ATI GPU
3/31/2017 11:39:53 PM	SETI@home	Scheduler request completed: got 1 new tasks

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

It looks like we are back in business!

3/31/2017 11:39:48 PM	SETI@home	Reporting 100 completed tasks
3/31/2017 11:39:48 PM	SETI@home	Requesting new tasks for ATI GPU
3/31/2017 11:39:53 PM	SETI@home	Scheduler request completed: got 1 new tasks

Now it's the mad scramble for work.
1/04/2017 13:10:07 | SETI@home | Sending scheduler request: Requested by user.
1/04/2017 13:10:07 | SETI@home | Reporting 50 completed tasks
1/04/2017 13:10:07 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
1/04/2017 13:10:51 | SETI@home | Scheduler request failed: HTTP internal server error
1/04/2017 13:11:08 | SETI@home | update requested by user
1/04/2017 13:11:11 | SETI@home | Sending scheduler request: Requested by user.
1/04/2017 13:11:11 | SETI@home | Reporting 50 completed tasks
1/04/2017 13:11:11 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
1/04/2017 13:12:53 | SETI@home | Scheduler request completed: got 0 new tasks
1/04/2017 13:12:53 | SETI@home | Project has no tasks available
1/04/2017 13:17:59 | SETI@home | Sending scheduler request: To report completed tasks.
1/04/2017 13:18:00 | SETI@home | Reporting 50 completed tasks
1/04/2017 13:18:00 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
1/04/2017 13:18:36 | SETI@home | Scheduler request completed: got 0 new tasks
1/04/2017 13:18:36 | SETI@home | Project has no tasks available
1/04/2017 13:23:41 | SETI@home | Sending scheduler request: To fetch work.
1/04/2017 13:23:41 | SETI@home | Reporting 1 completed tasks
1/04/2017 13:23:41 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
1/04/2017 13:24:22 | SETI@home | Scheduler request completed: got 0 new tasks
1/04/2017 13:24:22 | SETI@home | Project has no tasks available


1/04/2017 13:24:22 | SETI@home | Scheduler request completed: got 0 new tasks
1/04/2017 13:24:22 | SETI@home | Project has no tasks available
1/04/2017 13:29:36 | SETI@home | update requested by user
1/04/2017 13:29:37 | SETI@home | Sending scheduler request: Requested by user.
1/04/2017 13:29:37 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
1/04/2017 13:29:59 | | Project communication failed: attempting access to reference site
1/04/2017 13:29:59 | SETI@home | Scheduler request failed: Couldn't connect to server
1/04/2017 13:30:01 | | Internet access OK - project servers may be temporarily down.
1/04/2017 13:31:19 | SETI@home | Sending scheduler request: To fetch work.
1/04/2017 13:31:19 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
1/04/2017 13:31:41 | | Project communication failed: attempting access to reference site
1/04/2017 13:31:41 | SETI@home | Scheduler request failed: Couldn't connect to server
1/04/2017 13:31:42 | | Internet access OK - project servers may be temporarily down.

Hopefully things will settle down soon.

---

Grant
Darwin NT

Aye. Extended outage = extended recovery time.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Aye. Extended outage = extended recovery time.

True.
But usually we don't get Scheduler errors one after the other, after the other, after the other, after the other; after previously being able to get responses from the Scheduler (even if they were ones we didn't want to hear- Project has no tasks available).

---

Grant
Darwin NT

Not sure we're really up.
Can't report at this point:

SETI@home	3/31/2017 10:27:54 PM	update requested by user	
SETI@home	3/31/2017 10:27:58 PM	Sending scheduler request: Requested by user.	
SETI@home	3/31/2017 10:27:58 PM	Reporting 400 completed tasks	
SETI@home	3/31/2017 10:27:58 PM	Not requesting tasks: don't need (CPU: job cache full; NVIDIA GPU: job cache full)	
SETI@home	3/31/2017 10:29:12 PM	Scheduler request failed: HTTP internal server error	

Maybe just traffic, but that doesn't totally make sense either ... same on all 5 boxes.

---

Lol, well best of plans... had been trying to get the last tasks on my Linux/Mac host to report, so I can switch hardware and do things. It seems they have finally reported a few minutes ago. I guess the server hamsters got the delivery of replacement rubber bands OK

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Maybe just traffic, but that doesn't totally make sense either ... same on all 5 boxes.

Not just traffic IMHO.
Been plenty of weekly outages, some of them longer than others, and some rather long unscheduled outages, yet still it's been possible to contact the Scheduler after those outages.

I've been able to contact the Scheduler a couple of times, and the only response is "Project has no tasks available" And when I do contact the Scheduler, it takes up to 2 minutes to get a response- usually it's 3-4 seconds, regardless of how bad other parts of the system might be at the time.
Fact is, at the moment, the usual response to a Scheduler request is an error, and even if you do make contact, there's no work available at present.

Hopefully it'll settle down of it's own accord.

---

Grant
Darwin NT

Maybe just traffic, but that doesn't totally make sense either ... same on all 5 boxes.

Hopefully it'll settle down of it's own accord.

Looks like what's happening is that the Report-in queue is slow, and that after a few tries at least a portion do report. Nothing out as yet, tho, as reported tasks have not cleared the scheduler queue ...
Not often that an outage results in all boxes having 100% of their work to report at once, at least here.

---