I get the following message then trying to upload finished wu:

29.11.2006 12:24:28|rosetta@home|Error on file upload: [CAPRI_11_V2H2_GLOBAL_DOCKING_1413_4252_0_0] locked by file_upload_handler PID=-1

So, whats wrong?

---

My NEW BOINC-Site

Why people joined BOINC Synergy...

Hmmm, sounds like same problem Buffalo Bill was having. Look here for additional discussion.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

I can confirm that we have already collected successfully most of the CAPRI jobs from the first few batches. It does not look like a general problem.

I get the following message then trying to upload finished wu:

29.11.2006 12:24:28|rosetta@home|Error on file upload: [CAPRI_11_V2H2_GLOBAL_DOCKING_1413_4252_0_0] locked by file_upload_handler PID=-1

So, whats wrong?

---

I get the following message then trying to upload finished wu:

29.11.2006 12:24:28|rosetta@home|Error on file upload: [CAPRI_11_V2H2_GLOBAL_DOCKING_1413_4252_0_0] locked by file_upload_handler PID=-1

So, whats wrong?

To make sure only one process is trying to write to the same file, 2 writing to same file can lead to file-corruption, the upload-handler is using a "lock". In case an upload gets interrupted before finished, Upload-server sometimes doesn't get this "lost connection", so keeps the lock until reaches a time-out server-side. While waiting on this time-out, if you tries to upload same file again, you'll get the "locked by file_upload_handler PID=123..."

Not sure on how long the time-out is, but after client does maybe 6-7 backoffs, the old "lock" times-out server-side, and client can finish the upload normally.


So basically, if upload continues after waiting 1 hour, there aren't anything wrong.

---

"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."