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

points don't look right

G

gigglebyte

2[H]4U
Joined
Jan 18, 2001
Messages
3,814
ok....I have a question about the kind of points I should be seeing from my system. I just got this box up and its a C2D E6550 with 2 Gig of Ram running XP SP2. I got F@H on it earlier this week and when I checked my stats I see I only have 1800 for the week?!? I see people should be getting that in a day....any ideas??
 
Are you running the SMP client, or the regular clients? That's what I can think of right off my head...

 
I am running the SMP client and just to give you an idea of how slow this is....in the last hour, it hasn't moved even 1% and I am not really even doing anything on the system right now.....just general browsing
 
Something is definitely wrong... my P4 2g boxes with 256m running the standard client are producing faster than that....

What work unit do you have? Maybe kill it and start over? That's all I can think of.....

 
how can I tell what work unit I have?? I am looking in the console and I see project 2653 (Run 3, Clone 117, Gen 46) it does detect 2 cores and looking at the old log file, it looks like it was processing at about 1% per 19-20 minutes and even that seems slow...no I am not running a monitoring program but will be getting one (had one for my Macs) and how do I tell if big WUs are enabled? I am not used to using the console version and have always done the graphical one
 
now this was very odd...I checked task manager and it was showing that mpiexec was running even after I quit the app...on restart I checked task manager again and there are 2 fah.exes running and 4 FahCore_a1.exe running?? I could see two but not four?!? and each one of the FahCores are bouncing between 11-25% of the CPU
 
gigglebyte said:
now this was very odd...I checked task manager and it was showing that mpiexec was running even after I quit the app...on restart I checked task manager again and there are 2 fah.exes running and 4 FahCore_a1.exe running?? I could see two but not four?!? and each one of the FahCores are bouncing between 11-25% of the CPU
Click to expand...

That's is correct because SMP clients has four cores and you only got two so yeah that makes sense. However, the two fah.exe doesn't...
 
You should only see one fah.exe per SMP client.
 
Yep 4 core .exe's, only 1 f@h instance - somethings wrong there. But IMHO 19 mins isn't bad, if that's what you frame times actually are. 4 threads because it's meant for quad core machines (at least while in "beta"), not dual...But works just fine for many people w/ dual rigs.

e2140 @ 2944 various bench readings in F@HMon:

Min. Time / Frame : 17mn 27s - 1452.38 ppd
Avg. Time / Frame : 24mn 05s - 1052.35 ppd
Cur. Time / Frame : 18mn 18s - 1384.92 ppd
R3F. Time / Frame : 18mn 25s - 1376.14 ppd
Eff. Time / Frame : 24mn 12s - 1047.27 ppd

My actual average, despite the log is about 19 mins though.

[edit] Come to think of it.. I have an issue sometimes where I have to MANUALLY shut down the F@H process (well X out), because it gets stuck (quite often I might add!) @ the end - "will end MPI now" or whatever... Which is REALLY annoying, since if I finish a unit right after going to bed, and it hangs there's ~6-8 hours possibly that it's sitting doing NOTHING.
 
just checked task mgr again and it still shows 2 fah.exe's and its now been 28 minutes and still no movement :(
 
gigglebyte said:
just checked task mgr again and it still shows 2 fah.exe's and its now been 28 minutes and still no movement :(
Click to expand...
Therein must lie your problem. Shut down the client with Contrl-C. Wait until all the Fahcore.exe's have stopped processing in Task Manager. Reboot the system and start the client again.
 
ok...quit the client but I still see one fah.exe sitting out there?? shouldn't that have shut down as well? (I will reboot in just a minute...have a couple things I have to save out
 
Another thought...Is the system 100% stable/doing overclocking/etc?

If I manually close the F@H client, no problems on restart... But if I say have a BSOD/freeze, on restart the client restarts from 0...I've lost plenty of WU/points return due to that :(...Sucks when you hit 80%+ just to start all over.

[edit] It should, but it sounds like somethings wrong...Did you perhaps have a failed install @ 1st, and have to do it again? I had some wierd things happen when I first tried the SMP client on my Opteron rig - enough so that I gave up on it..Tried again when I went S775 and been fine ever since.

[edit again] Coffee starting to kick in...I think I had a similar issue at one point... I think I set the client up for SYSTEM SERVICE (and forgot about it; not supported as was in regular client btw), and either manually started the client or put the client [shortcut] into startup programs folder...Which led to 2 clients fighting for the 4 threads....And folding going nowhere. I think I ended up re-installing, whatever the case (whether it was 2 installs or I was starting client 2x somwhow).
 
no issues installing and I actually followed the directions...as for OC...I am not doing that on this rig...its pleanty fast enough for me ;) so everything is stock here....I did reboot and checked task manager and even before I launch F@H its showing fah.exe running under SYSTEM and its memory usage is 2,168k which is what I remember one of them being before the reboot, but oddly enough its not using any CPU

edit...

I did get into the original FAHlog file and found this

