Stuck on 'uploading'
Message boards :
Server and website :
Stuck on 'uploading'
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 2 Apr 09 Posts: 10 Credit: 90,125,593 RAC: 18,119 Level  Scientific publications 
|
I have a WU that has been reporting 'uploading' since around 3 October 2021) it's currently 5 November). Nothing seems to be happening. Despite the WU taking 2d6h to process, I have tried to abort it in desperation. I can't even do that, it is just stuck there. Please can anyone offer advice on this? |
 Send message Joined: 13 Dec 17 Posts: 1424 Credit: 9,189,946,190 RAC: 8 Level  Scientific publications    
|
Reset the project is the easiest solution. But first, make sure you are running the latest BOINC client that has the fix for the expired security certificate that caused the stalled upload in the first place. https://boinc.berkeley.edu/download_all.php |
|
Send message Joined: 4 Jul 21 Posts: 23 Credit: 12,162,988,127 RAC: 148,934 Level  Scientific publications
|
Hi, I have the same problem. 15 WUs are waiting for upload in Transfers (two computers, one Windows one Linux). If I reset the project, do I loose the WUs? :( Or is it possible to backup the completed WUs somewhere on the disk and resend them after resetting the project? 7 WUs where sent normally from the same two computers on 26th of November. I don't remember changing anything... |
|
Send message Joined: 11 Jul 09 Posts: 1639 Credit: 10,159,968,649 RAC: 0 Level Scientific publications  
|
DON'T reset the project. It won't help. I have both reported completed work, and downloaded new work, on four machines this morning - two Linux, and two Windows. But it's a complicated process, and has to be followed exactly. It'll take a while for me to write it up - please be patient. |
|
Send message Joined: 4 Jul 21 Posts: 23 Credit: 12,162,988,127 RAC: 148,934 Level Scientific publications
|
Thanks for quick answer. Waiting eagerly for the solution :) More info: I see now that all (3) my hosts last connected to gpugrid on 27th at around 11P.M. They all reported sucesfull tasks on 26th. |
|
Send message Joined: 11 Jul 09 Posts: 1639 Credit: 10,159,968,649 RAC: 0 Level Scientific publications
|
Instructions for working round the 'expired certificate'problem at GPUGrid. -1) Set 'No new tasks' for GRUGid. You cannot both report completed work, and request new work, in the same operation. Read the following instructions carefully and fully before starting. If you don't understand anything, STOP - now is not the moment to start learning about BOINC. To report completed work: 1) Stop the BOINC client. 2) Navigate to the BOINC data directory. 3) Open the file 'client_state.xml' for editing, using a plain text editor. 4) Locate the section for GPUGrid. Don't change anything outside this section. 5) Locate the line that starts <scheduler_url> (towards the end of the first section, above <code_sign_key>) 6) Change the scheduler url from https to http 7) Find every example of <upload_url> within the GPUGrid section. Change https to http 8) Save the edited file 9) Restart the BOINC client. GPUGrid files should upload, and finisted tasks should report, automatically - possibly after a short delay while benchmarks are run. To fetch new work: 0) This assumes you have modified the scheduler url to report completed work. If you haven't done that already, do it now. 1) From the 'Activity' menu in BOINC Manager, suspend network activity. 2) Allow new work for GPUGrid 3) Update the GPUGrid project manually. It won't do this automatically while networking is suspended. 4) Verify that new task(s) have been allocated, and that files are waiting to download. 5) Set 'No new work' again for GPUGrid 6) Stop the BOINC client. 7) Navigate to the BOINC data directory. 8) Open the file 'client_state.xml' for editing, using a plain text editor. 9) Locate the section for GPUGrid. Don't change anything outside this section. 10) Find every example of <download_url> within the GPUGrid section. Change https to http 11) You may as well change the new upload urls to http while you're here - it'll save time when the task finishes. 12) Save the edited file 13) Restart the BOINC client. GPUGrid files should download, and new tasks should start running, automatically - possibly after a short delay while benchmarks are run. |
 Retvari Zoltan Send message Joined: 20 Jan 09 Posts: 2380 Credit: 16,897,957,044 RAC: 0 Level Scientific publications
