Just a reminder, when you panic while the outage is on tomorrow you are welcome at https://boinc.berkeley.edu/dev/forum_thread.php?id=8105.

Just a reminder, when you panic while the outage is on tomorrow you are welcome at https://boinc.berkeley.edu/dev/forum_thread.php?id=8105.

I've got washing down 2 more rooms booked for tomorrow, but you never know.

Cheers.

Yep

---

Splitter output varies from, good, to great, to mostly insufficient. Luckily the brief periods of health are long enough to offset the longer periods where they're barley putting out work.
The MB Validation/Assimilation backlog has almost cleared, unfortunately the MB & AP deletion backlogs are reaching record levels.
And the Replica is at it's 3rd biggest lag for the year, and heading for the second biggest.

And I got home from work to find my main system almost out of work. The Scheduler really is having greater than usual issues. The triple update got me some work, but no where near a full cache, with the weekly outage only hours away.

---

Grant
Darwin NT

Splitter output varies from, good, to great, to mostly insufficient. Luckily the brief periods of health are long enough to offset the longer periods where they're barley putting out work.
The MB Validation/Assimilation backlog has almost cleared, unfortunately the MB & AP deletion backlogs are reaching record levels.
And the Replica is at it's 3rd biggest lag for the year, and heading for the second biggest.

And I got home from work to find my main system almost out of work. The Scheduler really is having greater than usual issues. The triple update got me some work, but no where near a full cache, with the weekly outage only hours away.

. . Yep, of all times to be getting "no tasks available" messages :(

Stephen

:(

Feels a bit like message 1900400:

For some reason the query that fills the "ready to send" queue is running about 10 times slower than it normally does.

Maybe we'll find out after the outrage. Last time, it was too little memory allocated. We might be able to afford some extra memory now :-)

splitter output is not working
Current result creation rate ** 0/sec 0.0236/sec 0.0563/sec

---

13-Dec-2017 15:32:23 [SETI@home] Sending scheduler request: To fetch work.
13-Dec-2017 15:32:23 [SETI@home] Requesting new tasks for CPU and AMD/ATI GPU
13-Dec-2017 15:32:45 [SETI@home] Scheduler request failed: Couldn't connect to server
13-Dec-2017 15:32:48 [---] Project communication failed: attempting access to reference site
13-Dec-2017 15:32:49 [---] Internet access OK - project servers may be temporarily down.

some lags to acces forum too ;)

---

13-Dec-2017 15:32:23 [SETI@home] Sending scheduler request: To fetch work.
13-Dec-2017 15:32:23 [SETI@home] Requesting new tasks for CPU and AMD/ATI GPU
13-Dec-2017 15:32:45 [SETI@home] Scheduler request failed: Couldn't connect to server
13-Dec-2017 15:32:48 [---] Project communication failed: attempting access to reference site
13-Dec-2017 15:32:49 [---] Internet access OK - project servers may be temporarily down.

some lags to acces forum too ;)

It always takes a few hours until the servers catch up with demand.

---

With each crime and every kindness we birth our future.

It always takes a few hours until the servers catch up with demand.

Check out the Database/file status, As of. Servers might be up, or at least showing up, but the project is still down/stuck/messed up.

---

It always takes a few hours until the servers catch up with demand.

For that to happen they will have to start splitting new data.

---

If you have big backlogs, try reporting fewer tasks at a time.

13/12/2017 15:05:07 | SETI@home | Reporting 150 completed tasks
13/12/2017 15:06:24 | SETI@home | Scheduler request failed: HTTP internal server error

13/12/2017 15:11:38 | SETI@home | Reporting 64 completed tasks
13/12/2017 15:12:17 | SETI@home | Scheduler request completed

and on another machine,

13/12/2017 15:27:28 | SETI@home | Reporting 191 completed tasks
13/12/2017 15:28:24 | SETI@home | Scheduler request failed: HTTP internal server error

May be a particular problem if you run Raistmer's apps with the huge stderr_txt entries. That file was 2.4 MB.

13/12/2017 15:32:01 | SETI@home | Reporting 64 completed tasks

was only 845 KB, and got through.

JACKPOT!
ASUS i7 960 SETI@home 13/12/2017 9:26:43 AM Scheduler request completed: got 17 new tasks

Of course my slow computer first, LOL

server is back few minutes after ;)

13-Dec-2017 15:35:26 [SETI@home] Sending scheduler request: To fetch work.
13-Dec-2017 15:35:26 [SETI@home] Requesting new tasks for CPU and AMD/ATI GPU
13-Dec-2017 15:36:06 [SETI@home] Scheduler request completed: got 0 new tasks
13-Dec-2017 15:36:06 [SETI@home] Project has no tasks available

0 AP to grab .. normal ;)

---

JACKPOT!
ASUS i7 960 SETI@home 13/12/2017 9:26:43 AM Scheduler request completed: got 17 new tasks

Of course my slow computer first, LOL

NO, NADA, nothing down here. LOL

---

I attempted to suspend a few ready to report tasks (hoping a to trickle a few in), and my entire backlog disappeared. :(

---

ASUS i7-3820 SETI@home 13/12/2017 9:49:42 AM Scheduler request completed: got 16 new tasks

A handful more in, over 2600 reported back, at least that cleared out.

Please Sir, can I have some (never mind more!)?

---

Having to use http_debug to even get a good connection. Mostly been getting project isn't available. Very slow in getting work reported. No tasks are available.

---

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

A proud member of the OFA (Old Farts Association)