[02:24:01] Work directory not found. Creating...
[02:24:01] Could not open work queue, generating new queue...
[02:24:01] - Preparing to get new work unit...
[02:24:01] + Attempting to get work packet
[02:24:01] - Connecting to assignment server
[02:24:01] - Successful: assigned to (171.64.65.64).
[02:24:01] + News From Folding@Home: Welcome to Folding@Home
[02:24:01] Loaded queue successfully.
[02:24:06] + Closed connections
[02:24:06]
[02:24:06] + Processing work unit
[02:24:06] Core required: FahCore_a1.exe
[02:24:06] Core not found.
[02:24:06] - Core is not present or corrupted.
[02:24:06] - Attempting to download new core...
[02:24:06] + Downloading new core: FahCore_a1.exe
 
gigglebyte said:
ok...quit the client but I still see one fah.exe sitting out there?? shouldn't that have shut down as well?
Click to expand...
It won't unless you terminate the process manually. It has happened to me before, which is why I recommend a reboot to be certain no extraneous processes are still running. Perhaps you should save the WU work progress as well, if you haven't already restarted the system.
 
gigglebyte said:
I did reboot and checked task manager and even before I launch F@H its showing fah.exe running under SYSTEM and its memory usage is 2,168k which is what I remember one of them being before the reboot, but oddly enough its not using any CPU
Click to expand...
Seems like something has autostarted the client's executable. You don't have F@H running as a service?

End the process and start the client and see what happens. Make certain that mpiexec.exe is running though or you might lose your work.
 
well I stopped that fah.exe and restarted the app and I now only have one fah running ...now is it odd to have mpiexec taking 25-30% of the CPU? and how can I tell if I have FAH running as a service? know it isn't in the startups but not sure about service
 
gigglebyte said:
well I stopped that fah.exe and restarted the app and I now only have one fah running ...now is it odd to have mpiexec taking 25-30% of the CPU? and how can I tell if I have FAH running as a service? know it isn't in the startups but not sure about service
Click to expand...
The possibility of having the SMP client running as a service was was only a guess on my part. I have never installed nor is it recommended to do so. Thus, I don't know what it might look like. You will need to check in Control Panel>Administration Tools>Services. If it's installed as a service, it will be visible there. Mpiexec.exe does not use any CPU processing power on any of my systems. I don't understand why it's doing that on yours. Odd...

If there's no resolution with the advices provided in this thread, a reinstall of the client should be then attempted. That is a last resort though.
 
If you installed as a service and didnt configure it properly with the batch file, maybe mpiexec is trying to initiate, but doesnt have the credentials to do so.

If you are going to run as a service there are a few extra steps to ensure it operates properly...

Such as, run the batch file, enter username/password for the service to run with.

Then you have to modify the service to log in with the same username/password.

Lastly, you should run regedit and add -forceasm to the Image Path for the service.
 
I did follow the directions and filled out everything like I should have but for some reason I think it had an issue with my user name and password...I went into services and checked its settings and added my admin user in the log on section...for some reason it was set to local system account...after reboot it looks like it is running properly....one fah.exe, four FahCore's one mpiexec and only the FahCore's are using CPU time!!

now the question is since it is the console version, other than running FahMon (or similar) how do I see what it is doing because the console doesn't come up on reboot
 
gigglebyte said:
I did follow the directions and filled out everything like I should have but for some reason I think it had an issue with my user name and password...I went into services and checked its settings and added my admin user in the log on section...for some reason it was set to local system account...after reboot it looks like it is running properly....one fah.exe, four FahCore's one mpiexec and only the FahCore's are using CPU time!!

now the question is since it is the console version, other than running FahMon (or similar) how do I see what it is doing because the console doesn't come up on reboot
Click to expand...

WEll you could go to the folder and look at the fah log files there. Simple as that... And since you are running it as service, the console will not show up at all, just running in the background.
 
Jon855 said:
WEll you could go to the folder and look at the fah log files there. Simple as that... And since you are running it as service, the console will not show up at all, just running in the background.
Click to expand...

Yup, that's how you do it. Also if you ever change your password, you'll need to change the password in the service and reinstall MPI with your new password.
 
ok...I can tell its running fine now...I have FahMon looking at it and it has already gone up 2% since I started it!! thanks for all your help everybody...now for a side question...I loaded my Macbook up with the SMP version but I saw that it said its beta was going to stop running on April 1st 2007 ?? should I even try to run that then?
 
Yeah, run it... Replacing the main fah file itself won't be hard, go ahead and run it...
 
With the Mac version, you can run the 6.0 client and it is the easiest one to install and setup. Make sure you download the right client because April 1st, 2007 was almost 9 months ago.
 
ND40oz said:
With the Mac version, you can run the 6.0 client and it is the easiest one to install and setup. Make sure you download the right client because April 1st, 2007 was almost 9 months ago.
Click to expand...

duh...I know its that old ;) ...but that is the only SMP client they have for OSX and when you look at the download page...there are TWO listed for Intel Macs and both are listed as beta...I just wanted to make sure they weren't going to screw anything up
 
So, it was running as a service? It explains why there was two executables then. Thought it might have been that.
 
APOLLO said:
So, it was running as a service? It explains why there was two executables then. Thought it might have been that.
Click to expand...

Yeah, that's why you need to follow the install instructions to the letter. If you run it with the -config only switch, it shouldn't start running after going through the config. Then you can reboot and let the service take off like normal. Just remember, running as a service is not supported by Stanford, so don't ask for help over on the official forums.
 
You must log in or register to reply here.
Back
Top