Uploads failing on one system, do not see this problem on other two systems running Einstein -
Einstein@Home | 8/16/2012 6:24:30 PM | Started upload of p2030.20090730.G55.84+00.77.C.b4s0g0.00000_2168_0_1
Einstein@Home | 8/16/2012 6:24:35 PM | [error] Error reported by file upload server: can't open file /BOINC/projects/EinsteinAtHome/upload/1a6/p2030.20090730.G55.84+00.77.C.b4s0g0.00000_2168_0_4: Permission denied (13)
Einstein@Home | 8/16/2012 6:24:33 PM | Temporarily failed upload of p2030.20090730.G55.84+00.77.C.b4s0g0.00000_2168_0_0: transient upload error
Einstein@Home | 8/16/2012 6:24:33 PM | Backing off 2 hr 14 min 36 sec on upload of p2030.20090730.G55.84+00.77.C.b4s0g0.00000_2168_0_0
Copyright © 2024 Einstein@Home. All rights reserved.
Upload Failure - Permission denied
)
These files were uploaded already on Aug 7 from a machine running on your account.
The server configuration (i.e. the user under which the file_upload_handler is running) has changed a bit since then, the current file_upload_handler can't overwrite the file created by the previous one. Technically this is a server side problem.
However the question remains why the Client tries to upload the same files again. Did you restore the BOINC directory from a backup?
BM
BM
It can happen when his client
)
It can happen when his client didn't get an ACK on upload, but the upload went through completely on both sides. Just the answer that it did went lost some corner of the internet.
So then the client will retry the upload until it gets an acknowledgment that the file was uploaded correctly. Mind, he won't be able to report this one either! Not without hacking the client_state.xml file... or you just setting the work-unit as done for all who done it and give credit by hand.
Yep, I just noticed that the
)
Yep, I just noticed that the result was completely uploaded, but never reported.
There are probably more Clients affected. I'll fix that in the filesystem. May take a bit, though, it holds millions of result files.
BM
BM