Floating on a sea of green?

Surely floating on the blue line.

In a green atmosphere...

Maybe we have already found alien life - in the form of a duck that breaths green air!!!

I really like that duck!

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

I'm surprised about the following message of BOINC which come from time to time since ~ 00:42 UTC: 'Scheduler request failed: Timeout was reached' - after ~ 60 secs, IIRC normal this happened ~ 600 secs in past..

I tested this with my 420M laptop, also running v6.12.28:

04/06/2011 00:33:22 | SETI@home | Sending scheduler request: To fetch work.
04/06/2011 00:33:22 | SETI@home | Reporting 7 completed tasks, requesting new tasks for CPU and NVIDIA GPU
04/06/2011 00:33:22 | SETI@home | [sched_op] CPU work request: 142292.84 seconds; 0.00 CPUs
04/06/2011 00:33:22 | SETI@home | [sched_op] NVIDIA GPU work request: 18929.68 seconds; 0.00 GPUs
04/06/2011 00:35:22 | SETI@home | Scheduler request completed: got 48 new tasks
04/06/2011 00:35:22 | SETI@home | [sched_op] estimated total CPU task duration: 157672 seconds
04/06/2011 00:35:22 | SETI@home | [sched_op] estimated total NVIDIA GPU task duration: 21611 seconds

So extactly two minutes, but no timeout. Of the 48 tasks, 39 were shorties.

6 days down & now into the 7th day of full network load.
Usually the Results returned per hour are around 50,000 or so. Since the network storage problem outage it hasn't been below 60,000. For the last day it's been above 70,000 & it almost hit 80,000 at one stage.
The hardware is certainly taking a beating, and no end in sight. The last batch of work i got still contained a lot of shorties.

---

Grant
Darwin NT

6 days down & now into the 7th day of full network load.
Usually the Results returned per hour are around 50,000 or so. Since the network storage problem outage it hasn't been below 60,000. For the last day it's been above 70,000 & it almost hit 80,000 at one stage.
The hardware is certainly taking a beating, and no end in sight. The last batch of work i got still contained a lot of shorties.

I wonder how much damage the project would suffer if the air conditioning went away under these circumstances?

Currently, "project backoff: 05:16:00"

---

The hardware is certainly taking a beating, and no end in sight. The last batch of work i got still contained a lot of shorties.

Oooops.

Grant, you and I forgot that the hardware is only working about 1/10th as hard as it was probably designed-for.

---

I wonder how much damage the project would suffer if the air conditioning went away under these circumstances?

No damage, but everything would shutdown.

Grant, you and I forgot that the hardware is only working about 1/10th as hard as it was probably designed-for.

Actually, due to the lack of the network storage, parts of it will be running pretty much at their limits.

---

Grant
Darwin NT

I really like that duck!

Steve

& for those of you that remember Orville on BBC1:

"I 'aaate that duck" ;)!

Actually, due to the lack of the network storage, parts of it will be running pretty much at their limits.

From my understanding an Overland tech logged into the storage server & got it operational again. (Thanks Overland) To my knowledge all data storage is online. If anythings hampering the server it'll be from tech news 1st June

There are some broken astropulse results clogging one of the validators (which is why it shows up on red on the status page). We'll have to figure out an automated way to detect these results and push them through (it's a real pain to do by hand). In the meantime, this is causing our workunit storage server to be quite full, and might hamper other workunit development sooner than later.

---

From my understanding an Overland tech logged into the storage server & got it operational again. (Thanks Overland) To my knowledge all data storage is online.

The last i saw they had got it up & running again, but were in the process of determining what the actual cause of the fault/s was/were. There hasn't been any outage since then to transfer the data back to it, so it's still residing on Thumper.

---

Grant
Darwin NT

The hardware is only working at about 1/10th of what it would be, because it is limited to 100mbit instead of gigabit.

Second, best I can tell, the overland storage IS functional and working.. but everything is still on thumper.

And the ridiculous amount of shorties probably coincides with the large number of the 100% blanked APs that I've gotten lately. Used to be there were only one or two of those per hundred, but now it seems there's 1-2 per 10, sometimes more than that (two days ago, I ran through eight in a row in my cache.. did some excellent stuff for the DCF..I ended up getting 10 more APs than I usually do). So there were a bunch of tapes recently that were essentially trash, or mostly trash.

