• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

f@h smp client stops working

m1ldslide1

Platinum Member
I'm seeing this on both machines that I'm running the smp client. Suddenly f@h will shut itself down, displaying the output pasted below, and will display the same output every time I try to run the app. On the first machine I noticed it on, I was frustrated and let it go for a few weeks. I tried again this morning, and it said that the deadline for the WU's had expired, downloaded new work, and is off and running again. The second machine is currently experiencing the issue. Any suggestions???

Thanks!
mild

####

Note: Please read the license agreement (Folding@home-Win32-x86.exe -license).
urther
use of this software requires that you have read and accepted this agreement.

2 cores detected
If you see this twice, MPI is working
If you see this twice, MPI is working


Launch directory: C:\Program Files\f@h
Executable: C:\Program Files\f@h\Folding@home-Win32-x86.exe
Arguments: -smp -smp -verbosity 9 -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.

[20:44:00] - Ask before connecting: No
[20:44:00] - User name: m1ldslide1 (Team 198)
[20:44:00] - User ID: 30CAB5BA7B4DC171
[20:44:00] - Machine ID: 1
[20:44:00]
[20:44:01] Loaded queue successfully.
[20:44:01]
[20:44:01] + Processing work unit
[20:44:01] Work type a1 not eligible for variable processors
[20:44:01] - Autosending finished units... [20:44:01]
[20:44:01] Core required: FahCore_a1.exe
[20:44:01] Trying to send all finished work units
[20:44:01] + No unsent completed units remaining.
[20:44:01] - Autosend completed
[20:44:01] Core found.
[20:44:01] Using generic mpiexec calls
[20:44:01] Working on queue slot 03 [September 17 20:44:01 UTC]
[20:44:01] + Working ...
[20:44:01] - Calling 'mpiexec -np 4 -channel auto -host 127.0.0.1 FahCore_a1.ex
-dir work/ -suffix 03 -checkpoint 15 -forceasm -verbose -lifeline 2476 -versio
622'

[20:44:01]
[20:44:01] *------------------------------*
[20:44:01] Folding@Home Gromacs SMP Core
[20:44:01] Version 1.74 (March 10, 2007)
[20:44:01]
[20:44:01] Preparing to commence simulation
[20:44:01] - Ensuring status. Please wait.
[20:44:18] - Assembly optimizations manually forced on.
[20:44:18] - Not checking prior termination.
[20:44:18]
[20:44:18] Folding@home Core Shutdown: MISSING_WORK_FILES
[20:44:18] Finalizing output
[20:46:21] CoreStatus = 1 (1)
[20:46:21] Client-core communications error: ERROR 0x1
[20:46:21] This is a sign of more serious problems, shutting down.
 
They did a revision of the client that fixes your problem (I think)

You can download it here

All you do is stop your smp client, delete the existing .exe and put the new one in it's place (make a new shortcut with the same stuff as your original one if you used one)

Good Luck!

-Sid
 
Slightly odd. A few suggestions:
-You gave it the -smp flag twice. It seems to have ignored you, but take one out 🙂
-forceasm and -advmethods do not apply to the SMP client. Ditto above.
-If this is a Windows machine, your FAHCore_a1 is way out of date. Delete the file and let it download the newest one.

If you still have no luck, manually delete the \work directory and queue.dat to fully purge any possible corrupted work files.
 
Alright - thanks guys. I downloaded the new beta client, and deleted my old /work file and queue.dat and it seems to work. Foxery: I also deleted tha FAHCore_a1 file so that it could update, plus removed the -smp flag from my shortcut. I left the other parameters in place since I didn't want to do the -configonly again unless I needed to.

Seems to be crunching now!
 
Back
Top