| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
zaschf
Advanced Cruncher New Zealand Joined: Jan 28, 2009 Post Count: 61 Status: Offline Project Badges:
|
Hello all,
----------------------------------------I have a seemingly simple issue but I can't resolve it. A task is sitting stuck 'uploading' on the BOINC manager Tasks window. The task is not actually uploading. The Transfers window is empty. This issue occurred during a power failure. On the 'My Contribution' web page it still shows as 'In Progress' so it didn't upload at all. On my BOINC manager I tried to abort the task to no avail. Anyone know a way to remove this errant task from my BOINC manager? Oh, and I'm running this all under Ubuntu 18.04.4 LTS Cheers, Frits.
Ubuntu 22.04.1 LTS [Linux 5.15.0-47-generic]
CPU: Intel Core i7-9700 @3.00GHz x 8 GPU: NVIDIA GeForce RTX2060 Rev. A plus a mighty Raspberry PI 4 |
||
|
|
Shebear
Cruncher United States Joined: Oct 26, 2007 Post Count: 7 Status: Offline Project Badges:
|
I am having this exact same problem. My machine is a Windows 7 that has run the software without issues for years.
Stephanie |
||
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3315 Status: Offline Project Badges:
|
I'm assuming you've tried the retry button.
----------------------------------------What does the event log show? ![]() - AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W - AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W - AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1684 Status: Offline Project Badges:
|
Because of the mentioned power failure, the transfer transaction has not been correctly completed.
----------------------------------------Within the last 13 years, I did experience this situation twice. The WU transfer has not been fully acknowledge in client_state.xml because of external problem (usually power failure) The only way to solve this issue is to look for the troubling WU ID, to stop boinc, to edit manually client_state.xml, suppressing all the entries (usually 2) related to the identified WU ID. BE VERY CAREFUL by editing client_state.xml, since you can significantly disturb boinc if you make a mistake (before I did it for the first time, I waited long months, hoping that the issue will correct itself ...). Afterwards, you shall restart boinc manually or reboot your machine. Cheers, Yves --- PS: In all cases, make a backup copy of client_state.xml prior editing it. |
||
|
|
|