|
Every text editor has a "search and replace" function, so it's easier to use it when editing the clent_state.xml file. Search for: https://www.gpugrid.net Replace to: http://www.gpugrid.net Is there a way to make this change permanent? I've tried to edit the account_www.gpugrid.net.xml file, but it still tries to pull the new tasks using https. I will try to detach one of my hosts, and reattach manually through http://www.gpugrid.net |
|
Send message Joined: 11 Jul 09 Posts: 1639 Credit: 10,159,968,649 RAC: 0 Level Scientific publications
|
Is there a way to make this change permanent? Every new task requires new files to be downloaded, and each new download comes with its own url - https by default. so NO. |
|
Send message Joined: 26 Dec 13 Posts: 87 Credit: 1,292,358,731 RAC: 0 Level  Scientific publications 
|
NB! If you change project url from secure HTTPS to unsecure HTTP, it's wise to beforehand change authentication key( <authenticator></authenticator> ) in account_www.gpugrid.net.xml to weak account key( https://gpugrid.net/weak_auth.php ) to prevent account abuse if http traffic will be sniffed by someone. |
|
Retvari Zoltan Send message Joined: 20 Jan 09 Posts: 2380 Credit: 16,897,957,044 RAC: 0 Level Scientific publications
|
I will try to detach one of my hosts, and reattach manually through http://www.gpugrid.netDon't try this, as you won't be able to attach your host to the project again. You should ignore the message: GPUGRID: Notice from BOINC You are attached to this project twice. Please remove projects named GPUGRID, then add https://www.gpugrid.net/ |
|
Send message Joined: 26 Dec 13 Posts: 87 Credit: 1,292,358,731 RAC: 0 Level Scientific publications
|
Instructions for working round the 'expired certificate'problem at GPUGrid. I didn't remember if the project state in the BOINC client would reset when project_url was changed, so I went a different way to get around the problem of checking an expired certificate - "a little" more stoned xD 1) Created a local CA (for simplicity, you can use Easy-RSA, there are a lot of instructions on the Internet) and issued a certificate for www.gpugrid.net 2) Added a local CA to the client's ca-bundle BOINC. 3) Changed <authenticator></authenticator> in account_www.gpugrid.net.xml to weak account key( https://gpugrid.net/weak_auth.php ) to prevent account abuse if http traffic will be sniffed by someone. 4) Configured stunnel to accept HTTPS on localhost(127.0.0.1) for BOINC client and transmit unencrypted HTTP to GPUGRID's IP-address 84.89.134.145 (Yeah, it's not secure, but weak account key used for authentication). 5) In hosts file for www.gpugrid.net reassigned IP-address to 127.0.0.1 (localhost). 6) PROFIT! xD If suddenly someone will be interested in this variant, I can try to make instructions for Windows(for *nix-like, in principle, everything is the same, only file's paths differ, and I think that *nix users can cope with this task anyway). |
|
Send message Joined: 21 Feb 20 Posts: 1116 Credit: 40,876,970,595 RAC: 2 Level Scientific publications
|
Instructions for working round the 'expired certificate'problem at GPUGrid. yesterday I downloaded 2 tasks, then set NNT. one completed and uploaded. the other is "stuck" in uploading. the file size is not too big (290MB and less, max_nbytes set to 1024MB), and the upload URLs are already all https. so? 
|
|
Send message Joined: 11 Jul 09 Posts: 1639 Credit: 10,159,968,649 RAC: 0 Level Scientific publications
|
so?So, change them to http if you want to bypass the certificate error. |
|
Send message Joined: 21 Feb 20 Posts: 1116 Credit: 40,876,970,595 RAC: 2 Level Scientific publications
|
oh sorry, i misread your post, I thought you were going the other way round (http->https). I'll try that.
|
|
Send message Joined: 11 Jul 09 Posts: 1639 Credit: 10,159,968,649 RAC: 0 Level Scientific publications
|
oh sorry, i misread your post, I thought you were going the other way round (http->https). I'll try that. Read it carefully, and fully. All steps are necessary, and in the order I've given them. |
|
Send message Joined: 21 Feb 20 Posts: 1116 Credit: 40,876,970,595 RAC: 2 Level Scientific publications
|
I understand it. the task is trivial for me, editing client_state is no big deal. as zoltan pointed out, find and replace of the entire upload URL (it's not present anywhere else) works fine. it's done, and works. thanks.
|
|
Send message Joined: 22 May 20 Posts: 110 Credit: 115,525,136 RAC: 0 Level  Scientific publications
|
Worked like a charm for me as well. Thanks for the instructions. Changed the authentificator to the weak account key beforehand as suggested. Edit: @Ian: your machine is a beast. the 3080Ti finished the WU ~4x faster than my 1660S. times are calling for an update. wish the prices would finally relax a little bit but might be way too soon to even hope for... |
|
Send message Joined: 16 Jul 07 Posts: 209 Credit: 6,054,860,456 RAC: 1,428,878 Level Scientific publications
|
Instructions for working round the 'expired certificate'problem at GPUGrid. I followed the instructions (and thanks for posting that!), and it worked to get the files uploaded. But the task will not report. I have this same problem across 3 different machines. I get the following: 131 GPUGRID 11/28/2021 7:18:52 AM update requested by user 135 GPUGRID 11/28/2021 7:19:01 AM [sched_op] Fetching master file 136 GPUGRID 11/28/2021 7:19:01 AM Fetching scheduler list 137 GPUGRID 11/28/2021 7:19:03 AM [sched_op] Deferring communication for 1 days 00:00:00 138 GPUGRID 11/28/2021 7:19:03 AM [sched_op] Reason: 52 consecutive failures fetching scheduler list FWIW, I did update the "<scheduler_url>" line as instructed. Reno, NV Team: SETI.USA |
|
Send message Joined: 11 Jul 09 Posts: 1639 Credit: 10,159,968,649 RAC: 0 Level Scientific publications
|
If you've reached that state (implying 10 or more consecutive failed attempts to contact the scheduler), you'll probably have to change the "<master_url>" - first line in the project section, in client_state.xml - to http like the others. But don't change that line - with a global replace or otherwise - unless you really have to. You'll get warning messages in the Event Log. Edit - after you change the master url, you'll probably be sent a new scheduler url. But that'll be https again, so then you'll need to change that again, as well. |
|
Send message Joined: 28 Mar 09 Posts: 490 Credit: 11,850,145,728 RAC: 301,281 Level Scientific publications
|
Moving the clock (time and date) back on the host, also works, but boinc runs a little funky, so as soon as you finish uploading, downloading and/or reporting your WUs, switch it back. |
©2026 Universitat Pompeu Fabra