Page 1 of 1

Welcome To The F@H Support Forum

Posted: Wed Mar 19, 2014 9:41 pm
by PantherX
Welcome to the Official F@H Support Forum!
Image

Thank you for visiting this site. Please find below sections of helpful information that will help you understand more about the F@H Software and how you can contribution to the F@H Community :D

Below is an index to help you navigate this topic with ease:

1 - Getting Help With Folding@Home - An introduction to the F@H support system

2 - Temporary Restrictions For New Members - Newly registered members may find this useful

3 - Introduction To Common F@H Jargon - Brief overview of vocabulary specific to the F@H Community

4 - Getting Started With F@H (Basic) - A quick-start guide to help you fold your first WU!

5 - Getting Started With F@H (Advanced) - Few pointers as you reach the next chapter in your folding journey

6 - How To Post A Log File (Windows) - Instructions on how to post a log file from the F@H Client here on the Forum

7 - How To Post A Log File (Linux) - Instructions on how to post a log file from the F@H Client here on the Forum

8 - How To Post A Log File (macOS) - Instructions on how to post a log file from the F@H Client here on the Forum

9 - Generic Troubleshooting Tips - Advise for common issues for F@H Client

10 - Additional Links - Other articles to learn more about the F@H Community and F@H Project

1 - Getting Help With Folding@Home

Posted: Sun Apr 19, 2020 12:09 am
by PantherX
  • 1 - Getting Help With Folding@Home
Some of you may have found this Forum because you encountered an issue when attempting to run the F@H Client, while others want to learn more about the F@H Project. Either way, there are a number of resources allowing for self-helping and self-learning which you can avail:
  1. You can start by searching this Forum to see if someone else has already reported the same problem. If so, you can try the suggested solutions (if applicable).
  2. You could try reading the FAQs to see if your question is answered.
We're happy to help you with any kind of F@H related problems. Most of the time we'll need information from you to help diagnose your problem. The log is a very vital source of information when it comes to troubleshooting the F@H Clients. The first ~100 lines of the log shows essential information about your system and any settings that the F@H Client has been configured for. Secondly, you should also include portions of the log which shows error messages especially the first time it happens. Do note that the forum has a limit of 60,000 characters (including spaces) so you can trim off the progress reported from 2& to 99%. For more details, please see How To Post A Log File (details below).

For the registered Forum Members, please note that our General Policies can be found here.

2 - Temporary Restrictions For New Members

Posted: Sun Apr 19, 2020 12:09 am
by PantherX
  • 2 - Temporary Restrictions For New Members
Please note that if you have recently joined this Forum, you may not be able to use some of the Forums' features initially. Our anti-spam policy sets a threshold just high enough that a spam-bot is unlikely to reach, while the Donors can, provided they are around long enough. Some of the features that you initially can't use are:
  1. Can't post URLs
  2. Can't quote another user
By participating normally, these temporary restrictions will be automatically removed :)

3 - Introduction To Common F@H Jargon

Posted: Sun Apr 19, 2020 12:10 am
by PantherX
  • 3 - Introduction To Common F@H Jargon
While browsing this Forum, you may come across some unusual acronyms which are commonly used by F@H Donors. Below is a list of commonly used acronyms and jargons:

WU - Work Unit is a small time-slice of protein processing that is downloaded by your F@H Client from the appropriate Server. Your system will process it and once it finishes folding, will upload the result to the Server and will request another WU unless the F@H Client is set to Finish.
Note: The duration to process this WU will vary from few hours to few days depending on the type of WU, F@H Client, system usage and several other factors. You will receive credits for a WU once it is successfully uploaded to the Servers and the Official Stats are updated (happens every hour).

PRCG - Project Run Clone Gen, is used to identify a WU that is assigned to you.
Project: Biological system.
Run: Different starting configuration (positions) of atoms.
Clone: Different starting velocities of atoms (each Run can have multiple Clones with different starting velocities).
Gen: Time sequence (so Clone 1, Gen 2 is sent after Clone 1, Gen 1 is received and processed).
Note: For a given Project number (and Protein name) there are many Runs, Clones and Gens so don't be alarmed if you seem to be processing the same Project/Protein again. The F@H Project doesn't assign duplicate WUs on purpose to keep Donors folding.

PPD - Points Per Day is the total number of points your system is generating while folding the assigned WU(s).
Note: PPD will vary from WU to WU (even if they belong to the same Project) and will be effected by system usage and other factors.

TPF - Time Per Frame means how long it takes to finish 1% of the assigned WU as 1% of a WU is equal to one frame.
Note: The TPF can vary significantly if the system is being used. A dedicated folding system experiences less fluctuations.

FahCore_XX - The piece of software that folds the assigned WU.

FahClient - The piece of software that manages FahCore_XX.

FAHControl (Advanced Control) - The Graphical User Interface (GUI) for FahClient.

FAHViewer - A protein viewer that either shows the current protein being folded by the FahCore_XX or a demo one if FahCore_XX doesn't generate the data.

FAHSlot (Slot) - How the FahClient manages your system's resources to fold the assigned WU. It is either a Central Processing Unit (CPU) or a Graphical Processing Unit (GPU) Slot.

4 - Getting Started With F@H (Basic)

Posted: Sun Apr 19, 2020 12:10 am
by PantherX
  • 4 - Getting Started With F@H (Basic)
If you would like to participate in the F@H Project, you can install the F@H Client on a compatible system. If you don't own the system, ensure you have the system owner's permission (usually written) as per the EULA. Below is a quick overview to help you get started. Please note that folding is very stressful on the system which means that it may generate extra heat, noise and consume more power. For a properly configured system, it isn't an issue. For systems that are overclocked, it may cause issues. The official stance of F@H is that it doesn't not support or encourage overclocking. The integrity for science supersedes any overclocking record.


Supported System Configuration
The following Operating Systems (OS) and hardware configurations are supported by F@H Software for folding. Please note that the older the hardware is, the longer it needs to fold per day to ensure that it can finish the assigned WU successfully before the Timeout date:
Windows (32 bit) - Windows 10, Windows 8, Windows 7
  • CPU with SSE2 or AVX2 or better - Intel Core 2 Duo or newer, Athlon 64 or newer
  • GPU with OpenCL 1.2 with Double Precision - AMD Radeon HD 5830 or newer, Nvidia GeForce GT 710 or newer
Windows (64 bit) - Windows 10, Windows 8, Windows 7
  • CPU with SSE2 or AVX2 or better - Intel Core 2 Duo or newer, Athlon 64 or newer
  • GPU with OpenCL 1.2 with Double Precision - AMD Radeon HD 5830 or newer, Nvidia GeForce GT 710 or newer
Linux (64-bit) - Centos, Debian, Fedora, Mint, Redhat, Ubuntu
  • CPU with SSE2 or AVX2 or better - Intel Core 2 Duo or newer, Athlon 64 or newer
  • GPU with OpenCL 1.2 with Double Precision - AMD Radeon HD 5830 or newer, Nvidia GeForce GT 710 or newer
