Server stsus page shows everything green (including the upload server), however the increase in network traffic has been, negligable.
So there might still be some problems with the upload server- i'd have expected uploads to max out as soon as the server came back up.

---

Grant
Darwin NT

I know you are Sutaru. Actually you're probably more patient than me :-)

Good news, since my last post I've had 3 upload so things are improved.

---

NEWS FLASH - I just had one WU upload! Only about a dozen left now...

15/07/2009 1:04:50 PM SETI@home Finished upload of 24fe09ab.20328.11115.5.8.44_3_0

I've had a few upload, but they're not being acknowledged. In other words, the transfer shows 100%, but they're not coming off my transfer list. It's a start.

---

Join the PACK!

Hmmm... so the answer would be either more funding for bigger pipes or perhaps making work units more computational intensive so that there is less traffic (which would also require funding in the shape of research and programming)

---

I have now maybe ~ 1,600 results ready for UL.

Your machine has 1,600 results, and it tries to connect 1600 times every four hours, more or less, depending on the backoff.

How many others out there have lots of uploads, and are retrying just as aggressively?

I hope you mean it not negative.


I have only one 24/7 PC..

Others have more PCs.. with same or more ULs?

I don't do it.. I don't press the 'retry/update' button.. BOINC do it automatically..

I don't mean it in a positive or negative way. It's just a fact of life.

As you say, this is what BOINC does. It tries very hard to push the work to the servers, and until we get a version that is less aggressive, we'll see high loads and lots of trouble.

... and we can fret over it, or we can wait it out.

I don't think there are enough here in the forums to do anything that'd matter.

Waiting is.

---

Or just attach to other projects and let BOINC try and retry to upload your Seti tasks.

Another reason why downloads are stopped when you have that many uploads going is one of deadlines. If no uploads happen, you have a chance that all the work you got done and still get to crunch will eventually pass its deadline. What good is that?

---

13-7-2009 20:06:00 SETI@home Started upload of 05dc08ag.1874.11933.13.8.11_2_0
13-7-2009 20:06:22 Project communication failed: attempting access to reference site
13-7-2009 20:06:22 SETI@home Temporarily failed upload of 05dc08ag.1874.11933.13.8.11_2_0: connect() failed
13-7-2009 20:06:22 SETI@home Backing off 1 min 0 sec on upload of 05dc08ag.1874.11933.13.8.11_2_0
14-7-2009 13:28:48 SETI@home Temporarily failed upload of 10oc08ab.9949.257801.10.8.195_0_0: connect() failed
14-7-2009 13:28:48 SETI@home Backing off 1 hr 4 min 21 sec on upload of 10oc08ab.9949.257801.10.8.195_0_0
14-7-2009 13:28:50 Internet access OK - project servers may be temporarily down.
14-7-2009 13:29:24 SETI@home Started upload of 10oc08ab.9949.11115.10.8.96_0_0
14-7-2009 13:29:27 Project communication failed: attempting access to reference site
15-7-2009 20:04:35 SETI@home Temporarily failed upload of 17oc08ac.23107.6616.6.8.98_1_0: connect() failed
15-7-2009 20:04:35 SETI@home Backing off 1 hr 42 min 55 sec on upload of 17oc08ac.23107.6616.6.8.98_1_0
15-7-2009 20:04:37 Internet access OK - project servers may be temporarily down.
15-7-2009 20:05:22 SETI@home Started upload of 06dc08ac.22025.9888.10.8.71_0_0
15-7-2009 20:05:26 SETI@home Started upload of 21no08ab.23122.9888.6.8.135_0_0
15-7-2009 20:05:44 Project communication failed: attempting access to reference site
15-7-2009 20:05:44 SETI@home Temporarily failed upload of 06dc08ac.22025.9888.10.8.71_0_0: connect() failed

Hi, I noticed, the UPLoad SERVER is ENABLED, although I still can't UPload, what's up?

---

Everyone else is trying to get through too. This creates a situation where only so many connections can be acknowledged before others get dropped. Hopefully the situation will improve as clients uploads tapper off.

---

Could someone explain why the uploads aren't getting through quickly even though the Cricket graphs are showing (generally) less than 50Mbs? Not complaining, just wondering.

Link to graphs:

http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=%2Frouter-interfaces%2Finr-250%2Fgigabitethernet2_3;ranges=d%3Aw;view=octets

---

Some of mine have got through - about 5% of my backlog is now 'ready to report', and I think some of them have reported already. Just give them time, and don't try to rush things.

Thanx for your swift reply, Ozzfan. You are right, as everyone tries to UPload, SERVER gets clogged up again!
And Richard, too, you are quick.

---

Just a theory, based on looking at Cricket graphs for the last week or month.

It looks to me like maybe the Berkley Boys have been playing with different ways of throttling downloads and uploads, in order to keep the 100 meg pipe full of mostly data, instead of clogging it with ACKs and other overhead when we try to cram too much into it all at once.

---

Just a theory, based on looking at Cricket graphs for the last week or month.

It looks to me like maybe the Berkley Boys have been playing with different ways of throttling downloads and uploads, in order to keep the 100 meg pipe full of mostly data, instead of clogging it with ACKs and other overhead when we try to cram too much into it all at once.

Possibly, but i still thing something's borked.
The problem has generally been downloads killing uploads, not the other way around. At the present rate it'll take a couple of days for the uploads to clear.

---

Grant
Darwin NT

Just a theory, based on looking at Cricket graphs for the last week or month.

It looks to me like maybe the Berkley Boys have been playing with different ways of throttling downloads and uploads, in order to keep the 100 meg pipe full of mostly data, instead of clogging it with ACKs and other overhead when we try to cram too much into it all at once.

Possibly, but i still thing something's borked.
The problem has generally been downloads killing uploads, not the other way around. At the present rate it'll take a couple of days for the uploads to clear.

Bloody moderators moving things around while I'm typing - got a 'Wrong Thread' error.

Anyway, to repeat what you didn't see me say:

I'm going to turn networking off, and go out to the pub. When you lot have finished crowding round the 'upload' door, could you leave a little space when I get back to get mine through? :-)

I'm going to turn networking off,

Already done that myself. Tried for 30min and not one got through so decided to wait till things start to clear a bit.
Being this far from the servers getting through all those other attempts just isn't possible.

---

Grant
Darwin NT

Hi Grant,

I posted an hour ago, asking what a 'good' wait is.
So far, I've waited since Sunday.

Yes, I understand about traffic - just want to know what the average number of days one should wait for a job to upload.

Any guess?

Thanks,
Jay

it looks like they know and are working the issue... and they hope it will level out soon. see new post at top of the board

---

no problemo's here - reattached project today - got work . . . crunchin' [Issues been fixed]

btw - Thanks to All @ Berkeley . . .

< nEXt

---

BOINC Wiki . . .

Science Status Page . . .

AFAIK, SETI@home Enhanced (MB) have min. 7 day deadline.
So normally enough time for UL and REPORT.


@ Richard

Well evening in the pub and Cheers! ;-)

---

So far, I've waited since Sunday.

Don't know why that should be the case.
From what i can recall on Sat, Sun & most of Monday there were no problems with uploads. Late Monday (for reasons unknown) the upload server went off line & it only came back online a couple of hours ago (if that).

Yes, I understand about traffic - just want to know what the average number of days one should wait for a job to upload.

Even when things are congested, most uploads will go through in a few hours. If it's really bad it might take 12-24hrs. Usually thay go through on the first attempt.

---

Grant
Darwin NT