After a major power outage last week, it recovered nicely.

---

Upload-wise yes very impressive.

uploads are fine but I can't get my work returned. I have 1100 errored WU's to send back and I can't get them off my machine. BOINC can reach the internet so something must be wrong at moonbase alpha

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

uploads are fine but I can't get my work returned. I have 1100 errored WU's to send back and I can't get them off my machine. BOINC can reach the internet so something must be wrong at moonbase alpha

You might have to do the max_tasks_returned mod to your cc config to send them back in small batches.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Must not be anything to panic about.. except that there's nothing to panic about.

I was just noticing that even though the pipe is maxed out, APs are downloading at 75KB/sec each. I've been getting 1 and 2 at a time. Usually when the pipe is maxed, it is between 20-35KB/sec each.

---

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

Must not be anything to panic about.. except that there's nothing to panic about.

I was just noticing that even though the pipe is maxed out, APs are downloading at 75KB/sec each. I've been getting 1 and 2 at a time. Usually when the pipe is maxed, it is between 20-35KB/sec each.

Well no APs coming out again, so panicking a bit.

Anyway, I'm also getting 1 or 2 APs when I get some. In the past I remember sometimes getting more, 10 or more. Is there now a limit on the number you can get on a request?

uploads are fine but I can't get my work returned. I have 1100 errored WU's to send back and I can't get them off my machine. BOINC can reach the internet so something must be wrong at moonbase alpha

You might have to do the max_tasks_returned mod to your cc config to send them back in small batches.

I've noticed an interesting thing since the comeback from the outage. When I do an Update, BOINC only reports about half the number of waiting tasks.

e.g. If (for example) there are 500 tasks waiting to report. On the first update it reports 250, on the next update 125, the next 75 and the remaining tasks on the last one.

I've noticed this on all 4 machines. All are running the standard 6.10.58 client with no "report max tasks line" in the cc_config file.

Has there been any unpublicised server side changes made recently that limit the max reports in one go ?

T.A.

Has there been any unpublicised server side changes made recently that limit the max reports in one go ?

T.A.

Well, we've talked about it a little.

Some of us had thousands after the outage and they were stuck. They wouldn't report at all and gave an error.

Several of us edited a cc_config file to make it report fewer and that got them unstuck. Eric then did something server-side. He set the max number of tasks to report below where we had all set it in cc_config (I think) and maybe did something else, too.

Maybe that's why you are seeing what you are seeing.

I'd be interested in knowing if once your tasks waiting to report got below 64 if they all went, or if they continued to go by half.

Has there been any unpublicised server side changes made recently that limit the max reports in one go ?

T.A.

Well, we've talked about it a little.

Some of us had thousands after the outage and they were stuck. They wouldn't report at all and gave an error.

Several of us edited a cc_config file to make it report fewer and that got them unstuck. Eric then did something server-side. He set the max number of tasks to report below where we had all set it in cc_config (I think) and maybe did something else, too.

Maybe that's why you are seeing what you are seeing.

I'd be interested in knowing if once your tasks waiting to report got below 64 if they all went, or if they continued to go by half.

Reports 64 per Update now.

---

All Seti Web pages became unavailable for a couple of minutes as well as uploads and downloads, the Website and downloads have recovered, uploads have dropped to Zero,

Claggy

All Seti Web pages became unavailable for a couple of minutes as well as uploads and downloads, the Website and downloads have recovered, uploads have dropped to Zero,

Claggy

And retrying uploads doesn't help - I'm getting timeouts on every connection attempt.

Looks like whichever hardware is being Bruno today has started the Memorial Day holiday early...

Yep, inbound network traffic is non-exisitent, and my uploads continue to accumulate.

---

Grant
Darwin NT

... when the cleaning crew takes a switch or two and wash them in water.
Wait until they decide to wash the servers. ...

Why not? If this helps to cleanup this yellow feather mess ;-)

__W__

---

_______________________________________________________________________________

82 wu's and climbing, still not uploading...

---

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

Uploads are not working.

I think it is because of that last AP unit.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Uploads are not working.

Mmm likewise.

Uploads are not working.

Mmm likewise.

Yep, dead for everyone. Right around 9:30 UTC or 2:30 PDT

---

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

Uploads are not working.

Mmm likewise.

Yep, dead for everyone. Right around 9:30 UTC or 2:30 PDT

Yep something barfed all over the place... ;)

---

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

Uploads are not working.

Mmm likewise.

Yep, dead for everyone. Right around 9:30 UTC or 2:30 PDT

Yep something barfed all over the place... ;)

Yep, Just as Claggy mentioned several hours ago.

---

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