EM3 problem

[MikeTimbers]

On one of my systems, EM3 insists on me being on loop 26 of 100 when it is actually on 4 and recently moved to 5. EM3 has now been stuck for what appears to be close to 48 hours! The top progress bar moves happily through to 100 but the bottom one refuses to budge.

Any ideas? I tried deleting the client from the EM3 config and re-creating it, I installed EM3 into a new directory, can't think of anything else to try.

The FAH client is working normally, BTW.

[pelligrini]

I haven't got a clue. Allthough, I've had that happen before.

You might try running the client with a -oneunit switch and then when it's done, delete all the files in the FAH directory keeping the client and the .cfg file and start it over. EMIII might not be reading the file it checks correctly.

[Bruce]

On one of my systems, EM3 insists on me being on loop 26 of 100 when it is actually on 4 and recently moved to 5. EM3 has now been stuck for what appears to be close to 48 hours! The top progress bar moves happily through to 100 but the bottom one refuses to budge.

Any ideas? I tried deleting the client from the EM3 config and re-creating it, I installed EM3 into a new directory, can't think of anything else to try.

The FAH client is working normally, BTW.

TheWeatherMan has updated EMIII several times to try to fix this problem and I don't think the latest version still takes care of it.

Look in the WORK folder and you will find most files contain a sequence number such as *_01* or *_02* or whatever. In FAHlog, you'll also find a sequence number when the current WU started processing . . or you can get it from queueinfo. You should alwaysl find a bunch of files with the proper sequence number for the active WU. If you run deadlineless WUs in batch mode (aka minimize networking) you'll find wudata_0x.dat files for the next WUs to be processed. If a server is down, there will be a WUResults_0X.dat waiting to upload. You'll also find a couple of files without sequence numbers. All of those files are normal, and you shouldn't mess with them.

In rare instances, you'll find a bunch of leftover files from a previous WU, and they confuse EMIII. You can safely delete files with the wrong sequence number (other than wudata and wureslts!) and then restart EMIII.

EMIII also gets confused if you have strange network errors, and I've never been able to figure out how to identify and/or fix those problems.

[MikeTimbers]

I've now got that FAH directory restored onto a brand new install (new mobo/cpu) of Windows and it's working flawlessly so go figure. Weird but over.