macOS (64-bit) - Catalina, Mojave, High Sierra, Sierra, El Capitan, Yosemite, Mavericks, Mountain Lion, Lion
  • CPU with SSE2 or AVX2 or better - Intel Core 2 Duo or newer, Athlon 64 or newer
Download F@H Software
Windows Installation Guide
Linux Installation Guide
macOS Installation Guide


Start Folding
After successfully installing the F@H Client, it will download a WU which has a Timeout date and an Expiration date. Your system can contribute by folding as as long as you can return the assigned WU before the Timeout date. Credit is granted for successfully completed WUs based upon how long it took to fold the WU. The time taken to fold the WU starts from when the WU was assigned to the F@H Client until it was successfully completed and uploaded to the F@H Servers.


Credit For WUs
All WUs get bonus points if they are returned before the Timeout date as long as you qualify for it. It uses the scheme of Quick Return Bonus (QRB) to incentivize folding WUs quickly since more science is being done. Credit for successfully completed WUs will not appear in the official stats pages until at least an hour or more after the results are uploaded. Below is a quick summary of how the credits system work:
  1. Before Timeout date - You will get bonus credit once you have folded the WU (bonus varies from system to system and increases for faster completion)
  2. Exceed Timeout date - WU will be reissued to another system while yours is currently folding it. You will get base credit once you have folded the WU (it is significantly less when compared to bonus credits)
  3. Exceed Expiration date - WU is deleted from your system. You won't get any credit (increase the hours for folding or update/retire the system)
In order for Donors to take advantage of QRB, there are some basic requirements which they must meet:
  1. Use F@H Software (Download)
  2. Configure the F@H Client with a Passkey (Details)
  3. Successfully fold 10 WUs before their timeout date by using the same combination of Username and Passkey
  4. Maintain a successful return rate of >= 80% for WUs, i.e. out of every 10 WUs assigned, you must successfully return at least 8 completed WUs (Check)

5 - Getting Started With F@H (Advanced)

Posted: Sun Apr 19, 2020 12:10 am
by PantherX
  • 5 - Getting Started With F@H (Advanced)
For this section, we shall assume that you're familiar with the F@H Software and can easily navigate your way around the F@H Community. There are aspects of the F@H Software that can be tweaked to increase the folding performance of your system and/or allow you to manage multiple systems easily.


Tweaking Slot Options
The default settings ought to be fine for most Donors. However, if you would like to tweak some settings specific to the FAH Slot, you can still do so. Below is the procedure to change the slot settings:
  1. Open up Advanced Control (AKA FAHControl)
  2. Click on Configure
  3. Select the Slots Tab
  4. Select the slot you would like to configure with a single click
  5. Click the Edit button
  6. Scroll down the Folding Slot window to the Extra slot options (expert only) section
  7. Click on the Add button
  8. A Edit Options box will appear where you have to enter the correct values for Name and Value (details below)
  9. Click OK button to close the Edit Options box
  10. Click OK button to close the Folding Slot window
  11. Click on the Save button to save the changes made to the slot
A list of common options are:

Code: Select all

Name					    Value		Description
----------------------------------------------------------------------------------------------------------------------------------------------------------
client-type				advanced	Assigns WUs in late-stage beta if available
next-unit-percentage	X			 X should be between 90 and 100. It tells when the next WU should be downloaded after the current WU reaches X percentage
max-units		        X		    X can be any number; 0 is indefinite. It tells when to pause the slot after X WUs are completed
checkpoint	     	  X		    X is a value between 3 and 30. It will create a checkpoint after X minutes (not all FahCore's accept this parameter)
pause-on-start	      true	    FAHClient starts the slot in the pause state
pause-on-start	      false	   FAHClient will start the slot normally
Managing Multiple FAHClients
If you have multiple systems folding within the same network, they can be easily monitored by a single system. Below are the steps to do so.

Remote System
  1. Open up Advanced Control (AKA FAHControl)
  2. Click Configure
  3. Click Remote Access tab
  4. Enter Password
  5. Enter either the Monitor System's IP or the IP Address range in the Allow field
  6. Click Save
  7. Restart the system
Monitor System
  1. Open up Advanced Control (AKA FAHControl)
  2. Click Add
  3. Under Name, enter the Remote System's name or any other name
  4. Under the Address, enter either the Hostname or IP address of the Remote System
  5. Under the Password, enter the password used in the Remote System
  6. Click Save

6 - How To Post A Log File (Windows)

Posted: Sun Apr 19, 2020 12:11 am
by PantherX
  • 6 - How To Post A Log File (Windows)
There are few methods to locate the log file for the F@H Client that you can use to locate, copy and paste your log to this Forum. However, please note that:
  1. We generally don't need the progress messages between 2% and 99% so they can be removed
  2. A single post has a limit of 60,000 characters so if you encounter this limit, you can remove repetitive messages or split your log file across multiple posts
  3. The default setting of verbosity (3) should be used, any higher will print additional data that is unnecessary which makes it very difficult to troubleshoot in the majority of cases
Method 1 (Windows 10, Windows 8, Windows 7)
  1. Ensure that FAHClient is running by looking for the F@H icon in the notification area of the task bar
  2. Right click the F@H icon
  3. Select Advanced Control (AKA FAHControl) from the menu options
  4. Once Advanced Control opens, select the Log tab
  5. Untick Follow
  6. Click the Refresh button
  7. Click the Copy button
  8. Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
  9. Click the Code button
  10. Within the code tags, paste the log
  11. Click the Submit button to post your post. If you reach the 60,000 character limit, remove progress messages between 2% and 99% and/or split your log across multiple posts
Method 2 (Windows 10, Windows 8, Windows 7)
  1. Type %AppData%\FAHClient in Windows Explorer and hit Enter (If that doesn't work, try %ALLUSERSPROFILE%\FAHClient)
  2. A window will open which will contain F@H files and folders. Depending on your need, focus on:
    A) log file -> This is the most recent log file
    B) logs folder -> This contains the previous 16 log files
  3. Double click on the appropriate log file to open it
  4. Copy the contents of it
  5. Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
  6. Click the Code button
  7. Within the code tags, paste the log
  8. Click the Submit button to post your post. If you reach the 60,000 character limit, remove progress messages between 2% and 99% and/or split your log across multiple posts
Method 3 (Windows 8, Windows 7)
  1. Click the Start Button
  2. Click on All Programs
  3. Click on FAHClient folder
  4. Click on Data Directory folder
  5. A window will open which will contain F@H files and folders. Depending on your need, focus on:
    A) log file -> This is the most recent log file
    B) logs folder -> This contains the previous 16 log files
  6. Double click on the appropriate log file to open it
  7. Copy the contents of it
  8. Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
  9. Click the Code button
  10. Within the code tags, paste the log
  11. Click the Submit button to post your post. If you reach the 60,000 character limit, remove progress messages between 2% and 99% and/or split your log across multiple posts
A sample log file covering the needed sections; System Info and Configuration along with normal folding process is shown below:

Code: Select all

