• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

EMIII problem

K

Kugar

Weaksauce
Joined
Mar 28, 2002
Messages
113
I use EMIII to monitor my boxes.
For one of my boxes, the magenta Frames Completed bar has been stuck at 2 of 100 for days now. Yet when I check that box's log, it appears to be progressing normally. The green current frame progress bar in EMIII looks fine, and the time per frame matches the log file. Also EMIII shows that box's work unit to be a 600 pointer but I don't believe it is correct (the time per frame is way too short for a 600 pointer).

One more thing. I noticed that box had an early end unit after 2 frames a couple days ago. So it aborted and got a new work unit. It has completed a couple WU since then. The EMIII problem must be related.

I deleted the box from EMIII and readded it, but there was no change. Any ideas on how to get EMIII to properly monitor the box?

 
Odd.

I just checked my EMIII and I seem to have a similar problem with a 600 pointer on my main boxen. It suddenly does not seem to be monitoring at al.. Maybe Lperry or others will notice this thread an see what can be done.

 
Kugar said:
I use EMIII to monitor my boxes.
For one of my boxes, the magenta Frames Completed bar has been stuck at 2 of 100 for days now. Yet when I check that box's log, it appears to be progressing normally. The green current frame progress bar in EMIII looks fine, and the time per frame matches the log file. Also EMIII shows that box's work unit to be a 600 pointer but I don't believe it is correct (the time per frame is way too short for a 600 pointer).

One more thing. I noticed that box had an early end unit after 2 frames a couple days ago. So it aborted and got a new work unit. It has completed a couple WU since then. The EMIII problem must be related.

I deleted the box from EMIII and readded it, but there was no change. Any ideas on how to get EMIII to properly monitor the box?

Click to expand...

You need to go into the work folder for the machine that is not updating. In there you will see different files that mostly end in 01, 02, 03 or something like that. There should only be one number in there such as 01 and I'd bet there is more than one. You need to find out which one is the current work unit and delete all the others that end in a different number. If the 05 protein is the one you are currently working on on that machine you will need to remove all the other ones which will probably be 04 or possibly 03. Once the extra files are gone, EMIII should begin to update normally again. This happens when the folding client encounters a problem with a protein and it ends early and it doesn't clean out that directory properly. Because of this, EMIII is confused as to what it's supposed to monitor from that box.

 
SmokeRngs said:
You need to find out which one is the current work unit and delete all the others that end in a different number.
Click to expand...

How can you tell which number is the current unit and which is junk?


 
If you go into the EM options menu and select the box with the problem, and then press the queue.dat file info button, EM will display the number of the current work unit. You can use that info to correct the garbage problem that sometimes causes EM to sit still for a work unit or two...
 
Yes, this has been happening for me too. I run 4 different processes, and when I have to stop them manually (CTRL-C) via the CMD windows, it seems that EMIII has issues when trying to restart them.

The fix for me is simple -- as soon as it errors out (you'll hear some audible alert) -- then just close out EMIII and relaunch it. It always seems to re-sync fine after that.
 
Normally when this sorta thing happens, I close EMIII and then re-open it, once it finishes a stage, it seems to be fine again.
 
You must log in or register to reply here.
Back
Top