• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

WHy does FAH #3 keep shutting off??

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Shelnutt2

Overclockers Team Content Editor
Joined
Jun 17, 2005
Location
/home/
I am running the quad install on my dual xeons. Just after I did the U wire mod and OCed a little more now the 3rd instance of FAH keeps shutting down. I've primed and superpied, It is a stable system. Why does the third instance keep turning off?
 
some WUs are sensative to OCing. Even if a system seems stable and possibly tests the same way, there may be issues. Pretty much a reason some people use the F@H programs to test the final stability of their rigs.
My guess is to try and get a different WU to work on for that one and see if it works better. If not, further testing and adjustments may be necessary before the work can be completed.
 
What does the log for that instance say is happening?
Does the service remain running or is it turning off? Could it be set to manual and just not be restarting on bootup?
 
the service remains runnin. I checked everything and I even went into the services and manually restarted it by stoping then starting it. It starts up but then shuts off. You can see in the task manager that it has shut down. The log for it jsut say start blah blah blah..and then is says completed ....15%
 
Sometimes you get a message like "Client Died" which is what it sounds like is happening.
 
Here is yesterdays log file.
--- Opening Log file [December 15 10:35:51]


# Windows Console Edition #####################################################
###############################################################################

Folding@Home Client Version 5.02

http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Program Files\FAH\FAH3
Executable: C:\Program Files\FAH\FAH3\FAH502-Console.exe
Arguments: -local -service -advmethods -forceasm

Warning:
By using the -forceasm flag, you are overriding
safeguards in the program. If you did not intend to
do this, please restart the program without -forceasm.
If work units are not completing fully (and particularly
if your machine is overclocked), then please discontinue
use of the flag.

[10:35:51] - Ask before connecting: No
[10:35:51] - User name: Shelnutt2 (Team 32)
[10:35:51] - User ID: 39F75E594380B074
[10:35:51] - Machine ID: 3
[10:35:51]

A potential conflict was detected:

Process 596 is currently running and may also be a client with Mach. ID 3.
Program will now exit. Upon restart, this check will not be done --
you may wish to check that no client is currently running in
C:\Program Files\FAH\FAH3 before restarting.

Here is todays:

--- Opening Log file [December 16 17:39:44]


# Windows Console Edition #####################################################
###############################################################################

Folding@Home Client Version 5.02

http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Program Files\FAH\FAH3
Executable: C:\Program Files\FAH\FAH3\FAH502-Console.exe
Arguments: -local -service -advmethods -forceasm

Warning:
By using the -forceasm flag, you are overriding
safeguards in the program. If you did not intend to
do this, please restart the program without -forceasm.
If work units are not completing fully (and particularly
if your machine is overclocked), then please discontinue
use of the flag.

[17:39:44] - Ask before connecting: No
[17:39:44] - User name: Shelnutt2 (Team 32)
[17:39:44] - User ID: 39F75E594380B074
[17:39:44] - Machine ID: 3
[17:39:44]
[17:39:44] Loaded queue successfully.
[17:39:44] + Benchmarking ...
[17:39:48]
[17:39:48] + Processing work unit
[17:39:48] Core required: FahCore_7a.exe
[17:39:48] Core found.
[17:39:48] Working on Unit 04 [December 16 17:39:48]
[17:39:48] + Working ...
[17:39:48]
[17:39:48] *------------------------------*
[17:39:48] Folding@Home GB Gromacs Core
[17:39:48] Version 1.86 (August 28, 2005)
[17:39:48]
[17:39:48] Preparing to commence simulation
[17:39:48] - Assembly optimizations manually forced on.
[17:39:48] - Not checking prior termination.
[17:39:49] - Expanded 66355 -> 359381 (decompressed 541.6 percent)
[17:39:49]
[17:39:49] Project: 2077 (Run 15, Clone 6, Gen 0)
[17:39:49]
[17:39:49] Assembly optimizations on if available.
[17:39:49] Entering M.D.
[17:40:10] (Starting from checkpoint)
[17:40:10] Protein: p2077_Ab Initio Protein Random Structure
[17:40:10]
[17:40:11] Writing local files
[17:40:11] GB activated
[17:40:11] Completed 473792 out of 3000000 steps (16)
[17:40:11] Extra SSE boost OK.
 
Can anyone help? Now FAH#1 is doing it. I tried deleting the work folder but same thing happens.




--- Opening Log file [December 20 01:28:59]


# Windows Console Edition #####################################################
###############################################################################

Folding@Home Client Version 5.02

http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Program Files\FAH\FAH1
Executable: C:\Program Files\FAH\FAH1\FAH502-Console.exe
Arguments: -local -service -advmethods -forceasm

Warning:
By using the -forceasm flag, you are overriding
safeguards in the program. If you did not intend to
do this, please restart the program without -forceasm.
If work units are not completing fully (and particularly
if your machine is overclocked), then please discontinue
use of the flag.