*********************** Log Started 2020-05-06T05:39:25Z ***********************
05:39:25:Trying to access database...
05:39:25:Successfully acquired database lock
05:39:25:Downloading GPUs.txt from assign1.foldingathome.org:80
05:39:25:Connecting to assign1.foldingathome.org:80
05:39:25:Read GPUs.txt
05:39:25:Enabled folding slot 01: PAUSED gpu:0:GP102 [GeForce GTX 1080 Ti] 11380 (by user)
05:39:25:****************************** FAHClient ******************************
05:39:25:        Version: 7.6.13
05:39:25:         Author: Joseph Coffland <joseph@cauldrondevelopment.com>
05:39:25:      Copyright: 2020 foldingathome.org
05:39:25:       Homepage: https://foldingathome.org/
05:39:25:           Date: Apr 27 2020
05:39:25:           Time: 21:21:01
05:39:25:       Revision: 5a652817f46116b6e135503af97f18e094414e3b
05:39:25:         Branch: master
05:39:25:       Compiler: Visual C++ 2008
05:39:25:        Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
05:39:25:       Platform: win32 10
05:39:25:           Bits: 32
05:39:25:           Mode: Release
05:39:25:         Config: C:\Users\PantherX-H\AppData\Roaming\FAHClient\config.xml
05:39:25:******************************** CBang ********************************
05:39:25:           Date: Apr 24 2020
05:39:25:           Time: 17:07:55
05:39:25:       Revision: ea081a3b3b0f4a37c4d0440b4f1bc184197c7797
05:39:25:         Branch: master
05:39:25:       Compiler: Visual C++ 2008
05:39:25:        Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
05:39:25:       Platform: win32 10
05:39:25:           Bits: 32
05:39:25:           Mode: Release
05:39:25:******************************* System ********************************
05:39:25:            CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
05:39:25:         CPU ID: GenuineIntel Family 6 Model 94 Stepping 3
05:39:25:           CPUs: 8
05:39:25:         Memory: 31.94GiB
05:39:25:    Free Memory: 22.16GiB
05:39:25:        Threads: WINDOWS_THREADS
05:39:25:     OS Version: 6.2
05:39:25:    Has Battery: false
05:39:25:     On Battery: false
05:39:25:     UTC Offset: 12
05:39:25:            PID: 16912
05:39:25:            CWD: C:\Users\PantherX-H\AppData\Roaming\FAHClient
05:39:25:  Win32 Service: false
05:39:25:             OS: Windows 10 Enterprise
05:39:25:        OS Arch: AMD64
05:39:25:           GPUs: 1
05:39:25:          GPU 0: Bus:1 Slot:0 Func:0 NVIDIA:8 GP102 [GeForce GTX 1080 Ti] 11380
05:39:25:  CUDA Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:6.1 Driver:10.2
05:39:25:OpenCL Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:1.2 Driver:442.19
05:39:25:******************************* libFAH ********************************
05:39:25:           Date: Apr 15 2020
05:39:25:           Time: 14:53:14
05:39:25:       Revision: 216968bc7025029c841ed6e36e81a03a316890d3
05:39:25:         Branch: master
05:39:25:       Compiler: Visual C++ 2008
05:39:25:        Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
05:39:25:       Platform: win32 10
05:39:25:           Bits: 32
05:39:25:           Mode: Release
05:39:25:***********************************************************************
05:39:25:<config>
05:39:25:  <!-- Folding Core -->
05:39:25:  <checkpoint v='30'/>
05:39:25:  <core-priority v='low'/>
05:39:25:
05:39:25:  <!-- Folding Slot Configuration -->
05:39:25:  <client-type v='advanced'/>
05:39:25:
05:39:25:  <!-- Network -->
05:39:25:  <proxy v=':8080'/>
05:39:25:
05:39:25:  <!-- Slot Control -->
05:39:25:  <pause-on-start v='true'/>
05:39:25:  <power v='full'/>
05:39:25:
05:39:25:  <!-- User Information -->
05:39:25:  <passkey v='*****'/>
05:39:25:  <team v='69411'/>
05:39:25:  <user v='PantherX'/>
05:39:25:
05:39:25:  <!-- Work Unit Control -->
05:39:25:  <next-unit-percentage v='100'/>
05:39:25:
05:39:25:  <!-- Folding Slots -->
05:39:25:  <slot id='1' type='GPU'/>
05:39:25:</config>
05:39:26:Set client configured
05:40:56:FS01:Unpaused
05:40:56:WU00:FS01:Connecting to assign1.foldingathome.org:80
05:40:57:WU00:FS01:Connecting to assign1.foldingathome.org:80
05:40:57:WU00:FS01:Assigned to work server 206.223.170.146
05:40:58:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP102 [GeForce GTX 1080 Ti] 11380 from 206.223.170.146
05:40:58:WU00:FS01:Connecting to 206.223.170.146:8080
05:41:04:WU00:FS01:Downloading 196.17MiB
05:41:10:WU00:FS01:Download 2.45%
TRIMMED
05:45:28:WU00:FS01:Download 98.42%
05:45:33:WU00:FS01:Download complete
05:45:33:WU00:FS01:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:14251 run:492 clone:1 gen:2 core:0x22 unit:0x00000002cedfaa925eab032255ac3329
05:45:34:WU00:FS01:Downloading core from http://cores.foldingathome.org/v7/win/64bit/Core_22.fah
05:45:34:WU00:FS01:Connecting to cores.foldingathome.org:80
05:45:34:WU00:FS01:FahCore 22: Downloading 4.04MiB
05:45:36:WU00:FS01:FahCore 22: Download complete
05:45:36:WU00:FS01:Valid core signature
05:45:36:WU00:FS01:Unpacked 13.50MiB to cores/cores.foldingathome.org/v7/win/64bit/Core_22.fah/FahCore_22.exe
05:45:36:WU00:FS01:Starting
05:45:36:WU00:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\PantherX-H\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/v7/win/64bit/Core_22.fah/FahCore_22.exe -dir 00 -suffix 01 -version 706 -lifeline 16912 -checkpoint 30 -gpu-vendor nvidia -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu 0
05:45:36:WU00:FS01:Started FahCore on PID 16588
05:45:36:WU00:FS01:Core PID:12752
05:45:36:WU00:FS01:FahCore 0x22 started
05:45:36:WU00:FS01:0x22:*********************** Log Started 2020-05-06T05:45:36Z ***********************
05:45:36:WU00:FS01:0x22:*************************** Core22 Folding@home Core ***************************
05:45:36:WU00:FS01:0x22:       Type: 0x22
05:45:36:WU00:FS01:0x22:       Core: Core22
05:45:36:WU00:FS01:0x22:    Website: https://foldingathome.org/
05:45:36:WU00:FS01:0x22:  Copyright: (c) 2009-2018 foldingathome.org
05:45:36:WU00:FS01:0x22:     Author: John Chodera <john.chodera@choderalab.org> and Rafal Wiewiora
05:45:36:WU00:FS01:0x22:             <rafal.wiewiora@choderalab.org>
05:45:36:WU00:FS01:0x22:       Args: -dir 00 -suffix 01 -version 706 -lifeline 16588 -checkpoint 30
05:45:36:WU00:FS01:0x22:             -gpu-vendor nvidia -opencl-platform 0 -opencl-device 0 -cuda-device
05:45:36:WU00:FS01:0x22:             0 -gpu 0
05:45:36:WU00:FS01:0x22:     Config: <none>
05:45:36:WU00:FS01:0x22:************************************ Build *************************************
05:45:37:WU00:FS01:0x22:    Version: 0.0.5
05:45:37:WU00:FS01:0x22:       Date: Apr 22 2020
05:45:37:WU00:FS01:0x22:       Time: 04:42:59
05:45:37:WU00:FS01:0x22: Repository: Git
05:45:37:WU00:FS01:0x22:   Revision: 2d69202c898bd9bb3e093f51cd32bf411c2a0388
05:45:37:WU00:FS01:0x22:     Branch: HEAD
05:45:37:WU00:FS01:0x22:   Compiler: Visual C++ 2008
05:45:37:WU00:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
05:45:37:WU00:FS01:0x22:   Platform: win32 10
05:45:37:WU00:FS01:0x22:       Bits: 64
05:45:37:WU00:FS01:0x22:       Mode: Release
05:45:37:WU00:FS01:0x22:************************************ System ************************************
05:45:37:WU00:FS01:0x22:        CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
05:45:37:WU00:FS01:0x22:     CPU ID: GenuineIntel Family 6 Model 94 Stepping 3
05:45:37:WU00:FS01:0x22:       CPUs: 8
05:45:37:WU00:FS01:0x22:     Memory: 31.94GiB
05:45:37:WU00:FS01:0x22:Free Memory: 22.16GiB
05:45:37:WU00:FS01:0x22:    Threads: WINDOWS_THREADS
05:45:37:WU00:FS01:0x22: OS Version: 6.2
05:45:37:WU00:FS01:0x22:Has Battery: false
05:45:37:WU00:FS01:0x22: On Battery: false
05:45:37:WU00:FS01:0x22: UTC Offset: 12
05:45:37:WU00:FS01:0x22:        PID: 12752
05:45:37:WU00:FS01:0x22:        CWD: C:\Users\PantherX-H\AppData\Roaming\FAHClient\work
05:45:37:WU00:FS01:0x22:         OS: Windows 10 Pro
05:45:37:WU00:FS01:0x22:    OS Arch: AMD64
05:45:37:WU00:FS01:0x22:********************************************************************************
05:45:37:WU00:FS01:0x22:Project: 14251 (Run 492, Clone 1, Gen 2)
05:45:37:WU00:FS01:0x22:Unit: 0x00000002cedfaa925eab032255ac3329
05:45:37:WU00:FS01:0x22:Reading tar file core.xml
05:45:37:WU00:FS01:0x22:Reading tar file integrator.xml
05:45:37:WU00:FS01:0x22:Reading tar file state.xml
05:45:38:WU00:FS01:0x22:Reading tar file system.xml
05:45:39:WU00:FS01:0x22:Digital signatures verified
05:45:39:WU00:FS01:0x22:Folding@home GPU Core22 Folding@home Core
05:45:39:WU00:FS01:0x22:Version 0.0.5
05:46:06:WU00:FS01:0x22:Completed 0 out of 500000 steps (0%)
05:46:07:WU00:FS01:0x22:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
05:47:37:WU00:FS01:0x22:Completed 5000 out of 500000 steps (1%)
05:49:07:WU00:FS01:0x22:Completed 10000 out of 500000 steps (2%)
TRIMMED
08:16:54:WU00:FS01:0x22:Completed 495000 out of 500000 steps (99%)
08:18:23:WU00:FS01:0x22:Completed 500000 out of 500000 steps (100%)
08:18:33:WU00:FS01:0x22:Saving result file ..\logfile_01.txt
08:18:33:WU00:FS01:0x22:Saving result file checkpointState.xml
08:18:34:WU00:FS01:0x22:Saving result file checkpt.crc
08:18:34:WU00:FS01:0x22:Saving result file positions.xtc
08:18:34:WU00:FS01:0x22:Saving result file science.log
08:18:34:WU00:FS01:0x22:Folding@home Core Shutdown: FINISHED_UNIT
08:18:35:WU00:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
08:18:35:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:14251 run:492 clone:1 gen:2 core:0x22 unit:0x00000002cedfaa925eab032255ac3329
08:18:35:WU00:FS01:Uploading 119.37MiB to 206.223.170.146
08:18:35:WU00:FS01:Connecting to 206.223.170.146:8080
TRIMMED
08:25:17:WU00:FS01:Upload 98.85%
08:25:22:WU00:FS01:Upload complete
08:25:22:WU00:FS01:Server responded WORK_ACK (400)
08:25:22:WU00:FS01:Final credit estimate, 143491.00 points
08:25:22:WU00:FS01:Cleaning up

