• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

I found a very annoying pattern in F@H

Markfw

Markfw

Moderator Emeritus, Elite Member
OK, so over the last 2 weeks (maybe more) I have found this pattern. I am getting a lot of EUE's on machines that have been stable for months. Now here is the pattern: It will have an EUE' 3 times in a row at the same place (% done) ON THE SAME WU. Then when I delete the work folder, and the queue after the 3rd time, it will say no work to do, then it will get one. About 1/2 to 1/3 the WU's will actually complete normally. So on the same machine, it might get an "EUE unit" I will call it, then after 3 times, will process one completely normally, maybe 2 units. Then get another bad one 3 times.

This has happened on every computer in my house, and now that I know the pattern, after the first EUE, I delete, restart right after being given the unit, until the 3rd time, then I get a good one. The downside, is its a lot of maintenance time, and also uses up a lot of cycles. I think these are known bad units, the stanford is feeding us, wanting the 2nd or 3rd user to confirm its bad. My PPD has dropped like a rock, and its really annoying.
 
Beta testing 😕

The old SMP client I am using, 5.something, does not send information to Stanford about an EUE, it just deletes.

I bet the newer clients still do this too. If so then they have no way of finding out about bad WUs and they continue to be sent out. As the project gets closer to the end there will only be bad WUs 😱

As to the three times in a row thing - this is normal. The server keeps a record of the WU sent to the client and if results for a WU are not sent in then it will resend the same WU. There must be a time interval taken into consideration though it seems because I can get different WUs for the same MachineID (with regular client) after a day or so (although this might just be some servers because sometimes I can get a repeat WU after more than a day - I keep track of WU size for every WU I get so I don't get multiples of same WU for sneakernet machines)
 
I am having less EUEs now, but when I do see one I delete the work folder and queue.dat then restart it. If I get the same one again, I stop the SMP client immediately and delete the work folder and queue.dat file again. I repeat this unitl I get a new work unit. This takes about 15 minutes and is very annoying, but :beer: helps.

In the folding forum, in the list of known bugs they acknowledge the failure of the 6.22 client to respond properly to EUEs. Other threads talk about getting the same one 3 times before getting a new one (I have also read 5 times, but it looks like 3 here).

So the good news is that it's not just you and also they 'are working on it'.

:beer:

-Sid
 
Retrying 3 times is technically correct, (5.9x sometimes did this,) but the client is supposed to inform Stanford when it ultimately fails, and is currently not doing so. (5.9x sometimes did, sometimes didn't) It's on the To-Do list... 🙁
 
You must log in or register to reply here.
Back
Top