Message boards :
Number crunching :
WU's not being recognised by BOINC
Message board moderation
Author | Message |
---|---|
Send message Joined: 25 Oct 04 Posts: 83 Credit: 78,941,926 RAC: 28,897 |
I had a nasty lockup and reset of my computer. I still have about 30 wu's in my boinc/projects/lhc folder. Yet, under the work tab on BOINC it does not show any of these. How do I re-start or re-initialise the wu's into boinc ? |
Send message Joined: 29 Sep 04 Posts: 196 Credit: 207,040 RAC: 0 |
How do I re-start or re-initialise the wu's into boinc ? That's very complicated. The WUs are listed in client_state.xml along with some additional information (checksum, size, state). You'd have to manually enter that information in for each work unit. Problem is doing it accurately and generating the checksum (if it's not identical to the one which was issued the WU will be invalid for "tampering"). So the easy fix: Start -> Run -> CMD Type "net stop boinc" Go back to the LHC@home folder and delete the affected WU zipfiles. Back at the command prompt type "net start boinc" Type "exit" Check your Boinc Manager to make sure no WUs are still being reported. (You may have to exit and open the BM after stopping the service) Wish I had better news for you especially since work has run out. [edit] I just saw your other message in another thread.. you wern't overclocking were you? :) |
Send message Joined: 25 Oct 04 Posts: 83 Credit: 78,941,926 RAC: 28,897 |
Yikes....I briefly looked at these files...messy work. Might there be any other process to integrate these WU's into boinc? Or should I report these as lost so the project can clean them up from my report? I understand the removal. This occured on my amd 4400 system. My overclock is at 210mhz up from stock speed of 200mhz. It has been this way since I first built this system. |
Send message Joined: 1 Sep 04 Posts: 506 Credit: 118,619 RAC: 0 |
My advice: leave well alone. There are enough complaints about ghost results, orphaned results, usw. without risking adding to the mess by manually fiddling with the client state files. If you have lost the work, that's too bad. The redundancy built into BOINC will see to it that the units are re-issued if necessary. Gaspode the UnDressed http://www.littlevale.co.uk |
Send message Joined: 29 Sep 04 Posts: 196 Credit: 207,040 RAC: 0 |
My overclock is at 210mhz up from stock speed of 200mhz. I suspected as much- when people experience the kind of lockup you had, either bad hardware or overclocking is the most likely cause. As discussed in other threads here at LHC, sixtrack is very sensitive to overclocking and it just makes sense given your symptoms and recent attachment. As far as your WUs.. take MikeW's advice. Just delete them. It's not worth it to try and salvage it. |
©2024 CERN