7 - How To Post A Log File (Linux)

Posted: Sun Apr 19, 2020 12:11 am
by PantherX
  • 7 - How To Post A Log File (Linux)
There are few methods to locate the log file for the F@H Client that you can use to locate, copy and paste your log to this Forum. However, please note that:
  1. We generally don't need the progress messages between 2% and 99% so they can be removed
  2. A single post has a limit of 60,000 characters so if you encounter this limit, you can remove repetitive messages or split your log file across multiple posts
  3. The default setting of verbosity (3) should be used, any higher will print additional data that is unnecessary which makes it very difficult to troubleshoot in the majority of cases
Method 1 (Centos, Debian, Fedora, Mint, Redhat, Ubuntu)
  1. Open up up Advanced Control (AKA FAHControl)
  2. Select the Log tab
  3. Untick Follow
  4. Click the Refresh button
  5. Click the Copy button
  6. Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
  7. Click the Code button
  8. Within the code tags, paste the log
  9. Click the Submit button to post your post. If you reach the 60,000 character limit, remove progress messages between 2% and 99% and/or split your log across multiple posts
Method 2 (*unix)
  1. Navigate to /var/lib/fahclient
  2. You will see F@H files and folders. Depending on your need, focus on:
    A) log file -> This is the most recent log file
    B) logs folder -> This contains the previous 16 log files
  3. Double click on the appropriate log file to open it
  4. Copy the contents of it
  5. Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
  6. Click the Code button
  7. Within the code tags, paste the log
  8. Click the Submit button to post your post If you reach the 60,000 character limit, remove progress messages between 2% and 99% and/or split your log across multiple posts
A sample log file covering the needed sections; System Info and Configuration along with normal folding process is shown below:

Code: Select all

