Gun Shy

Anonymous
Topic 13013

Quote:

Hey Tweakster,

If you have any h1_nnnn (note the small h) style work units on any of your boxes then you'll have to get rid of them ASAP as you'll be wasting cycles. I'm using 4.19 as it works well for me (mostly :).) and it's a bit of a chore to get rid of the cancelled work, as there is no abort button.

See Bruce's posts and my questions over in the main thread on this and I've just posted there what I did to get things moving again. Hope this helps. The good thing is that Bruce has reset to 8 the daily limit and this has worked for me as all my boxes that were suffering from this are now back at 8 after being much lower.

Note: I'll continue during the next few days to reset the daily limits by hand for hosts that got h1_ workunits.

Bruce Allen
Bruce Allen
Joined: 15 Oct 04
Posts: 958
Credit: 170,849,008
RAC: 0

Gun Shy

Quote:

Bruce; Here's the cleanup report: Box 202106 went daily quota of one at 5pm CDT today, suffering from h1_0078. It has 6+ WU's left. I think I was able to delete the file, but the server hasn't got a clue how to update it to health. Box 98411 suffers from h1_0101.5 and h1_0417.0, I was able to delete these nasties, but the WU's remain. Box 211430 is infected with h1_0441.5 and h1_0073.5. Box 102573, running version 4.45, carries two WU's from h1_0443 which I have set to aborted. Box 61409 suffers with h1_0430.0. I deleted the file but the 4 WU's remain in my que. Bruce, I am giving the project a full pull, stay away from the console and educate the freshman volunteers. It's tough managing a dozen+ machines on a diet of whoopsies.

Regards-tweakster

I've again reset the quotas for all machines that got h1_ workunits. I'll do this at least a few times per day over the next few days.

Bruce

Comment viewing options

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