• 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.

problem with EM

B

buckma

n00b
Joined
May 13, 2005
Messages
4
Has anyone ever experienced a problem where EM stops showing the progress of a WU on a box and refuse to update it until the client starts a new unit?

I've had this problem pretty consistently with a box that I monitor remotely (it doesn't say 'Possible Network Error,' it just says 'Status Unknown'), and I assumed that it was a network quirk of some sort. I have an open connection to that PC with a username that's authorized to access the FAH directory, and can't imagine what the problem could be, but I eventually just decided to ignore it. Things seem to correct themselves when the client gets a new WU...until it loses track again somehow.

But it just started doing the same thing for the local client...so I'm wondering if anyone has had this problem before since it doesn't seem to be a network problem. I dunno if LPerry checks this forum regularly anymore, but I wanted to post here before I bug him about it.
 
I had some problems at first with my first QMD core, it refused to update the status for ever, but finally did eventually, other than that thats the only real problems ive had.
 
I would try to check the logs to make sure the clients aren't having trouble with the WUs. I've had a problem where EM wouldn't update or update properly when a system had trouble with WUs. Sometimes it would go through a couple of new proteins before it would start updating. Some of the time it had a corrupted core with the client core communications error. I would look into seeing if there are any errors with the systems themselves.

 
Do you have the latest protien dat file on that box?
It will show that answer without it.

Good luck

 
EM has a mind of it's own for me. It constantly has trouble keeping the update of a couple of the 8 machines I monitoring with it now. It also has a mind of it's own for coming out of stealth mode.

It's free, so I can't complain.(much :p) I do wish it would only put one icon the the tray though, I hate that stupid lightbulb.
 
You can turn that lightbulb off....
I've not had any real problem with EMIII over the years... it just keeps getting better.... Larry does a great job identifying and fixing problems as they come up


Keep on Folding!! For the [H]orde!!

 
Yepper... I visit here several times nearly every day. ;)

As pointed out, the "Bulb" can be turned off in the options menu. It is there to visually alert you if you have EM minimized and/or the warning sounds turned off... but it doesn't have to be there if you don't like it.

The tracking issues... there are several problems. One of the biggest pains is something Stanford introduced and has "mostly" been fixed. They are supposed to adjust things in the next release. I have no idea when that will be, but since they are constantly working to improve their client I expect it will be sooner rather than later... I hope. :D

Many times the tracking issue occurs because the client can't communicate with the server when it finishes a work unit. When that happens, "left overs" ... files that are usually deleted when an upload occurs... start messing up the work folder. To fix this, you can clean out the work folder yourself. I don't do it for you as I might get some bullets flying my way if EM actually deleted something it wasn't supposed to. I debated about a "clean-up" button... I may still do that, but I would hate to be responsible for deleting files that may have been good. Most of the files in the work folder will have the same work number, 02, 03, etc. A few of them will be different than the majority... those few need to be removed. This "usually" fixes the issue... but, there are times when the client "forgets" to update files I look at. When that happens there is nothing to be done about it. It's a bug in the Client and they haven't been able to fix it... it's been there a long, long time.

Some people have issues with wireless networks... they are a problem at times. Since this usually doesn't occur with a hard wire, it isn't EM's problem. The connection gets lost for some odd reason. Remember, while wireless has been around a while, it has its own issues that only appear when it is required to be there 100% of the time, just like a wire would be... Things are getting better, but the connection is still lost every so often and EM is designed to let you know a network problem exists. This is mainly due to the fact that something has usually gone wrong if communication with that computer is lost.

I continue to try and improve this program and fix issues as they come up. The "quirks" that currently exist can't easily be fixed without some help from the client. Remember that EM is complex. No other program does as many things or gives you as much info as EM in a single package. While at times I wish it wasn't as bloated as it is, I would be hard pressed to decide what features to remove as most are useful to somebody out there. ;)
 
Thanks for the info Larry! Since EM's development has kind of slowed down over the last couple of years and we don't get daily or weekly updates on its progress, it's kind of easy for people to forget that many of the "problems" with it are a result of shortcomings in the client. For most of us, the client problems aren't an issue, but this gives you a little insight into the issues that developers like Larry have to deal with every day.
 
Thanks for pointing out hte lightbulb can be turned off. I guess I just missed the option when I looked though it. The main thing I don't like about it is the space it takes up. I like a minimal amount of icons in my tray. It would be nice though if the microscope icon changed colors instead of the lightbulb though. I have been running EM3 in stealth mode because I disliked the 2 icons it was using, I may stop using steath mode nwo that it's turned off.

And thanks for the program Larry. I may bitch about it at times, but it is really helpful in keeping track of all my boxen. There is one machine that always has a problem tracking, and I can't figure out why. It's setup the same as all my other machines, and no wifi here, it's all copper. Oh well.

Also, another suggestion while I'm thinking about it. Allow the window to be resized and show more machines. I currently monitor 8 machines, and like the layout of the 7 machine view, and have to scroll to see the last one. I'm about to add another 4 machines to monitor as well, and the 13 machine view is a bit cramped.
 
I did forget to mention one issue that many have run into...
The OS sometimes has a default time limit as to how long someone can be logged on.
Windows 2000 is the main culprit in this issue. But, since you can limit this time, you need to check that feature. I suspect that is the real problem... the OS just disconnects and won't allow an automatic reconnect. ;)

I've got a list of things people would like to see. More clients in the window is the main one. I haven't done that as resizing the windows, skins, etc. is a pain because the original design called for 4 clients... everything after that has been a modification. EM is over 4 years old... I'd like to rewrite it, but time isn't something I have a lot of. ;)

Expect to see a small update soon. :)
 
Thanks for the replies LPerry. Deleting the left-over files did the trick for my troublesome clients.

Thanks for 3.1.7 :)
 
You must log in or register to reply here.
Back
Top