Author |
Message |
Matt Send message
Joined: 11 Jan 13 Posts: 216 Credit: 846,538,252 RAC: 0 Level
Scientific publications
|
I'm receiving an upload error that looks like this:
10/1/2013 8:52:22 AM | GPUGRID | Started upload of I35R6-NATHAN_KIDKIXc22_6-15-50-RND3209_0_9
10/1/2013 8:52:28 AM | GPUGRID | [error] Error reported by file upload server: [I35R6-NATHAN_KIDKIXc22_6-15-50-RND3209_0_9] locked by file_upload_handler PID=21220
10/1/2013 8:52:28 AM | GPUGRID | Temporarily failed upload of I35R6-NATHAN_KIDKIXc22_6-15-50-RND3209_0_9: transient upload error
I've had a few of these happen to me in the last week. What it seems to result in is that once the upload has finally been allowed to complete, it never shows up as completed in my Results list. Any ideas? |
|
|
flashawkSend message
Joined: 18 Jun 12 Posts: 297 Credit: 3,572,627,986 RAC: 0 Level
Scientific publications
|
What about your antivirus software? |
|
|
Matt Send message
Joined: 11 Jan 13 Posts: 216 Credit: 846,538,252 RAC: 0 Level
Scientific publications
|
AVG. It's been installed nearly a year. I've only been having this problem in the last week or so. Right now, I'm not having problems with the majority of WUs, but I'm getting one of these errors every few days. My last completed WU (the one from the log in my original post) has been unable to upload for the last 6 hours. It keeps giving the same error. |
|
|
flashawkSend message
Joined: 18 Jun 12 Posts: 297 Credit: 3,572,627,986 RAC: 0 Level
Scientific publications
|
Did you look at the Stderr output file to see if there might be more information in it? Your computers are hidden so I couldn't look for my self. Hopefully, one of the project people will see this and might know what's up. |
|
|
skgivenVolunteer moderator Volunteer tester
Send message
Joined: 23 Apr 09 Posts: 3968 Credit: 1,995,359,260 RAC: 0 Level
Scientific publications
|
Can't see your systems and no link to WU, so can only go by the errors which say the upload is temporary.
Speculating, this could have been caused by connection issues; the file may have been locked because it was in the process of uploading when the upload was interrupted, and when your system tried to upload it again the server thought it was already being uploaded so refused the new connection. Alternatively the file might have uploaded, but your system thinks the upload didn't complete. Of course there are lots of other potential causes (server issues, slot corruption).
____________
FAQ's
HOW TO:
- Opt out of Beta Tests
- Ask for Help |
|
|
Matt Send message
Joined: 11 Jan 13 Posts: 216 Credit: 846,538,252 RAC: 0 Level
Scientific publications
|
Didn't realize I had my computer hidden. Should be visible now.
Here are two of the WUs I've had this issue with. The one from my original post seems to have finally uploaded and been validated, but these two appear as if I never completed them:
http://www.gpugrid.net/workunit.php?wuid=4806173
http://www.gpugrid.net/workunit.php?wuid=4798114
Another thing I'm just noticing. Whereas all my other WUs are attributed to Computer 143481, these two are attributed to computers with different numbers, although if you look at those computers they are definitely still me.
Computer 143481:http://www.gpugrid.net/show_host_detail.php?hostid=143481
And the two these WUs specify:
Computer 159300:http://www.gpugrid.net/show_host_detail.php?hostid=159300
Computer 159518:http://www.gpugrid.net/show_host_detail.php?hostid=159518 |
|
|
skgivenVolunteer moderator Volunteer tester
Send message
Joined: 23 Apr 09 Posts: 3968 Credit: 1,995,359,260 RAC: 0 Level
Scientific publications
|
Nobody else is reporting this issue, so it's likely an problem with your system.
If you removed the GPUGrid project, and then reattached and used backed up data that might explain what has been happening, but that's guesswork. Merging computers might have fixed it at the time (or not).
You don't want to be loosing days of work so I won't suggest a project reset and see if that works...
If you think there might be account or project corruptions in your Boinc folders I suggest you remove Boinc, check the disk drive, and reinstall Boinc.
Check Disk:
Open Windows Explorer (Start + E keys), Right click on the drive Boinc is installed on, select Properties, Tools, Check Now, Tick both boxes, Scan Now, and OK the request to run the check on the next reboot. If your Boinc data is on a different drive, scan that drive too.
I suggest you set no more tasks for all projects. Abort anything that has not started to run. Finish anything running. When tasks complete and upload, Uninstall Boinc, Delete the Boinc folders, set the disk check, restart, and then Reinstall Boinc. If you are using BAM attach to the account manager, else add each project you contribute to manually.
____________
FAQ's
HOW TO:
- Opt out of Beta Tests
- Ask for Help |
|
|
|
I think we should be clear that there are two separate and distinct problems discussed in this thread.
The first,
Error reported by file upload server: [I35R6-NATHAN_KIDKIXc22_6-15-50-RND3209_0_9] locked by file_upload_handler PID=21220
is as described in the thread title, and it is a server issue only. The server process lock on the file will - by design - be released after a predetermined time, and a subsequent attempt to upload the file should succeed. As it did this time - the task validated. People who encounter this problem should do nothing with their client except wait. No amount of fiddling at your end will cure it.
Secondly, and quite separately, there is the question of duplicate host records and ghost tasks. Experience at other BOINC projects suggests that both these are related to communications glitches between server and client: the client issues a work request, the server receives the request and acts on it, but the reply from server to client gets swallowed up by a passing internet black hole and never reaches the client.
Most forms of communication over computer networks - whether local or the internet - require an explicit 'ack' to signal completion, but this one doesn't. I'm not sure whether we should discuss this here as a server issue, or in Number Crunching as a client issue. |
|
|