Hm, maybe I just never noticed but after seeing an Upload Transfer Queue having built up, I had a look at it.

While some Results (jump-neg-****) are only 30-50kb, I also have a series of _CAPRI17_T38*** that clock in between 7500kb and over 10000kB *ugh*

Considering I can't seem to upload at the moment, is that a normal Upload Data size for that type of WorkUnit or is that an anomaly (and possibly the cause fo my stuck Upload Queue) ?

My ADSL Upload is upto 45kb/sec but squeezing a Queue of (currently) ~166MB through it really takes some time, even if it was working normal :P

---

I have had one of the small guys ~ 48kb thats been stuck trying to upload all nite long, so unless there are a bunch of you folks with those huge guys jamming things up it may just be that the upload server is fubar?

---

That would be unusually large FalconFly. The good news is that BOINC is able to make partial transfers and continue from where it left off if necessary.

Check the transfers tab and see if you've actually got any data moving, or if the upload server is really the current problem.

Both issues are certainly possible. If several others have these large results files, that's going to bogg down the upload server. On the other hand, the Project Team will need to see what they are filled with in order to address the problem.

---

Rosetta Moderator: Mod.Sense

I've notified the Project Team about this.

If you cancel the upload, you won't get credit. But, since the upload is choking your bandwidth, you might want to suspend work on any unfinished CAPRI17 tasks until we get more information about what has happened.

If you are seeing sluggish internet access because of these transfers, you could suspend network while you use the internet, and then allow network access again when you are done. This is done on the advanced view, on the "activity" dropdown menu.

---

Rosetta Moderator: Mod.Sense

Time here is UTC +1

I have a 61.53 kb file trying to upload and I get this:

1/17/2009 7:54:49 PM|rosetta@home|Sending scheduler request: Requested by user. Requesting 80668 seconds of work, reporting 0 completed tasks
1/17/2009 7:55:11 PM||Project communication failed: attempting access to reference site
1/17/2009 7:55:12 PM||Internet access OK - project servers may be temporarily down.
1/17/2009 7:55:14 PM|rosetta@home|Scheduler request failed: Couldn't connect to server

This has been going on since 10am my time.
Also looks like Einstein had a brief outage as well.

The server status page shows everything in green, so is there a comm problem now instead of a computer problem?

That would be unusually large FalconFly. The good news is that BOINC is able to make partial transfers and continue from where it left off if necessary.

Check the transfers tab and see if you've actually got any data moving, or if the upload server is really the current problem.

Both issues are certainly possible. If several others have these large results files, that's going to bogg down the upload server. On the other hand, the Project Team will need to see what they are filled with in order to address the problem.

Alright, as of now I'm seeing a total of 230MB in the Upload Queue.
None of the transfers in my current upload queue (not even the very small ones) was able to transfer more than ~3kB before stalling.

Additionally, my BOINC 5.10.45 installations do not seem to download new WorkUnits at normal rate, I'm hardly receiving any.
The Message Tabs are full of these lines :
Temporarily failed upload of _CAPRI17_T38_2_.sjf_br_docking.protocol__6221_13586_0_0: http error
Backing off 24 min 46 sec on upload of _CAPRI17_T38_2_.sjf_br_docking.protocol__6221_13586_0_0

Additionally, I got a few of those :
Sending scheduler request: To fetch work. Requesting 19271 seconds of work, reporting 0 completed tasks
Scheduler request failed: HTTP gateway timeout


==========================
I have Climate Prediction working parallel, its transfers work normal on all Systems, Internet connection is working fine as well.

--- edit ---

Just now I'm seeing a single large Result being transferred at good speed (2108 UTC time).
According to my Results table, however, my Network actualy has been reporting results throughout the day.
But apparently reporting/downloading any took longer than computing fresh ones, leading to my Network running dry and the upload queue filling up.

---

I've been having upload problems as well. This message comes up:

1/17/2009 13:36:26|rosetta@home|[file_xfer] Temporarily failed upload of SrR115G_t074_1_RDC_NMR_NESG_SAVE_ALL_OUT_6214_18454_0_0: system connect
along with the statement that the project servers could be down. I've been able to upload other WUs, but my host cannot connect to report any of my finished WUs, so my Tasks tab lists them as Ready to Report. For me, it's been doing this for a few hours. I've been hoping to resolve these before I unplug my computer so it can be minorly-repaired while I'm out of town. They'll have to wait until next week. :(

---

from what i am seeing on my machine, communications are sporadic at best and uploads/reporting are a 50/50 chance of going through.

it is now 22;48 utc and i am waiting to get new work, but can not, even though there is communications to the server.

Apparently all solved overnight, all is back to normal here :)

---