Permanent Upload Certificate Error

Message boards : Bug reports : Permanent Upload Certificate Error

To post messages, you must log in.

AuthorMessage
Jon Fox

Send message
Joined: 22 Sep 07
Posts: 1
Credit: 298,824
RAC: 0
Message 2143 - Posted: 30 Oct 2011, 13:49:43 UTC
Last modified: 30 Oct 2011, 14:10:30 UTC

Sun Oct 30 07:52:25 2011 | Enigma@Home | [error] Error reported by file upload server: invalid signature
Sun Oct 30 07:52:25 2011 | Enigma@Home | Giving up on upload of rxpsb107-p2_0_13709062_25078_0_0: permanent upload error

From the BOINC forums:


David Anderson wrote:
There are (at least) two issues with 6.13.3:

1) For GPU apps, it passes an additional command-line argument that causes some apps to fail (usually by exiting immediately). This will be fixed in 6.13.4.

2) 6.13.3 handles file upload certificates (a mechanism that prevents DoS attacks on upload servers) differently than previous versions.
This change was necessary to make scheduler requests and replies readable by standard XML parsers. But it means that file uploads will fail to projects that a) use upload certificates, and b) aren't running current server code.

I sent email to boinc_projects describing this change, and recommending that projects disable upload certificates until they're able to upgrade their server code. Not all project admins read boinc_projects, so it may be necessary to contact them via their message boards or email, and I urge Alpha-testers to do so.

-- David


David Anderson, boinc_projects email list wrote:
"Upload certificates" are a mechanism that keeps bad guys from DoS'ing your upload servers (note: such an attack has never happened, as far as I know).

We're changing the format of upload certificates, and we're starting to test a version of the client for which old-format certificates won't work. Volunteers testers won't be able to upload completed jobs, and they may complain to you.

I suggest that all projects disable upload certificates. To do so, add the following to your config.xml file:

<dont_generate_upload_certificates/>
<ignore_upload_certificates/>

To resume using upload certificates, if you wish:

1) upgrade to the current server source code (from trunk)
2) wait for all jobs with old-format certificates to be dispatched
3) re-enable certificates by removing the above lines.

Let me know if any questions.

-- David
ID: 2143 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Ageless
Volunteer moderator
Volunteer tester
Avatar

Send message
Joined: 11 Sep 07
Posts: 104
Credit: 155,932
RAC: 0
Message 2145 - Posted: 31 Oct 2011, 16:43:00 UTC

Please Slawek, can you do this? We're testing 6.13.10 at the moment, we're going to a more public BOINC 7 in a bit and this disturbs the work flow, all the work we're trying to return gets debunked as bad and has to be sent out again. Plus the people running the alpha/beta client do work for nothing.
Jord.

BOINC FAQ Service.
ID: 2145 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile TJM
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 25 Aug 07
Posts: 843
Credit: 69,983,998
RAC: 386,225
Message 2146 - Posted: 31 Oct 2011, 17:02:33 UTC

Hm it was already disabled a couple of days ago, perhaps I forgot to restart the server.

M4 Project homepage
M4 Project wiki
ID: 2146 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Ageless
Volunteer moderator
Volunteer tester
Avatar

Send message
Joined: 11 Sep 07
Posts: 104
Credit: 155,932
RAC: 0
Message 2147 - Posted: 31 Oct 2011, 17:42:11 UTC - in response to Message 2146.  
Last modified: 31 Oct 2011, 17:43:08 UTC

If you have more than one upload server, you have to disable the certificates on all of them.

Things seem 'broken' here anyway, as my signature is missing. ;-)
Jord.

BOINC FAQ Service.
ID: 2147 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Ageless
Volunteer moderator
Volunteer tester
Avatar

Send message
Joined: 11 Sep 07
Posts: 104
Credit: 155,932
RAC: 0
Message 2148 - Posted: 31 Oct 2011, 21:11:13 UTC - in response to Message 2146.  

Whatever it is you did, it fixed the upload problem. :-)

31/10/2011 21:34:13 | Enigma@Home | Started upload of fmngi58-1_0_13709167_113_0_0
31/10/2011 21:34:13 | Enigma@Home | [file_xfer] URL: http://www.enigmaathome.net/file_upload_handler
31/10/2011 21:34:13 | | [statefile] set dirty: pers_file_xfer_set poll
31/10/2011 21:34:13 | | [statefile] Writing state file
31/10/2011 21:34:13 | | [statefile] Done writing state file
31/10/2011 21:34:14 | Enigma@Home | [file_xfer] http op done; retval 0 (Success)
31/10/2011 21:34:14 | Enigma@Home | [file_xfer] parsing upload response: <data_server_reply> <status>0</status></data_server_reply>
31/10/2011 21:34:14 | Enigma@Home | [file_xfer] parsing status: 0
31/10/2011 21:34:14 | Enigma@Home | [file_xfer] file transfer status 0 (Success)
31/10/2011 21:34:14 | Enigma@Home | Finished upload of fmngi58-1_0_13709167_113_0_0
31/10/2011 21:34:14 | Enigma@Home | [file_xfer] Throughput 184 bytes/sec
31/10/2011 21:34:14 | | [work_fetch] Request work fetch: project finished uploading

Jord.

BOINC FAQ Service.
ID: 2148 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Message boards : Bug reports : Permanent Upload Certificate Error




Copyright © 2017 TJM