Hello,

For more than 24 hours my system is trying to upload a WU. Do more people heave problem, or is it only me?
Do I have to use "abort transfer" in the transfers tab or just wait longer?

Thanks for the help.
TJ

---

Greetings,
TJ.

same here for about 6 hours,guess just need wait for longer.

Same here on two specific jobs. One from last night (1.87) and one from this morning (1.88). Several other WUs have gone through successfuly in that time. I have no idea why these are being left behind.

The file upload server has been having some problems. The uploads do not occur in order of completion when the client has to do retries hitting the server with the upload. Just depends on which connections get through and what delay time each gets when it has to wait and try later.

NO, don't abort the transfer. That's just throwing away your work, not helping anything other then your desire to have a transfers tab with no line items on it.

---

Rosetta Moderator: Mod.Sense

for several days I've been getting the following messages when I try to upload.

7/31/2009 12:03:20 PM rosetta@home Started upload of lr8_B_seq_score12_ss5.0_rlbd_2d4f_IGNORE_THE_REST_DECOY_14598_1689_0_0
7/31/2009 12:03:21 PM rosetta@home [error] Error reported by file upload server: [lr8_B_seq_score12_ss5.0_rlbd_2d4f_IGNORE_THE_REST_DECOY_14598_1689_0_0] locked by file_upload_handler PID=-1
7/31/2009 12:03:21 PM rosetta@home Temporarily failed upload of lr8_B_seq_score12_ss5.0_rlbd_2d4f_IGNORE_THE_REST_DECOY_14598_1689_0_0: transient upload error
7/31/2009 12:03:21 PM rosetta@home Backing off 16 min 30 sec on upload of lr8_B_seq_score12_ss5.0_rlbd_2d4f_IGNORE_THE_REST_DECOY_14598_1689_0_0

Other jobs are uploading fine. I've rebooted several times. any suggestions?

Tim

---

Other jobs are uploading fine. I've rebooted several times. any suggestions?

Tim

Just wait a few days. As Mod.Sense said, the servers are under a heavy load right now and may take several days to catch up. It is just a matter of luck as to which work units get through.

The only choices are to abort them or wait for the upload to complete, but aborting them will waste all the work you did on them.

---

Try forcing a manual retry of the send. Sometimes it takes a few tries, but I have found that I can get it through.

Try forcing a manual retry of the send. Sometimes it takes a few tries, but I have found that I can get it through.

While that may be a successful tactic for forcing your own work to upload, it is probably not a good idea for the project as a whole when the servers are under stress.

The servers are currently trying to catch up with all the outstanding communication, uploading and downloading after a few days of limited activity. When you force a communication with the server you are just increasing the amount of work the server has to cope with; repeat that with enough participants and the server will be so busy trying to sort through random communications that it has no time to upload or download anything.

---