I'm wondering why all those unsplitted astropulse tapes are went missing?
According to the number of AP results ready to send, they surely weren't processed. There were 300+ channels left before this latest meltdown and now it's down to 34.

---

Who the hell is General Failure and why is he reading my harddisk?¿

confirmed, I am currently downloading 34MB's and just in the nick of time:))

Stupid machines, it had gone to split requests and asked for CPU tasks first. And Whoopie it got 40.
Next time it requested fot the GPU and lo and behold, reached a &TYR*UG%PI& limit.

Looks like things are going to be erratic for a while- managed to download some work, but now downloads aren't happening, Scheduler requests time out & uploads aren't going through.

---

Grant
Darwin NT

We're going down again shortly.

Well, you're right again ...

---

- Performance is not a simple linear function of the number of CPUs you throw at the problem. -

I built up a 5 or 6 day cache on Einstein, and set it to NNT. If Seti is functional when it depletes, I will load up with Seti work. I will keep evaluation what Seti is doing, although I am hoping that at some point the higher through put machines will be able to build a cache. I know this may take a couple of weeks or so, and I'm not concerned. The last couple of months has been a bit tough, but science still got done. ET may be in the data we crunched with flaky DCF's, or near empty machines.

Steve

---

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

I built up a 5 or 6 day cache on Einstein, and set it to NNT. If Seti is functional when it depletes, I will load up with Seti work. I will keep evaluation what Seti is doing, although I am hoping that at some point the higher through put machines will be able to build a cache. I know this may take a couple of weeks or so, and I'm not concerned. The last couple of months has been a bit tough, but science still got done. ET may be in the data we crunched with flaky DCF's, or near empty machines.

Steve

My cache on Einstein is either 2 or 3 days, ones for the gpus and one was by accident and is for the cpu, once I'm out of Einstein cpu work I'll be happier.

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

Got some downloaded now cannot upload yet server status states that it is running or is this wrong again?

---

Cricket says we are down again. Hope it isn't for long. I have at least 2 days work on both my G4s and have set NNT, but I hear others are running on fumes, so......

---

Donald
Infernal Optimist / Submariner, retired

My blushes Sten, surely there is a better venue for that ribawdwy!

Try this while you are waiting?

No Time To Lose

i'm running milkyway@home i have done all my Seti units.
and in the milkyway@home the NVIDIA is at the loosing site for best performance cards... ATI is the king ...
let's hope they will fix the problem soon

---

My Guf is Empty for 36 hours now..can I please get some work!!!!

See News

---

Janice

Just uploaded all wu. Just downloaded 50 wu.
All cuda fermis.

May be work coming. Little guy just got gpu work on 3 consecutive fetches, all mb, mix of long /short. No retries, cricket says I'm not the only one, but not maxed out yet.

---

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

May be work coming. Little guy just got gpu work on 3 consecutive fetches, all mb, mix of long /short. No retries, cricket says I'm not the only one, but not maxed out yet.

Yep:

29/09/2011 22:48:04 SETI@home [sched_op_debug] Starting scheduler request
29/09/2011 22:48:04 SETI@home Sending scheduler request: Requested by user.
29/09/2011 22:48:04 SETI@home Reporting 12 completed tasks, requesting new tasks for GPU
29/09/2011 22:48:04 SETI@home [sched_op_debug] CPU work request: 0.00 seconds; 0.00 CPUs
29/09/2011 22:48:04 SETI@home [sched_op_debug] NVIDIA GPU work request: 288072.26 seconds; 0.00 GPUs
29/09/2011 22:48:04 SETI@home [sched_op_debug] ATI GPU work request: 432000.00 seconds; 1.00 GPUs
29/09/2011 22:48:15 SETI@home Scheduler request completed: got 67 new tasks
29/09/2011 22:48:15 SETI@home [sched_op_debug] Server version 613
29/09/2011 22:48:15 SETI@home Message from server: No tasks are available for the applications you have selected
29/09/2011 22:48:15 SETI@home Message from server: No tasks are available for Astropulse v505
29/09/2011 22:48:15 SETI@home Message from server: Your preferences allow tasks from applications other than those selected
29/09/2011 22:48:15 SETI@home Message from server: Sending tasks from other applications
29/09/2011 22:48:15 SETI@home Project requested delay of 303 seconds
29/09/2011 22:48:15 SETI@home [sched_op_debug] estimated total CPU job duration: 0 seconds
29/09/2011 22:48:15 SETI@home [sched_op_debug] estimated total NVIDIA GPU job duration: 43059 seconds
29/09/2011 22:48:15 SETI@home [sched_op_debug] estimated total ATI GPU job duration: 0 seconds

Edit: and all downloaded now.

Claggy

Well I'll be clagged ;), I got only 1, glad Ya got 67 though, sigh.

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

Stupid machines, it had gone to split requests and asked for CPU tasks first. And Whoopie it got 40.
Next time it requested fot the GPU and lo and behold, reached a &TYR*UG%PI& limit.

I don't understand this one. I was well down on the test rig, but after a few fetches and failed fetches, I got up to the expected 450 (400 GPU and 50 CPU) limit without any problems from partial limits for one or other device on the way.

After a rocky recovery from the failed RAID, we seem to be running OK now (and with plenty of non-shorties in the mix, which should help a lot).

...we seem to be running OK now (and with plenty of non-shorties in the mix, which should help a lot).

Well, not for me

30.09.2011 03:18:00 | SETI@home | Requesting new tasks for CPU and ATI GPU
30.09.2011 03:18:43 |  | Project communication failed: attempting access to reference site
30.09.2011 03:18:43 | SETI@home | Scheduler request failed: Failure when receiving data from the peer
30.09.2011 03:18:45 |  | Internet access OK - project servers may be temporarily down.

---

pipes are running amazingly fast. It feels like something major got fixed.

---

Janice

Have you taken a look at the Cricket graph?

I think this is how it's supposed to be if the servers
aren't maxed out.