Units getting stuck at 100%

[nothingspecial]

Getting units sticking at 100% over the last few days, and can't work out why, except I keep getting this in the log:

[00:42:54] + Attempting to send results [December 9 00:42:54 UTC]

[00:42:54] - Reading file work/wuresults_03.dat from core

[00:42:54] (Read 327563 bytes from disk)

[00:42:54] Gpu type=3 species=30.

[00:42:54] Connecting to http://171.67.108.54:8080/

[00:42:57] Posted data.

[00:42:57] Initial: 0000; - Uploaded at ~106 kB/s

[00:42:57] - Averaged speed for that direction ~106 kB/s

[00:42:57] + Results successfully sent

[00:42:57] Thank you for your contribution to Folding@Home.

[00:42:57] + Number of Units Completed: 298

[00:43:01] Trying to send all finished work units

[00:43:01] + No unsent completed units remaining.

[00:43:01] + -oneunit flag given and have now finished a unit. Exiting.***** Got a SIGTERM signal (2)

[00:43:01] Killing all core threads

Folding@Home Client Shutdown.

I've definately not set a -oneunit flag, but it keeps creating them randomly. Any ideas?

Edit: Restarting the rig seems to bump it into life

 

[yassarikhan786]

Are you using GPU Tracker or the Command Line?

 

[SieB]

You might have a corrupt WU. Go to client > GPU0 > delete WU and delete the WU.

Do the same for SMP as well if you do SMP I have had this happen to me before but not with GPU just SMP and deleting the WU worked. It might be something different though, one of the more experienced folders will know if it is anyway.

EDIT: forgot to mention there is an update for GPU tracker so make sure your version is up to date, just go to setup > check for updates it should then find them and ask if you want to download them.

 

[yassarikhan786]

I guess SieB answered my question

 

[SieB]

I'm just guessing but the same goes for any other client, if it is a corrupted WU

 

[yassarikhan786]

I'm just guessing but the same goes for any other client, if it is a corrupted WU

Cool. Thanks for the info, will come in handy for the future

.

 

[riotcity76]

Just so we're all on the same page here, GPU Tracker uses the -oneunit flag as part of its "featureset"...this allows you to make changes to your config while folding a WU and having the changes be reflected in the very next WU you start folding (automatically). I'm not sure if this has changed or not in the newest version...but that would be why the OP has the -oneunit flag set even though they have not manually set it.

 

[nothingspecial]

You might have a corrupt WU. Go to client > GPU0 > delete WU and delete the WU.

Do the same for SMP as well if you do SMP I have had this happen to me before but not with GPU just SMP and deleting the WU worked. It might be something different though, one of the more experienced folders will know if it is anyway.

EDIT: forgot to mention there is an update for GPU tracker so make sure your version is up to date, just go to setup > check for updates it should then find them and ask if you want to download them.

Just updating now. If that doesn't fix it, I'll try deleting the WU.

Just so we're all on the same page here, GPU Tracker uses the -oneunit flag as part of its "featureset"...this allows you to make changes to your config while folding a WU and having the changes be reflected in the very next WU you start folding (automatically). I'm not sure if this has changed or not in the newest version...but that would be why the OP has the -oneunit flag set even though they have not manually set it.

I'll keep an eye on that too. Cheers.

Many thanks all.

Edit: Just for info's sake, the client update (3.54) has fixed it. Cheers again.