[01:28:59] - Ask before connecting: No
[01:28:59] - User name: Shelnutt2 (Team 32)
[01:28:59] - User ID: 39F75E594380B074
[01:28:59] - Machine ID: 1
[01:28:59]

A potential conflict was detected:

Process 520 is currently running and may also be a client with Mach. ID 1.
Program will now exit. Upon restart, this check will not be done --
you may wish to check that no client is currently running in
C:\Program Files\FAH\FAH1 before restarting.
 
what it is saying is that you are trying to run more than 1 client with the "Machine ID: 1 " or 3 so check you config files and make sure that they are all different or the clients may be running as a service and that is the reason you are getting the error. I know it happens to me when i try to run the same client more than 1 time
 
Also, make sure the service is stopped before editing the client.cfg ... it rewrites the file with whatever it started with.
 
There is a bug (sort of) in FAH that mainifests itsself when running Windows XP after an improper shutdown of the client. There is a "lock" file that doesn't get deleted and causes the client to beleive the instance is already running. There has yet to be an explanation as to why this happens only sometimes after an improper shutdown of the client.

In my experience, about one in ten instances will wind up conflicted after a power failure. THe real question is why is your machine crashing? Or how are you shutting down FAH? What caused instance 1 to restart on [December 20 01:28:59]. My guess is there is no sigterm message in the log on the shutdown prior to this restart.
 
#2 is shutting off on me now. I have deleted the work folders three times and I even went and deleted all the cores to see if that was the problem. It is set to service in the registry. Help this is the one that folds QMDs.

Here is the log

--- Opening Log file [January 26 10:34:44]


# Windows Console Edition #####################################################
###############################################################################

Folding@Home Client Version 5.02

http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:program FilesFAHFAH2
Executable: C:program FilesFAHFAH2FAH502-Console.exe
Arguments: -local -service -forceasm -advmethods

Warning:
By using the -forceasm flag, you are overriding
safeguards in the program. If you did not intend to
do this, please restart the program without -forceasm.
If work units are not completing fully (and particularly
if your machine is overclocked), then please discontinue
use of the flag.

[10:34:44] - Ask before connecting: No
[10:34:44] - User name: Shelnutt2 (Team 32)
[10:34:44] - User ID: 3D2038E853E7A7B9
[10:34:44] - Machine ID: 1
[10:34:44]

A potential conflict was detected:

Process 828 is currently running and may also be a client with Mach. ID 1.
Program will now exit. Upon restart, this check will not be done --
you may wish to check that no client is currently running in
C:program FilesFAHFAH1 before restarting.



--- Opening Log file [January 27 10:50:42]


# Windows Console Edition #####################################################
###############################################################################

Folding@Home Client Version 5.02

http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:program FilesFAHFAH2
Executable: C:program FilesFAHFAH2FAH502-Console.exe
Arguments: -local -service -forceasm -advmethods

Warning:
By using the -forceasm flag, you are overriding
safeguards in the program. If you did not intend to
do this, please restart the program without -forceasm.
If work units are not completing fully (and particularly
if your machine is overclocked), then please discontinue
use of the flag.

[10:50:42] - Ask before connecting: No
[10:50:42] - User name: Shelnutt2 (Team 32)
[10:50:42] - User ID: 3D2038E853E7A7B9
[10:50:42] - Machine ID: 1
[10:50:42]

A potential conflict was detected:

Process 304 is currently running and may also be a client with Mach. ID 1.
Program will now exit. Upon restart, this check will not be done --
you may wish to check that no client is currently running in
C:program FilesFAHFAH1 before restarting.
 
are you sure your machine id's are all unique? and are between 1 and 8?

and that each instance has the -local flag set?
 
it looks like both your #1 and #2 clients were both set with a machine id of 1...that's one problem... as for the 3rd and 4th, they might both be running 3...try reinstalling FAH with wedo's oneclick.
 
pscout said:
are you sure your machine id's are all unique? and are between 1 and 8?

and that each instance has the -local flag set?

Ok, fold#2 id was set to id #1. I changed it, and have restarted it still does not start. there is no work folder to delete.

All instances do have the flag "-local"
 
did you try reinstalling FAH again? and now that i think of it, with wedo's you'd have to get one of the non-advmethods ones and manually turn on advmethods on one instance.
 
the garynator said:
did you try reinstalling FAH again? and now that i think of it, with wedo's you'd have to get one of the non-advmethods ones and manually turn on advmethods on one instance.

No I haven't reinstalled...but I can use the advmethods one click? I want to run advmethods on all of them. That gives me the most PPD. Just only on teh second instance I turn on big packets. Or do you recommend using no-advmethods?
 
I'll be darned. I haven't restart my computer or FAH or reinstalled it (been watching Forest Gump on TNT). Here it is my computer's been on an hour and #2 starts back up. It works now and I guess that all that matters.
 
Back