*********************** Log Started 2014-03-08T00:14:54Z ***********************
00:14:54:************************* Folding@home Client *************************
00:14:54:    Website: http://folding.stanford.edu/
00:14:54:  Copyright: (c) 2009-2014 Stanford University
00:14:54:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
00:14:54:       Args: --child --lifeline 1698 /etc/fahclient/config.xml --run-as
00:14:54:             fahclient --pid-file=/var/run/fahclient.pid --daemon
00:14:54:     Config: /etc/fahclient/config.xml
00:14:54:******************************** Build ********************************
00:14:54:    Version: 7.4.4
00:14:54:       Date: Mar 4 2014
00:14:54:       Time: 12:02:38
00:14:54:    SVN Rev: 4130
00:14:54:     Branch: fah/trunk/client
00:14:54:   Compiler: GNU 4.4.7
00:14:54:    Options: -std=gnu++98 -O3 -funroll-loops -mfpmath=sse -ffast-math
00:14:54:             -fno-unsafe-math-optimizations -msse2
00:14:54:   Platform: linux2 3.2.0-1-amd64
00:14:54:       Bits: 64
00:14:54:       Mode: Release
00:14:54:******************************* System ********************************
00:14:54:        CPU: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz
00:14:54:     CPU ID: GenuineIntel Family 6 Model 30 Stepping 5
00:14:54:       CPUs: 8
00:14:54:     Memory: 3.85GiB
00:14:54:Free Memory: 3.44GiB
00:14:54:    Threads: POSIX_THREADS
00:14:54: OS Version: 3.8
00:14:54:Has Battery: false
00:14:54: On Battery: false
00:14:54: UTC Offset: 0
00:14:54:        PID: 1700
00:14:54:        CWD: /var/lib/fahclient
00:14:54:         OS: Linux 3.8.0-36-generic x86_64
00:14:54:    OS Arch: AMD64
00:14:54:       GPUs: 0
00:14:54:       CUDA: Not detected
00:14:54:***********************************************************************
00:14:54:<config>
00:14:54:  <!-- Client Control -->
00:14:54:  <fold-anon v='true'/>
00:14:54:
00:14:54:  <!-- Folding Slot Configuration -->
00:14:54:  <gpu v='false'/>
00:14:54:
00:14:54:  <!-- Folding Slots -->
00:14:54:  <slot id='0' type='CPU'/>
00:14:54:</config>
00:14:54:Switching to user fahclient
00:14:54:Trying to access database...
00:14:55:Successfully acquired database lock
00:14:55:Enabled folding slot 00: READY cpu:7
00:14:55:WU00:FS00:Starting
00:14:55:WU00:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/www.stanford.edu/~pande/Linux/AMD64/Core_a3.fah/FahCore_a3 -dir 00 -suffix 01 -version 704 -lifeline 1700 -checkpoint 15 -np 7
00:14:55:WU00:FS00:Started FahCore on PID 1923
00:14:55:WU00:FS00:Core PID:2016
00:14:55:WU00:FS00:FahCore 0xa3 started
00:14:56:WU00:FS00:0xa3:
00:14:56:WU00:FS00:0xa3:*------------------------------*
00:14:56:WU00:FS00:0xa3:Folding@Home Gromacs SMP Core
00:14:56:WU00:FS00:0xa3:Version 2.27 (Dec. 15, 2010)
00:14:56:WU00:FS00:0xa3:
00:14:56:WU00:FS00:0xa3:Preparing to commence simulation
00:14:56:WU00:FS00:0xa3:- Looking at optimizations...
00:14:56:WU00:FS00:0xa3:- Files status OK
00:14:56:WU00:FS00:0xa3:- Expanded 3845612 -> 4375408 (decompressed 113.7 percent)
00:14:56:WU00:FS00:0xa3:Called DecompressByteArray: compressed_data_size=3845612 data_size=4375408, decompressed_data_size=4375408 diff=0
00:14:56:WU00:FS00:0xa3:- Digital signature verified
00:14:56:WU00:FS00:0xa3:
00:14:56:WU00:FS00:0xa3:Project: 8579 (Run 0, Clone 0, Gen 495)
00:14:56:WU00:FS00:0xa3:
00:14:56:WU00:FS00:0xa3:Assembly optimizations on if available.
00:14:56:WU00:FS00:0xa3:Entering M.D.
00:15:02:WU00:FS00:0xa3:Mapping NT from 7 to 7 
00:15:06:WU00:FS00:0xa3:Completed 0 out of 500000 steps  (0%)
00:26:18:WU00:FS00:0xa3:Completed 5000 out of 500000 steps  (1%)
00:37:06:WU00:FS00:0xa3:Completed 10000 out of 500000 steps  (2%)
00:47:53:WU00:FS00:0xa3:Completed 15000 out of 500000 steps  (3%)
00:58:39:WU00:FS00:0xa3:Completed 20000 out of 500000 steps  (4%)
01:09:28:WU00:FS00:0xa3:Completed 25000 out of 500000 steps  (5%)

8 - How To Post A Log File (macOS)

Posted: Sun Apr 19, 2020 12:11 am
by PantherX
  • 8 - How To Post A Log File (macOS)
There are few methods to locate the log file for the F@H Client that you can use to locate, copy and paste your log to this Forum. However, please note that:
  1. We generally don't need the progress messages between 2% and 99% so they can be removed
  2. A single post has a limit of 60,000 characters so if you encounter this limit, you can remove repetitive messages or split your log file across multiple posts
  3. The default setting of verbosity (3) should be used, any higher will print additional data that is unnecessary which makes it very difficult to troubleshoot in the majority of cases
Method 1 (via FAHControl)
  1. Open up up Advanced Control (AKA FAHControl)
  2. Select the Log tab
  3. Untick Follow
  4. Click the Refresh button
  5. Click the Copy button
  6. Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
  7. Click the Code button
  8. Within the code tags, paste the log
  9. Click the Submit button to post your post

Method 2 (via Finder)
  1. Navigate to /Library/Application Support/FAHClient
  2. You will see F@H files and folders. Depending on your need, focus on:
    A) log file -> This is the most recent log file
    B) logs folder -> This contains the previous 16 log files
  3. Double click on the appropriate log file to open it
  4. Copy the contents of it
  5. Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
  6. Click the Code button
  7. Within the code tags, paste the log
  8. Click the Submit button to post your post
A sample log file covering the needed sections; System Info and Configuration along with normal folding process is shown below:

Code: Select all

