Anyone have instability with new 6.22 beta2 client?

[douirc]

I was folding for weeks on the previous SMP version, OCCT stable, prime stable and everything else stable, but now the new beta2 is giving me problems and I don't know why. It simply returns the error that instability has been found and shutting down the core. I don't understand why I could fold on the previous SMP client flawlessly and the new one is giving me problems, unless of course, that's why they call it a BETA?!

anyone else having stability problems with the new BETA2?

[smegenstein]

does it juts come up with a window saying:"Folding@home has run into a serious error running the core. and will shutdown."

And in the SMP CMD Window say:
Folding@home COre Shutdown: MISSING_WORK_FILES
Finalizing output
CoureStatus = 1 <1>
Client-core communications error: ERROR0x1
This is a sign of a more serious problem shutting down


if so...I HAS THAT PROBLEM...finished my first WU on the SMP client, and then it came up with that and wont boot back up again

[douirc]

yeah, i think that's exactly what i get. i did a little looking on the folding forum and apparently it's a common problem:

http://foldingforum.org/viewtopic.php?f=46&t=4353

this really sucks of course, because we're wasting time folding on a buggy release. wish the previous version still worked. whenever i try running it, it says the beta expired or something, forcing me to upgrade to 6.22.

someone from folding is working on a fix, and I guess there's a new core coming out (A2)?

[smegenstein]

Anything I can do in the meantime?

[douirc]

apparently they recognize they screwed up and are now offering the previous versions again with an extended expiration time.

http://folding.typepad.com/news/2008...mp-client.html

I went back to version 5.91 and it's running fine.

[smegenstein]

I did the same, just put the .exe in the same folder and changed the shortcut path, had to remove -smp from the command line thingy in the shortcut though..
also looks like i lost the WU that i was working on, was meant to give me ~1950 points, was at 100%, didn't get any points for it though because of the rror it got deleted QQ

[AaronNunley]

The only problem I am experiencing with the new client is the lower PPD from it. On my stcok quad rig, I get ~800 PPD I'll look into installing the older client tomorrow.

[KillerBeagle]

Geez, I thought I was the only one having problems. About half of the WU's I have gotten since updating the client have gotten errors and died. I switched back to 5.91 and it was able to pick up and complete work that the newer client died on.

[smegenstein]

Lucky for you!
Mine just decided to delete the work files when i rolled back to 5.91

[Librarian]

6.22 has same story for me. I dumped it as well. My 5.91 is also unstable (still trying to figure that one out)...I hope they get 6.22 patched soon.

[AaronNunley]

I haven't had a dumped WU or anything like that, yet. Just horrible PPD from both machines running the 6.22.

[jevans64]

I have been seeing A LOT more EUEs with 6.22. I would normally use qfix to repair the queue file and send the partial BUT qfix doesn't work with 6.22. Qfix hasn't been updated since 2005, so I doubt a new version is in the works.

I am having to delete the Work directory, queue.dat, and unitinfo in order to get the client to start back up. You'll STILL get the same WU so you'll have to stop the client and repeat the delete process THREE times before you pick up a new WU.

On the third restart, you will get this message...

[xx : xx : xx] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[xx : xx : xx] - Attempt #1 to get work failed, and no other work to do. Waiting before retry.

... then you SHOULD get a new WU to work on.

[chiefish]

I have both problems going on it looks like, i know my ppd has dropped since using the new one and i also noticed that i have turned in w/u that are worth 0 , i have checked my logs and dont see any EUEs going on but somthings happening. Not sure what the problem is but ill hang in there until they release somthing better i guess

[KillerBeagle]

Originally Posted by jevans64

I am having to delete the Work directory, queue.dat, and unitinfo in order to get the client to start back up. You'll STILL get the same WU so you'll have to stop the client and repeat the delete process THREE times before you pick up a new WU.

Two slightly quicker ways to get a new WU, after deleting the files you mentioned:
1. Change your machine ID to one that hasn't recently been used on that system, or
2. Delete the FAH registry key HKEY_LOCAL_MACHINE\SOFTWARE\PandeGroup\Folding@hom e

[FunkZ]

Originally Posted by AaronNunley

The only problem I am experiencing with the new client is the lower PPD from it.

Same here, running fine but down maybe 5-10% from the old version.

[dblind1]

I'm guess i'm lucky. I'm using the mpich version and I had no drop in PPD and it seems to run fairly stable. I screwed up a few times and didn't know to use the -smp flag, but I got it fixed and I'm making 1200 ish points on 2 cores of my stock quad.

[onewecallgod]

I've been having problems as well. I'm not sure if it was due to the new client or not, but for the last week I've been having 2665s end early, always at 60%.

[xomcat]

****! I wish I would have spotted this thread sooner! I've, basically, had five rigs down this week. WU's finished wouldn't send and "Unstable Machine" errors on rigs that were productive before (including running the new client also). Between the power outages and fubared clients, production is way down.