Message boards : Server and website : Stuck on 'uploading'
Author | Message |
---|---|
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? | |
ID: 57772 | Rating: 0 | rate:
![]() ![]() ![]() | |
Reset the project is the easiest solution. | |
ID: 57773 | Rating: 0 | rate:
![]() ![]() ![]() | |
Hi, | |
ID: 57908 | Rating: 0 | rate:
![]() ![]() ![]() | |
DON'T reset the project. It won't help. | |
ID: 57909 | Rating: 0 | rate:
![]() ![]() ![]() | |
Thanks for quick answer. Waiting eagerly for the solution :) | |
ID: 57910 | Rating: 0 | rate:
![]() ![]() ![]() | |
Instructions for working round the 'expired certificate'problem at GPUGrid. | |
ID: 57912 | Rating: 0 | rate:
![]() ![]() ![]() | |
Every text editor has a "search and replace" function, so it's easier to use it when editing the clent_state.xml file. | |
ID: 57913 | Rating: 0 | rate:
![]() ![]() ![]() | |
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. | |
ID: 57915 | Rating: 0 | rate:
![]() ![]() ![]() | |
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. | |
ID: 57916 | Rating: 0 | rate:
![]() ![]() ![]() | |
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/ | |
ID: 57917 | Rating: 0 | rate:
![]() ![]() ![]() | |
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). | |
ID: 57921 | Rating: 0 | rate:
![]() ![]() ![]() | |
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? ____________ ![]() | |
ID: 57923 | Rating: 0 | rate:
![]() ![]() ![]() | |
so?So, change them to http if you want to bypass the certificate error. | |
ID: 57924 | Rating: 0 | rate:
![]() ![]() ![]() | |
oh sorry, i misread your post, I thought you were going the other way round (http->https). I'll try that. | |
ID: 57925 | Rating: 0 | rate:
![]() ![]() ![]() | |
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. | |
ID: 57926 | Rating: 0 | rate:
![]() ![]() ![]() | |
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. | |
ID: 57927 | Rating: 0 | rate:
![]() ![]() ![]() | |
Worked like a charm for me as well. Thanks for the instructions. Changed the authentificator to the weak account key beforehand as suggested. | |
ID: 57928 | Rating: 0 | rate:
![]() ![]() ![]() | |
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 | |
ID: 57929 | Rating: 0 | rate:
![]() ![]() ![]() | |
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. | |
ID: 57930 | Rating: 0 | rate:
![]() ![]() ![]() | |
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. | |
ID: 57934 | Rating: 0 | rate:
![]() ![]() ![]() | |
Instructions for working round the 'expired certificate'problem at GPUGrid. Hello Richard for this full explanation. Like you write, not easy. By the way, why, we need to solve the problems, if admin seems to do nothing ? I have try your solution. Instead of CA error, now I have transient error. So, roll back to normal settings. Once again, thank you for yourhelp. ____________ ![]() | |
ID: 57937 | Rating: 0 | rate:
![]() ![]() ![]() | |
By the way, why, we need to solve the problems, if admin seems to do nothing ? My sympathies are with the project's scientific researchers, who are probably just as exasperated with the project's administrators as we are. This problem has surfaced on a Sunday, which is probably the worst day of the week for a quick fix. Doing what we can to get results back for the scientists is at least a token attempt to keep things running, until the administrators reach their desks tomorrow. | |
ID: 57939 | Rating: 0 | rate:
![]() ![]() ![]() | |
I tried as RH instructed. | |
ID: 57940 | Rating: 0 | rate:
![]() ![]() ![]() | |
.. but than I couldn't verify that new tasks were alocated (how can thez be if network is suspended in step 1)?)? Learn to use other parts of BOINC's user interface. Switch to 'Advanced view', if you haven't already. Pressing 'Update' while networking is suspended temporarily allows that one single request to get out to the network. If it is successful, files awaiting transfer will appear on the 'Transfers' tab. The tasks themselves will be visible on the tasks tab, and details of the transaction will be listed in the Event Log. | |
ID: 57941 | Rating: 0 | rate:
![]() ![]() ![]() | |
@Richard Haselgrove: since always I've been using Advanced view, which doesn't meen at all that I am advanced... (for years i've only been running Einstein, Milkywy, WCG - projects that in all the years didn't request any intervention, so... no opportunity to learn there). :) | |
ID: 57945 | Rating: 0 | rate:
![]() ![]() ![]() | |
Sorry, once the server has decided on an outcome, that's the end of it. We can only influence the outcome before that final report has been made. | |
ID: 57947 | Rating: 0 | rate:
![]() ![]() ![]() | |
:( 4GPUs working for almost a day... | |
ID: 57948 | Rating: 0 | rate:
![]() ![]() ![]() | |
Will the administrators actually fix this problem by updating the required certificate. Seems the obvious solution. | |
ID: 57949 | Rating: 0 | rate:
![]() ![]() ![]() | |
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. didnt work for me. I was in the same situation. tasks "uploaded" but would not "report". changed the scheduler_url to http. nothing. changed the master url to http and it bombed the whole project lol. now it can't re-attach until it's fixed. so yeah, changing the master url is not the right move and will just make you lose everything. it's basically like hitting project reset. glad I only had one stuck task to lose. ____________ ![]() | |
ID: 57950 | Rating: 0 | rate:
![]() ![]() ![]() | |
The tasks aren't due until Dec 2. So I will wait to try this until just before they are late, hoping the crew issue will be fixed before that. | |
ID: 57951 | Rating: 0 | rate:
![]() ![]() ![]() | |
Will the administrators actually fix this problem by updating the required certificate. Seems the obvious solution. all we can do is hope. Although I am unsure how long this will take to happen | |
ID: 57952 | Rating: 0 | rate:
![]() ![]() ![]() | |
Just had a brief database outage, so somebody's awake and poking around. Two of my manual downloads from yesterday have uploaded and reported, without further manual intervention. | |
ID: 57953 | Rating: 0 | rate:
![]() ![]() ![]() | |
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. I did the same exact thing and had the same outcome. Essentially a project reset on the daily driver. Lost one task. | |
ID: 57968 | Rating: 0 | rate:
![]() ![]() ![]() | |
I can't find link to this page anywhere | |
ID: 57982 | Rating: 0 | rate:
![]() ![]() ![]() | |
I can't find link to this page anywhereI've made one for you above. The link gone missing when the webpage redesigned a couple of years ago. | |
ID: 57984 | Rating: 0 | rate:
![]() ![]() ![]() | |
I can't find link to this page anywhereI've made one for you above. Not missing. Apparently it was put on the “Join Us” page. http://www.gpugrid.net/join.php ____________ ![]() | |
ID: 57989 | Rating: 0 | rate:
![]() ![]() ![]() | |
Thanks to Richard Haselgrove for attempting a workaround narrative to my OP. | |
ID: 58027 | Rating: 0 | rate:
![]() ![]() ![]() | |
Your Manager will not report the latest available BOINC Client and Manager. You are currently running an outdated BOINC package with a known flaw of an expired SSL certificate at the end of September that prevents correct communication with many projects including this one. | |
ID: 58036 | Rating: 0 | rate:
![]() ![]() ![]() | |
5) Locate the line that starts <scheduler_url> (towards the end of the first section, above <code_sign_key>)Is this still needed? | |
ID: 58051 | Rating: 0 | rate:
![]() ![]() ![]() | |
No, it was a temporary, already overcome situation. | |
ID: 58056 | Rating: 0 | rate:
![]() ![]() ![]() | |
No, it was a temporary, already overcome situation. | |
ID: 58057 | Rating: 0 | rate:
![]() ![]() ![]() | |
Message boards : Server and website : Stuck on 'uploading'