*********************** Log Started 2014-03-08T01:42:21Z ***********************
01:42:21:************************* Folding@home Client *************************
01:42:21:    Website: http://folding.stanford.edu/
01:42:21:  Copyright: (c) 2009-2014 Stanford University
01:42:21:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
01:42:21:       Args: --child --lifeline 65 --respawn
01:42:21:     Config: /Library/Application Support/FAHClient/config.xml
01:42:21:******************************** Build ********************************
01:42:21:    Version: 7.4.4
01:42:21:       Date: Mar 4 2014
01:42:21:       Time: 20:27:54
01:42:21:    SVN Rev: 4130
01:42:21:     Branch: fah/trunk/client
01:42:21:   Compiler: GNU 4.2.1 (Apple Inc. build 5666) (dot 3)
01:42:21:    Options: -std=gnu++98 -O3 -funroll-loops -mfpmath=sse -ffast-math
01:42:21:             -fno-unsafe-math-optimizations -msse3 -arch x86_64
01:42:21:             -mmacosx-version-min=10.6
01:42:21:   Platform: darwin 10.8.0
01:42:21:       Bits: 64
01:42:21:       Mode: Release
01:42:21:******************************* System ********************************
01:42:21:        CPU: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz
01:42:21:     CPU ID: GenuineIntel Family 6 Model 30 Stepping 5
01:42:21:       CPUs: 8
01:42:21:     Memory: 4.00GiB
01:42:21:Free Memory: 3.39GiB
01:42:21:    Threads: POSIX_THREADS
01:42:21: OS Version: 10.9
01:42:21:Has Battery: false
01:42:21: On Battery: false
01:42:21: UTC Offset: 0
01:42:21:        PID: 173
01:42:21:        CWD: /Library/Application Support/FAHClient
01:42:21:         OS: Darwin 13.1.0 x86_64
01:42:21:    OS Arch: AMD64
01:42:21:       GPUs: 0
01:42:21:       CUDA: Not detected
01:42:21:***********************************************************************
01:42:21:<config>
01:42:21:  <!-- Folding Slots -->
01:42:21:  <slot id='0' type='CPU'/>
01:42:21:</config>
01:42:21:Trying to access database...
01:42:29:Successfully acquired database lock
01:42:29:Enabled folding slot 00: READY cpu:7
01:42:29:WU00:FS00:Starting
01:42:29:WU00:FS00:Running FahCore: /usr/bin/FAHCoreWrapper "/Library/Application Support/FAHClient/cores/www.stanford.edu/~pande/OSX/AMD64/Core_a4.fah/FahCore_a4" -dir 00 -suffix 01 -version 704 -lifeline 173 -checkpoint 15 -np 7
01:42:29:WU00:FS00:Started FahCore on PID 224
01:42:32:WU00:FS00:Core PID:228
01:42:32:WU00:FS00:FahCore 0xa4 started
01:42:34:WU00:FS00:0xa4:
01:42:34:WU00:FS00:0xa4:*------------------------------*
01:42:34:WU00:FS00:0xa4:Folding@Home Gromacs Core
01:42:34:WU00:FS00:0xa4:Version 2.27 (Thu Feb 10 09:46:40 PST 2011)
01:42:34:WU00:FS00:0xa4:
01:42:34:WU00:FS00:0xa4:Preparing to commence simulation
01:42:34:WU00:FS00:0xa4:- Looking at optimizations...
01:42:34:WU00:FS00:0xa4:- Files status OK
01:42:34:WU00:FS00:0xa4:- Expanded 882159 -> 1469104 (decompressed 166.5 percent)
01:42:34:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=882159 data_size=1469104, decompressed_data_size=1469104 diff=0
01:42:34:WU00:FS00:0xa4:- Digital signature verified
01:42:34:WU00:FS00:0xa4:
01:42:34:WU00:FS00:0xa4:Project: 9005 (Run 139, Clone 3, Gen 37)
01:42:34:WU00:FS00:0xa4:
01:42:34:WU00:FS00:0xa4:Assembly optimizations on if available.
01:42:34:WU00:FS00:0xa4:Entering M.D.
01:42:40:WU00:FS00:0xa4:Mapping NT from 7 to 7 
01:42:43:WU00:FS00:0xa4:Completed 0 out of 250000 steps  (0%)
01:44:34:WU00:FS00:0xa4:Completed 2500 out of 250000 steps  (1%)
01:46:18:WU00:FS00:0xa4:Completed 5000 out of 250000 steps  (2%)
01:48:02:WU00:FS00:0xa4:Completed 7500 out of 250000 steps  (3%)
01:49:47:WU00:FS00:0xa4:Completed 10000 out of 250000 steps  (4%)
01:51:31:WU00:FS00:0xa4:Completed 12500 out of 250000 steps  (5%)
01:53:17:WU00:FS00:0xa4:Completed 15000 out of 250000 steps  (6%)

9 - Generic Troubleshooting Tips

Posted: Sun Apr 19, 2020 12:12 am
by PantherX
  • 9 - Generic Troubleshooting Tips
Below are some broad suggestions to help fix an issue that you might have. Please note that these are generic tips and suggestions so it may not apply to your particular setup. We do encourage you to create a thread in the appropriate Forum to get help specific to your needs.


Overheating CPU
  1. Make sure that the cooling system is properly set-up
  2. Make sure that the cooling system is clean and that no dust or debris is blocking the ventilation
  3. Reduce the number the CPUs used by F@H. In V7, this is done via the Advanced Control -> Configure -> Slots Tab -> CPU -> Replace -1 with a number greater than or equal to 1
  4. If you CPU is overclocked, consider reducing the frequencies to lower the heat output
Overheating GPU
  1. Make sure that the cooling system is properly set-up
  2. Make sure that the cooling system is clean and that no dust or debris is blocking the ventilation
  3. If you GPU is overclocked, consider reducing the frequencies to lower the heat output
Missing QRB
  1. Are there any typos in the Username and/or Passkey?
  2. Is the Username/Passkey combination qualified for the QRB?
  3. Are any of your clients producing errors which may have caused you to fall below the 80% WU return rate (Check)?
  4. Are you finishing the WU before the Timeout date?
  5. Is the Client properly configured?
Downloading/Uploading WUs
  1. You are connected to the internet
  2. Your security application isn't blocking F@H connections. If it is, please create an exception
  3. For more information, please see this topic: Troubleshooting F@H Server Connectivity Issues (Do This First)
Web Control Issues
If the Web Control can't connect to the FAHClient, possible reasons are:
  1. FAHClient isn't running. Please ensure that it is.
  2. Browser isn't supported. Make sure that you are using the latest browser version
  3. Sandbox limitations of JavaScript is preventing a remote connection
Advanced Control Issues (Local)
If the Advanced Control can't connect to the FAHClient on the same system, possible reasons are:
  1. FAHClient isn't running. Please ensure that it is.
  2. A security application might be blocking the local connection to FAHClient. Please create an exception.
  3. Make sure that you meet the minimum requirements for Windows, Linux, macOS
Advanced Control Issues (Remote)
If the Advanced Control can't connect to the FAHClient on the remote system, possible reasons are:
  1. FAHClient isn't running on the remote system. Please ensure that it is.
  2. Firewall is blocking the remote connection. Ensure that the firewall rules permit F@H connections.
  3. Advanced Control (AKA FAHControl) isn't connecting. Ensure that that the Network Profile is not Public
  4. Passwords on the local and remote system is the same. Please ensure that they are the same.
  5. Remote system is using a different version of F@H Software than the local system. Please ensure that both systems are running the same version of F@H Software.
  6. The allow/deny settings might be incorrect. Please ensure that the settings are correct.
  7. Remote client wasn't restarted after configuring remote access. Please restart the client after configuring remote access.
  8. Make sure that you meet the minimum requirements for Windows, Linux, macOS
