Upload server problems resolved

Jim Wilkins
Jim Wilkins
Joined: 1 Jun 05
Posts: 33
Credit: 28,426,884
RAC: 0

All of my previously stuck

All of my previously stuck ones are now unstuck, so something good happened.

Roland Hughes
Roland Hughes
Joined: 14 Nov 09
Posts: 10
Credit: 20,684,902
RAC: 1,838

Well, at 3:30 this morning it

Well, at 3:30 this morning it was a goodly number, I didn't count, but they appeared to be stacking up. Clicking retry-now numerous times proved to be useless.

Only the half dozen packets on the Cinnamon partition of this machine are of significant issue. The only reason that partition still exists is to report those WU and I can't leave it up. Only boot that for under an hour per day just to try and check those WU in.

I'm certain they will miss deadlines, no matter what they are, because this machine has been re-purposed for another project. Cinnamon partition will be booted over lunch hour, then again over supper time. After supper, they physically won't exist.

I did check the other machines after reading your message. They seem to have finally cleared though clicking on retry-now earlier only got them longer back-off times.

Were there instructions on how to migrate completed WUs from one machine to another then have the other machine upload them that would solve the issue. There are two lesser machines running BOINC which I could happily assign the reporting task.

Richard Haselgrove
Richard Haselgrove
Joined: 10 Dec 05
Posts: 1,938
Credit: 273,142,882
RAC: 106,486

RE: Were there instructions

Quote:
Were there instructions on how to migrate completed WUs from one machine to another then have the other machine upload them that would solve the issue. There are two lesser machines running BOINC which I could happily assign the reporting task.


You can't migrate individual tasks from a BOINC installation on one machine to a running BOINC installation on a different machine - the tasks would be rejected because the report came from a different HostID than expected.

But you can achieve the final clean-up for a retiring machine quite easily, provided you have a second machine running the same (or a compatible) operating system, and running BOINC (even if only temporarily).

First, fire up BOINC on the machine being retired, for one last time. Set 'No New Tasks' for all projects, to prevent any accidents later. If you've done that already, you can skip this step.

Close BOINC down, and locate the BOINC data folder. Copy or archive the entire data folder - including all subfolders - to removable media or a network location. The old machine can be surrendered now.

Switch your attention to the new machine. Shut down BOINC if it is running. Locate that machine's BOINC data folder, back it up, and move it to a safe location where BOINC won't see it. Then, put the data folder recovered from the old machine in place of the one you've just moved from the new machine.

Start BOINC on the new machine. It will now be impersonating the old machine, and the uploads, completed tasks etc. should be visible. Complete all the pending operations as needed.

Finally, close BOINC down again, reverse the data folder swap, and you can go back to normal crunching.

Roland Hughes
Roland Hughes
Joined: 14 Nov 09
Posts: 10
Credit: 20,684,902
RAC: 1,838

RE: RE: Were there

Quote:
Quote:
Were there instructions on how to migrate completed WUs from one machine to another then have the other machine upload them that would solve the issue. There are two lesser machines running BOINC which I could happily assign the reporting task.

You can't migrate individual tasks from a BOINC installation on one machine to a running BOINC installation on a different machine - the tasks would be rejected because the report came from a different HostID than expected.

But you can achieve the final clean-up for a retiring machine quite easily, provided you have a second machine running the same (or a compatible) operating system, and running BOINC (even if only temporarily).

First, fire up BOINC on the machine being retired, for one last time. Set 'No New Tasks' for all projects, to prevent any accidents later. If you've done that already, you can skip this step.

Close BOINC down, and locate the BOINC data folder. Copy or archive the entire data folder - including all subfolders - to removable media or a network location. The old machine can be surrendered now.

Switch your attention to the new machine. Shut down BOINC if it is running. Locate that machine's BOINC data folder, back it up, and move it to a safe location where BOINC won't see it. Then, put the data folder recovered from the old machine in place of the one you've just moved from the new machine.

Start BOINC on the new machine. It will now be impersonating the old machine, and the uploads, completed tasks etc. should be visible. Complete all the pending operations as needed.

Finally, close BOINC down again, reverse the data folder swap, and you can go back to normal crunching.

Thank you,
I will give it a try this evening assuming the upload server is still telling me to back off. Otherwise those packets will be wasted cycles.

[TA]Assimilator1
[TA]Assimilator1
Joined: 22 Jan 05
Posts: 11
Credit: 184,551,007
RAC: 18

My uploads have cleared now.

My uploads have cleared now.

Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H.

Main rig - Ryzen 5 3600, 32GB DDR4 3200, RX 580 8GB, Win10 64bit

2nd rig - i7 4930k @4.1 GHz, 16GB DDR3 1866, HD 7870 XT 3GB(DS), Win 7 64bit

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.