I still think that after the software blanking runs through and does its thing, it should be able to just mark 100% blanked WUs and keep them from being sent out in the first place. MBs aren't so bad because they are small, but wasting 16MB on APs like that just doesn't make sense.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I'm surprised about the following message of BOINC which come from time to time since ~ 00:42 UTC: 'Scheduler request failed: Timeout was reached' - after ~ 60 secs, IIRC normal this happened ~ 600 secs in past..

I tested this with my 420M laptop, also running v6.12.28:

04/06/2011 00:33:22 | SETI@home | Sending scheduler request: To fetch work.
04/06/2011 00:33:22 | SETI@home | Reporting 7 completed tasks, requesting new tasks for CPU and NVIDIA GPU
04/06/2011 00:33:22 | SETI@home | [sched_op] CPU work request: 142292.84 seconds; 0.00 CPUs
04/06/2011 00:33:22 | SETI@home | [sched_op] NVIDIA GPU work request: 18929.68 seconds; 0.00 GPUs
04/06/2011 00:35:22 | SETI@home | Scheduler request completed: got 48 new tasks
04/06/2011 00:35:22 | SETI@home | [sched_op] estimated total CPU task duration: 157672 seconds
04/06/2011 00:35:22 | SETI@home | [sched_op] estimated total NVIDIA GPU task duration: 21611 seconds

So extactly two minutes, but no timeout. Of the 48 tasks, 39 were shorties.

This is the log of the time in question:
03-Jun-2011 02:41:05 [SETI@home] Reporting 2 completed tasks, requesting new tasks for CPU and NVIDIA GPU
03-Jun-2011 02:42:02 [SETI@home] Scheduler request failed: Timeout was reached


From ~ the time of your contact:
04-Jun-2011 00:25:50 [SETI@home] Reporting 5 completed tasks, requesting new tasks for CPU and NVIDIA GPU
04-Jun-2011 00:26:45 [SETI@home] Scheduler request failed: Timeout was reached

04-Jun-2011 00:42:00 [SETI@home] Reporting 7 completed tasks, requesting new tasks for CPU and NVIDIA GPU
04-Jun-2011 00:42:58 [SETI@home] Scheduler request completed: got 20 new tasks


And from a few minutes ago:
SETI@home 04.06.2011 20:00:43 Reporting 3 completed tasks, requesting new tasks for CPU and NVIDIA GPU
SETI@home 04.06.2011 20:01:43 Scheduler request failed: Timeout was reached

SETI@home 04.06.2011 20:19:11 Reporting 6 completed tasks, requesting new tasks for CPU and NVIDIA GPU
SETI@home 04.06.2011 20:20:03 Scheduler request completed: got 12 new tasks


All ~ 60 secs between request and answer.
I have only DSL light (384/64 kbit/s).

---

Uh oh, uploads have stopped going through.

---

Grant
Darwin NT

The upload server is just responding real slow right now, it took almost a minute before it showed the test page for me.

---

Uh oh, uploads have stopped going through.

Panic over, must have been a minor glitch.

---

Grant
Darwin NT

Uh oh, uploads have stopped going through.

Panic over, must have been a minor glitch.

Or maybe not. Another bunch have started to pile up. Couple of minutes down & none of them have even started to go through.

---

Grant
Darwin NT

Uploads seem to be going away. Haven't had much success in the last hour or so. Cricket graph shows upload declining as well. Wasn't this related to a full storage situation in the past? With all these shorties coming back, that certainly would make sense.

---

It looks like the UL server/service is completely down now.

Temporarily failed upload of xxxxxxxxxxxxxxxxxxx: HTTP error
Temporarily failed upload of xxxxxxxxxxxxxxxxxxx: connect() failed
and so on..

At least my BOINC can't UL.


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

---

Uploads are working, maybe a little slowly;

05/06/2011 06:05:46 SETI@home Started upload of 2ap11ac.7671.13564.7.10.33_0_0
05/06/2011 06:07:02 SETI@home Finished upload of 2ap11ac.7671.13564.7.10.33_0_0

Times BST i.e. UTC +1

Uploads are working, maybe a little slowly;

Try extremely slowly. Anything from 1-12 attempts before it goes through, and at about 2kB/s if i'm lucky.
Network traffic & Scarecrow's Graphs show a significant drop off in the amount of work being returned. Something's broken, or seriously clogged.


EDIT- and even the forums are behaving sluggishly now & then.

---

Grant
Darwin NT