Incorrect Slot Options
If you have changed some of the slot options and can't remember the defaults, below is the list of options and their default values for V7.6.13, please note that some are dependent on the operating system:

Code: Select all

PS C:\Program Files (x86)\FAHClient> .\FAHClient.exe --help
Usage: C:\Program Files (x86)\FAHClient\FAHClient.exe [[--config] <filename>] [OPTIONS]...

OPTIONS:
  --chdir <string>
      Change directory before starting server. All files opened after this point, such as the configuration file, must have paths relative to the new directory.

  --configure
      Create a basic configuration file, then exit.

  --dump <string>
      Dump either 'all' or a specific work unit, identified by its queue ID, then exit.

  --finish
      Finish all current work units, send the results, then exit.

  --install-service
      Install the application as a Win32 service then exit.

  --lspci
      List the PCI bus devices, which can be helpful for finding GPU vendor and device IDs.

  --queue-info
      Print work unit queue then exit.

  --send
      Send all finished work units, then exit.

  --send-command <string>
      Send a command to an already running client.

  --send-finish [string]
      Finish a slot or all slots on an already running client.

  --send-pause [string]
      Pause a slot or all slots on an already running client.

  --send-unpause [string]
      Unpause a slot or all slots on an already running client.

  --start-service
      Start Win32 service then exit.

  --stop-service
      Stop Win32 service then exit.

  --uninstall-service
      Uninstall the application as a Win32 service then exit.

Configuration:
  --config <string=config.xml>
      Set configuration file.

  --print
      Print configuration and exit.

Informational:
  --help [string]
      Print help screen or help on a particular option and exit.

  --html-help
      Print help in HTML format and exit.

  --info
      Print application and system information and exit.

  --license
      License information and exit.

  -q|--quiet
      Set verbosity to zero.

  -v|--verbose
      Increase verbosity level.

  --version
      Print application version and exit.


Configuration options:
The following options can be specified in a configuration file or on the command line using the following syntax:

    --<option> <value>

  or:

    --<option>=<value>

  or when marking boolean values true:

    --<option>

Client Control:
  client-threads <integer=6>
    The number of client processing threads.

  cycle-rate <double=4>
    The maximum cycle frequency in Hz of client threads.

  cycles <integer=-1>
    Run at most this many cycles. A value less than zero means run indefinitely.

  disable-sleep-when-active <boolean=true>
    Attempt to keep the system from sleeping when folding, unless on battery.

  exit-when-done <boolean=false>
    Exit when all slots are paused.

  fold-anon <boolean=false>
    Start folding even if not configured.

  open-web-control <boolean=false>
    Make an operating system specific call to open the Web Control in a browser once client is fully loaded

Configuration:
  config-rotate <boolean=true>
    Rotate the configuration file to a backup when saving would overwrite the previous configuration.

  config-rotate-dir <string=configs>
    Put rotated configs in this directory.

  config-rotate-max <integer=16>
    The maximum number of rotated configuration files to keep. A value of zero will keep all configuration file backups.

Error Handling:
  max-slot-errors <integer=10>
    The maximum number of errors before a slot is paused.

  max-unit-errors <integer=5>
    The maximum number of errors before a work unit is dumped.

Folding Core:
  checkpoint <integer=15>
    Tell cores to checkpoint at least every # minutes.

  core-priority <string=idle>
    Set the core priority. Valid values are: idle or low

  cpu-usage <integer=100>
    The maximum percentage of the CPU a core should use. Not implemented by all cores.

  gpu-usage <integer=100>
    GPU usage as a percent from 10-100

  no-assembly <boolean=false>
    Tell cores to disable optimized assembly code.

Folding Slot Configuration:
  cause <string=ANY>
    The cause you prefer to support.

  client-subtype <string=STDCLI>
    The client subtype

  client-type <string=normal>
    The client type. Can be 'normal', 'advanced' or 'beta'.

  cpu-species <string=X86_PENTIUM_II>
    CPU species.

  cpu-type <string=AMD64>
    CPU type.

  cpus <integer=-1>
    How many CPUs a slot should use. <= 0 will use all the CPUs detected in the system.

  cuda-index <string>
    The CUDA device index of the GPU, counting starts from 0.

  disable-viz <boolean=false>
    Disable reading visualization data.

  extra-core-args <string>
    Pass extra arguments to the core.

  gpu <boolean=true>
    Enable or disable auto-confiugration of GPU slots, requires appropriate hardware.

  gpu-index <string>
    The index of the GPU as detected by the client. This index corresponds directly to the GPUs listed in the client's '--info' output.

  max-packet-size <string=normal>
    Max size in bytes of a work unit packet. Can be small=5MiB, normal=25MiB, big=500MiB or a number.

  memory <string>
    Override memory, in bytes, reported to Folding@home.

  opencl-index <string>
    The OpenCL device index of the GPU, counting starts from 0.

  os-species <string=WIN_8>
    Operating system species.

  os-type <string=WIN32>
    Operating system type.

  project-key <integer=0>
    Key for access to restricted testing projects.

  smp <boolean=true>
    Enable or disable auto-configuration of SMP slots, requires appropriate hardware.

GUI:
  gui-enabled <boolean=true>
    Set to false to disable the GUI. A GUI is not currently supported on all operating systems.

HTTP Server:
  allow <string=127.0.0.1>
    Client addresses which are allowed to connect to this server. This option overrides IPs which are denied in the deny option. The pattern 0/0 matches all addresses.

  connection-timeout <integer=60>
    The maximum amount of time, in seconds, a connection can be idle before being dropped.

  deny <string=0/0>
    Client address which are not allowed to connect to this server.

  http-addresses <string=0:7396>
    A space separated list of server address and port pairs to listen on in the form <ip | hostname>[:<port>]

  https-addresses <string=>
    A space separated list of secure server address and port pairs to listen on in the form <ip | hostname>[:<port>]

  max-connect-time <integer=900>
    The maximum amount of time, in seconds, a client can be connected to the server.

  max-connections <integer=800>
    Sets the maximum number of simultaneous connections.

  max-request-length <integer=52428800>
    Sets the maximum length of a client request packet.

  min-connect-time <integer=300>
    The minimum amount of time, in seconds, a client must be connected to the server before it can be dropped in favor or a new connection.

HTTP Server SSL:
  certificate-file <string>
    The servers certificate file in PEM format.

  crl-file <string>
    Supply a Certificate Revocation List. Overrides any internal CRL

  private-key-file <string>
    The servers private key file in PEM format.

Logging:
  log <string=log.txt>
    Set log file.

  log-color <boolean=false>
    Print log messages with ANSI color coding.

  log-crlf <boolean=true>
    Print carriage return and line feed at end of log lines.

  log-date <boolean=false>
    Print date information with log entries.

  log-date-periodically <integer=21600>
    Print date to log before new log entries if so many seconds have passed since the last date was printed.

  log-domain <boolean=false>
    Print domain information with log entries.

  log-domain-levels <string ...>
    Set log levels by domain. Format is:
      <domain>[:i|d|t]:<level> ...
    Entries are separated by white-space and or commas.
      i - info
    For example: server:i:3 module:6
    Set 'server' domain info messages to level 3 and 'module' info messages to level 6. All other domains will follow the system wide log verbosity level. If <level> is negative it is relative to the system wide verbosity.

  log-header <boolean=true>
    Enable log message headers.

  log-level <boolean=true>
    Print level information with log entries.

  log-no-info-header <boolean=true>
    Don't print 'INFO(#):' in header.

  log-redirect <boolean=false>
    Redirect all output to log file. Implies !log-to-screen.

  log-rotate <boolean=true>
    Rotate log files on each run.

  log-rotate-dir <string=logs>
    Put rotated logs in this directory.

  log-rotate-max <integer=16>
    Maximum number of rotated logs to keep.

  log-short-level <boolean=false>
    Print shortened level information with log entries.

  log-simple-domains <boolean=true>
    Remove any leading directories and trailing file extensions from domains so that source code file names can be easily used as log domains.

  log-thread-id <boolean=false>
    Print id with log entries.

  log-thread-prefix <boolean=true>
    Print thread prefixes, if set, with log entries.

  log-time <boolean=true>
    Print time information with log entries.

  log-to-screen <boolean=true>
    Log to screen.

  log-truncate <boolean=false>
    Truncate log file.

  verbosity <integer=3>
    Set logging level for INFO messages.

Network:
  proxy <string=>
    Set proxy for outgoing HTTP connections

  proxy-enable <boolean=false>
    Enable proxy configuration

  proxy-pass <string=>
    Set password for proxy connections

  proxy-user <string=>
    Set user name for proxy connections

Process Control:
  child <boolean=false>
    Disable 'daemon', 'fork', 'pid' and 'respawn' options. Also defaults 'log-to-screen' to false. Used internally.

  daemon <boolean=false>
    Short for --pid --service --respawn --log=''

  pid <boolean=false>
    Create PID file.

  pid-file <string=FAHClient.pid>
    Name of PID file.

  priority <string>
    Set the process priority. Valid values are: idle, low, normal, high or realtime.

  respawn <boolean=false>
    Run the application as a child process and respawn if it is killed or exits.

  service <boolean=false>
    Ignore user logout or hangup and interrupt signals

Remote Command Server:
  command-address <string=0.0.0.0>
    The address to which the command server should be bound.

  command-allow-no-pass <string=127.0.0.1>
    IP address ranges that are allowed access to the command server with out a password if the 'password' option is set. These addresses will also have to be allowed IP based access.

  command-deny-no-pass <string=0/0>
    IP address ranges that are not allowed access to the command server with out a password if the 'password' option is set. Overridden by command-allow-no-pass

  command-enable <boolean=true>
    Set to false to disable the command server.

  command-port <integer=36330>
    The port to which the command server should be bound.

  password <string>
    Set a command server password. Warning, setting a password disables the default IP address blocking.

Slot Control:
  idle <boolean=false>
    Only run slot when idle.

  max-shutdown-wait <integer=60>
    The maximum amount of time to wait in seconds for a unit to exit on shutdown.

  pause-on-battery <boolean=true>
    Pause the client or slot when the OS indicates the machine is running on battery power.

  pause-on-start <boolean=false>
    If true the slot will be started in a paused state.

  paused <boolean=false>
    True if slot is paused.

  power <string=medium>
    Set the client's power level. Valid values are 'light', 'medium' or 'full'. This setting affects the defaults of several other options such as 'cpus', 'pause-on-battery', etc.

User Information:
  machine-id <integer=0>
    The machine ID.

  passkey <string=>
    Your passkey.

  team <integer=0>
    Your team number.

  user <string=Anonymous>
    Your user name.

Web Server:
  web-allow <string=127.0.0.1>
    Client addresses which are allowed to connect to this Web server. This option overrides IPs which are denied in the web-deny option. This option differs from the 'allow'/'deny' options in that clients that are not allowed are served an access denied page rather than simply dropping the connection. The value '0/0' matches all IPs.

  web-deny <string=0/0>
    Client address which are not allowed to connect to this Web server.

  web-enable <boolean=true>
    Set to false to disable the web server.

Web Server Sessions:
  session-cookie <string=sid>
    The name of the session cookie.

  session-lifetime <integer=86400>
    The maximum session lifetime in seconds. Zero for unlimited session lifetime.

  session-timeout <integer=3600>
    The max maximum amount of time in seconds since the last time a session was used before it timesout. Zero for no session timeout.

Windows Service:
  service-description <string=FAHClient>
    The description for the Windows service control manager.

  service-restart <boolean=true>
    Configure Windows service to automatically restart on failure.

  service-restart-delay <integer=5000>
    The amount of time in milliseconds to delay between restarts of the Windows service.

Work Unit Control:
  dump-after-deadline <boolean=true>
    Dump units if their deadline has passed.

  max-queue <integer=16>
    Maximum units per slot in the work queue.

  max-units <integer=0>
    Process at most this number of units, then pause.

  next-unit-percentage <integer=99>
    Pre-download the next work unit when the current one is this far along. Values less than 90 are not allowed.

  stall-detection-enabled <boolean=false>
    Attempt to detect stalled work units and restart them.

  stall-percent <integer=5>
    Minimum estimated percent work unit completion since last frame before a WU can be considered stalled, if zero the percentage is ignored.

  stall-timeout <integer=1800>
    Minimum time, in seconds, since last frame before a WU can be considered stalled.
PS C:\Program Files (x86)\FAHClient>

10 - Additional Links

Posted: Sun Apr 19, 2020 12:12 am
by PantherX
  • 10 - Additional Links
Below is a list of links which you may find help:

New F@H Projects & General Announcements - Information posted by the F@H Team to update the Donors
F@H Web Apps - List of F@H web tools to check your passkey, view project descriptions, check WU status, etc
F@H FAQs - Frequently Asked Questions regarding F@H
F@H Username Selection - Guidance on how to choose your F@H username
F@H Passkey - Information on the reason behind using a passkey
F@H Timeline - Milestone and important achievements attained by the F@H
F@H Papers & Results - All the scientific papers published using F@H
F@H Wikipedia Article - Additional information of F@H on Wikipedia
F@H Science Codebase - The code used by F@H to drive the science behind folding on CPUs
F@H Science Codebase - The code used by F@H to drive the science behind folding on GPUs
F@H Open Source Codebase - F@H Software that is open source
F@H Homepage - Main site for F@H
F@H Twitter -> Official Twitter account
F@H Facebook -> Official Facebook page
F@H LinkedIn -> Official LindedIn page
F@H YouTube -> Official YouTube channel
F@H Twitch -> Official Twitch channel
F@H Reddit -> Official Reddit page
F@H Discord -> Official Discord Server



Additional comments are welcomed via Private Message (PM) to me. I wish to thanks the following users who have contributed in this thread (alphabetically):
7im, bollix47, bruce, Joe_H, P5-133XL, SeanPearce44, sukritsingh, whatshisname

Last Updated: 19 May 2020