dslreports logo
site
spacer

spacer
 
    All FAQs Site FAQ DSL FAQ Cable Tech About DSL Distance DSL Hurdles »»
spc

spacer




how-to block ads




2.6 Troubleshooting

Do you have a firewall? If so, and if the name of the FAHxxxxx.exe file is different, did you change the firewall rule to allow it access?

This FAQ was suggested by jazzman916 See Profile, who apparently has some personal experience. ;)

by sortofageek See Profile
last modified: 2005-11-14 21:44:26

The short answer is "yes." However, the results may not be as intended. If you are tempted to try that, please read this first. If you still want to try it, please make a backup of your Folding@Home folder and all files and subfolders before you start so you can go back if it doesn't go well for you.

Thank you, dandelion See Profile, for finding the topic for us. :)

by sortofageek See Profile
last modified: 2006-07-19 13:00:41

Changes in IE settings for IE7 prevent the client from uploading work if the "Use Internet Explorer Settings" parameter is set to yes. You will see this in your log file:

[21:28:11] - Use IE connection settings: Yes 
 

To change it, reconfigure your client as specified in these FAQs:
(Note: The following two links are currently dead until we can create new FAQs for them, sorry. ~sorto')
»www3.dslreports.com/faq/thfaq/2.···on#14182
»www3.dslreports.com/faq/thfaq/2.···ion#3017

When you get to the "Use Internet Explorer Settings?" question, type no.

Even after correcting this parameter, you may continue to see reports of failed attempts to return work. You may see something similar to this in your console window or fahlog.txt file:

[03:11:43] + Could not connect to Work Server (results) 
[03:11:43] (171.64.122.136:80) 
[03:11:43] - Error: Could not transmit unit 06 (completed January 10) to work server. 
[03:11:43] - 13 failed uploads of this unit. 
 
[03:11:43] + Attempting to send results 
[03:11:43] - Reading file work/wuresults_06.dat from core 
[03:11:43] (Read 2545330 bytes from disk) 
[03:11:44] Error: Got status code 503 from server 
[03:11:44] + Could not connect to Work Server (results) 
[03:11:44] (171.65.103.100:80) 
[03:11:44] Could not transmit unit 06 to Collection server; keeping in queue. 
 
[03:11:44] + Attempting to send results 
[03:11:44] - Reading file work/wuresults_07.dat from core 
[03:11:44] (Read 4621137 bytes from disk) 
[03:12:17] Couldn't send HTTP request to server (wininet) 
[03:12:17] + Could not connect to Work Server (results) 
[03:12:17] (171.64.65.83:8080) 
[03:12:17] - Error: Could not transmit unit 07 (completed January 11) to work server. 
[03:12:17] - 6 failed uploads of this unit. 
 
[03:12:17] + Attempting to send results 
[03:12:17] - Reading file work/wuresults_07.dat from core 
[03:12:17] (Read 4621137 bytes from disk) 
[03:12:20] Error: Got status code 503 from server 
[03:12:20] + Could not connect to Work Server (results) 
[03:12:20] (171.65.103.100:8080) 
[03:12:20] Could not transmit unit 07 to Collection server; keeping in queue. 
 

(In this instance, the user has 2 WUs that are unable to be sent.)

In some cases, the WU is actually submitted, but the client is not receiving acknowledgement, so it does not do its normal post-submission cleanup. The client repeatedly attempts to resubmit the same work unit.

If you keep close track of your stats and can verify that you received credit for the FIRST submission, the WU can be deleted (see below). If you aren't sure, post the line like this from your fahlog.txt file (in this format, please)

Project: 2124 (Run 172, Clone 23, Gen 14) 
 

sortofageek See Profile (or any Folding Community Forum moderator) can query the stats database to check on submitted WUs. If she replies that the WU has been successfully received and credited, you can delete the wuresults_xx.dat file, where xx is the unit number referenced in the error messages.

A thread discussing one instance of this issue is here.

by antbhill2 See Profile edited by sortofageek See Profile
last modified: 2007-08-31 14:20:23

When attempts to send the work unit (WU) to the server fail, the program will queue the WU results so that they are not lost. The same problem that caused the upload to fail may also cause the "get work" to fail. If Ctrl+C will not shut down the program, it is safe at this time to use the "x" in the window's upper right corner to close the window or click the upper left corner of the window and select close to stop the program. When the problem is corrected, restart the program and no data will have been lost.

by DSmithLady See Profile edited by nozero See Profile
last modified: 2005-08-07 17:36:30

By all means post in the forum, but please try the suggestions here first.

by sortofageek See Profile

If you know your internet connection is up, have checked and found the problem is not the Stanford servers, try reconfiguring your client for this particular setting:

Use Internet Explorer Settings [no] (yes/no)?
If your client is currently configured with a no answer to this question, change that setting to yes and try again. If your client is configured as yes, change to no and retry.

by sortofageek See Profile
last modified: 2005-11-14 21:43:36

You can find some of those here, along with the known reasons they occur.

Common Folding@Home Errors

by sortofageek See Profile
last modified: 2008-04-27 13:56:33

Yes, you can learn about the different ones here.

EUE Types

by sortofageek See Profile
last modified: 2008-05-16 03:28:14

If you notice a work unit does not upload after completion, check the FAHlog.txt file in your F@H folder for an error message like this:

[03:30:41] - Server reports digital signature does not match.
[03:30:41] (May be due to corruption during network transmission or a corrupted file.)
[03:30:41] - Error: Could not transmit unit 02 (completed May 13). Keeping unit in queue.


The most likely cause is running an older version of the F@H client. If this is the case, download the latest final client. Shut down the client properly just after the end of a completed frame. Place the new client in your F@H folder. Be sure to change the shortcut to point to this new client's executable file. Restart the client. The work unit(s) in the queue should then go home.

If your client will not connect after the upgrade, please see the following FAQs:

After upgrading, my client won't connect? (#10217)

The client software will not connect to Stanford servers? (#9672)

For some history in regard to our experience with this error so far, look here: [FAH] Server reports digital signature does not match

by sortofageek See Profile edited by nozero See Profile
last modified: 2005-08-07 17:37:27

There is a list of core status codes and what they might indicate here.

by sortofageek See Profile

You can find information about that here.

by sortofageek See Profile


LINCS warning followed by an Early WU End message is an indication that progress of a Work Unit was terminated due to Simulation Instability. Following log entries show this message:


[01:20:01] Completed 132000 out of 200000 steps (66)
[01:20:05] + Writing 'sec_per_frame = 1050.500000' to config
[01:20:05] + Working ...Timered checkpoint triggered.
[01:43:59] Quit 101 - Fatal error:
[01:43:59] Step 133288, time 266.576 (ps) LINCS WARNING

[01:43:59] relative constraint deviation after LINCS:
[01:43:59] max 0.000464 (between atoms 70341 and 70343) rms 0.000007
[01:43:59]
[01:43:59] Simulation instability has been encountered. The run has entered a
[01:43:59] state from which no further progress can be made.

[01:43:59] If you often see other project units terminating early like this
[01:43:59] too, you may wish to check the stability of your computer (issues
[01:43:59] such as high temperature, overclocking, etc.).
[01:43:59] Going to send back what have done.
[01:43:59] logfile size: 76172
[01:43:59] - Writing 76858 bytes of core data to disk...
[01:43:59] ... Done.
[01:43:59]
[01:43:59] Folding@home Core Shutdown: EARLY_UNIT_END
[01:44:04] CoreStatus = 72 (114)
[01:44:04] Sending work to server

[01:44:04] + Attempting to send results
[01:44:04] - Reading file work/wuresults_02.dat from core
[01:44:04] (Read 76858 bytes from disk)
[01:44:09] - Uploaded at ~15 kB/s
[01:44:09] - Averaged speed for that direction ~36 kB/s
[01:44:09] + Results successfully sent
[01:44:09] Thank you for your contribution to Folding@Home.


In this case a WU ended early, however partial results were sent to Stanford for partial credit.

This happens due to bad work units as Larry the weatherman explains this thread: /forum/remark,11699582~mode=flat


by pervez8 See Profile edited by nozero See Profile
last modified: 2005-08-07 17:38:04

+ Attempting to get work packet
- Connecting to assignment server
- Error: Getwork failed, and no other work to do
Sleeping for about x minutes then retrying

Possible problems:

    •Your Internet connection is down.

    •Network congestion on the Internet or at Stanford.

    •A network component is down on the Internet.

    •One or more Folding servers are down.


The client will continue to retry until that particular server has been re-started or the assignment server switches you to another available work server after about 20 minutes.

You can, in the meantime, try stopping and re-starting the client several times, maybe more!

There is a trick, from the FAH olden days, that still works for FAH (most of the time) if you have a dynamic WAN IP address:

    •Shutdown the client.

    •Force an WAN IP address change.

    •Re-start the client. Again, it may require several shutdowns and re-starts.



by Gizmo See Profile edited by nozero See Profile
last modified: 2005-08-07 17:37:46

+ Attempting to send results
- Connecting to server (171.64.122.xxx)
- Error: Could not transmit unit xx. Keeping unit in queue.

The client will attempt to transmit a complete WU twice before it moves on and downloads a new work unit for processing. The results will be kept in the work folder until the next time it has to transmit another WU. Once the client completes the WU, it will attempt to send all queued work again! You can force a retry, by stopping and re-starting the client! The client will retry sending the queued work units every six hours. There is more info in this thread.

Possible problems:


    •Your Internet connection is down.

    •Network congestion on the Internet or at Stanford.

    •A network component is down on the Internet.

    •One or more Folding servers are down.



Troubleshooting Tips from the community folding forum as of October 21, 2008:

quote:
If it's an upload problem and the server appears to be functioning normally, (for windows only:) be sure that Use_IE_Settings is set to NO.

If it's an upload problem and the server appears to be in trouble, the client is designed to deal with this issue. After the first couple of upload attempts, it should try both the Work Server for that project and a Collection Server. If both fail, the client will keep the result in the local queue and will re-attempt the upload periodically without need for you to intervene. If you're running a firewall that is designed to block spyware, be sure that the FAH client can contact the internet (or disable the outgoing firewall briefly to confirm if that's the problem). If the upload attempts have continued to fail for some time, please add the -verbosity 9 flag to your client and post the section of FAHlog.txt that shows the errors.

If you get a message "Server does not have record of this unit" don't worry about it. Each WU has to be uploaded to a primary Work Server. If that server is busy or down, the client will attempt to upload to a Collection Server. Normally the Collection Server has a list of all or almost all of the WUs that it can accept. If that list was incomplete at the time the Work Server went down, the remaining WUs will need to wait for the Work Server to be on-line again. Normally that is only a very small percentage of the outstanding WUs.

NOTE: Virtually all upload problems involve two servers. The first one is your primary Work Server for that project and is where the WU will eventually reside. The second one is called a Collection Server (CS). It is a backup server designed to accept uploads when the primary Work Server is overloaded or down. If serverstat indicates that your Collection Server is operating but heavily loaded, that means one or more of the Work Servers are not accepting their share of uploads. The CS can get overloaded quite easily and nothing can really be done about that. Of course, if it's not operating properly, it should be reported, but main focus of any error report should be on getting the primary Work Server repaired and able to accept the uploads so nobody has to revert to the CS.


by Gizmo See Profile edited by sortofageek See Profile
last modified: 2008-10-21 15:10:16

The most likely cause of this, is that the GUI client uses OpenGL and it is not included in some of the older video drivers.

To fix it, you will need to update the drivers for your video card and you may have to update the Microsoft DirectX drivers as well.

Even with the updated drivers applied, other users are still experiencing problems with the GUI client crashing occasionally. Stanford is aware and is looking into what might be causing these crashes.

The alternative is to use the console client.

by Gizmo See Profile edited by nozero See Profile
last modified: 2005-08-07 17:38:57

Determining CPU usage.
Determining the number of available cores or logical processors.
Installing the SMP client.
Installing additional clients on older and slower Multi-Core Processors.

CPU usage.

    •Right click on the 'Task Bar' at the bottom of your screen.
    •Left click and select 'Start Task Manager'.

The CPU usage is displayed at the bottom of the Task Manager window.



The number of cores or logical processors.

    •Left click on 'Start".
    •Left click on 'All Programs'.
    •Left click on 'Accessories'.
    •Left click on 'System Tools'.
    •Left click on 'System Information'.

Under Item 'Processors', the number of cores and/or logical processors are displayed.



Installing the SMP client on Multi-Core Processors.


Your system must have a recent dual core processor or better to run this client with the -smp switch in SMP mode. Four cores or more are strongly recommended. This means older single core processors cannot run this client with the -smp switch, and older dual cores will not meet the very short work unit deadlines. If after running this client with the -smp switch on an older dual or an older quad core system, and the client does not meet the work unit preferred deadline, please remove the SMP client and replace it with one or more instances of this preferred CPU client technique and/or GPU client. For more information, please read this installation guide. Windows XP or newer is required to run v6.x clients or later. and .NET 2.0 or newer is required in XP to run the SMP client. Windows Vista and newer meet both of these requirements. Windows 2000 is not supported.



You must first stop and delete the current running client. Consider waiting until the current Work Unit completes and then simultaneously depress the 'Ctrl' key with the 'c' key while in the console window. Then delete your FAH folder and all of its contents. If you were running the FAH client as a service you may also have to uninstall it via your Windows 'Control Panel'.



First, create a new folder for the FAH SMP client. In Windows Vista and Windows 7, this location is suggested: C:\Users\[username]\FAH - Please do NOT install the SMP client in C:\FAH or C:\Program Files\FAH to avoid issues with permissions. Vista/7 have new security restrictions (not in Win XP) that prevent the client from running. In Windows XP, this location is suggested: C:\FAH.



Download and open the v6.34 (or v7 Beta) SMP client executable file to the folder you just created from the instructions found Here.



To make the next steps easier to follow, renaming the client executable to something shorter, easy to remember, and install using the system console is suggested. Right-click on the executable file, select Rename and change it to 'fah6' or 'fah7' if you chose the newer beta version.



Note: Depending on the file name and folder display settings, the file extension may or may not be shown. Rename Folding@home-Win32-x86 to fah6 or rename Folding@home-Win32-x86.exe to fah6.exe.



You may want to consider a passkey at this point. It is recommended and you can acquire more points for each WU. Find out about how to get a passkey Here.



The next step is to configure the client. Open a Command Prompt and change the directory to the location where you unzipped the FAH SMP client. For example: ...>cd C:\Users\admin\fah



Type this in the command prompt to begin (assuming you renamed the FAH executable to "fah6" or "fah6.exe" depending on the file view settings as noted above):


At the prompt: C:\Users\[your user name]\FAH

Enter:

fah6 -configonly -smp

The client will display some information and then prompt you for answers to configuration questions. Note that for most answers, the default setting is the recommended setting. Here is an example of what is displayed on screen, with an explanation of each option:



[16:25:22] Configuring Folding@Home...

User Name [Anonymous]?

Enter your FAH User Name (not the Windows user name). Or press enter to accept the default user name Anonymous. Almost everyone selects a personalized user name.

Team Number [0]? 4

Enter your FAH Team #. We are Team Number 4.

Passkey []?

Enter your passkey, or press enter to leave it blank and go to the next option. Use of a passkey is optional. However, a passkey is required to be eligible for the quick return bonus on SMP2 work units.

Ask before fetching/sending work (no/yes) [no]?

Because of the short deadlines on SMP work assignments, persistent connections are strongly recommended and this option should be set to no.

Use proxy (yes/no) [no]?

If you are connected to a proxy, enter yes and configure the proxy options for proxy user name, password, address, etc. Or press enter to skip.

Acceptable size of work assignment and work result packets (bigger units
may have large memory demands) -- 'small' is <5MB, 'normal' is <10MB, and
'big' is >10MB (small/normal/big) [normal]? big


This option states a preference for the size of work units downloaded and uploaded to the project servers. Note that all SMP WUs are large in size, so big is the required setting. Bigger units will also have bigger memory requirements. If you run on a slower broadband or dialup internet connection, small is the recommended setting to ease your bandwidth usage and you may want to switch to the CPU client instead.

Change advanced options (yes/no) [no]? yes

If you want to change the advanced options, enter yes. It is not mandatory but is recommended for SMP installs.

Core Priority (idle/low) [idle]?

This adjusts the FAH client priority level. This is similar to, but not the same as the Windows priority setting. In most cases, the default idle setting is recommended.
Note: For better performance when mixing CPU or SMP clients with GPU clients, raise the priority of the GPU clients by selecting the low priority setting. Do NOT change the Windows priority settings for the client or fahcore.

CPU usage requested (5-100) [100]?

This will adjust the percentage of CPU usage. The FAH client only uses spare CPU cycles not used by other programs, so reducing this setting is not typically necessary. However, if you want to lower system temperatures, or reserve CPU cycles for more intensive computer tasks, enter a number below 100. In the SMP client, changing this setting does not reduce CPU usage.

Disable highly optimized assembly code (no/yes) [no]?

If you are having issues running the client, disable this. For 99.9% of the users, leave this at the default setting since this reduces the client performance a lot.

Pause if battery power is being used (useful for laptops) (no/yes) [no]?

If you run a laptop, set this to yes to pause if the laptop is not plugged into the wall. This will avoid the client draining the battery.

Interval, in minutes, between checkpoints (3-30) [15]?

Number of minutes between each checkpoint where the client is writing the client progress to disk in case of unexpected interruption. 15 is the recommended setting.

Memory, in MB, to indicate (1013 available) [1013]?

Sets the amount of memory seen by the work servers. By default, it shows the full system memory amount. Note that reducing this setting does not reserve more memory for other programs. However, reducing this setting will prevent the client from downloading memory intensive work units. A setting too low may prevent the client from getting any new work. In the SMP client, .5 GB per CPU core is the minimum, while 1 GB per core is recommended.

Machine ID (1-16) [1]?

This is not applicable for the SMP client.

Launch automatically, install as a service in this directory (yes/no) [no]?

If you want the client to run as a service, say yes and it will install a new entry in the services list. The next time you restart the computer, the service will start automatically and run in the background. SMP as a service is only supported in v6.30 and newer.
Note: The current Windows user account must have Administrator privileges to install FAH as a service. And rebooting the computer to start the client running as a service is required.

The following options require you to restart the client before they take effect Disable CPU affinity lock (no/yes) [no]?

Not useful for SMP since it uses all cores.

Additional client parameters []? -smp

You can enter the client flags here so you don't have to type the flag each time you run the client. We strongly suggest you enter the -smp flag, especially when running as a service. Do NOT enter -config or -configonly or any single-use flag in this field to avoid problems.

IP address to bind core to (for viewer) []?

For future use when the Viewer is working better. Specifies the IP address of the machine of which the viewer should display the client output.

When you press enter after the last question, the configuration will end and you will be back to the command prompt. You have successfully configured the client so the next step is to start the client. Here are 3 ways:

1. By clicking on the executable icon (this assumes you entered the proper flags during configuration).
2. By typing fah6 on the same command prompt window. Enter the necessary flags (including the mandatory -smp flag) if you didn't enter those during configuration.
3. Create a new shortcut to the FAH executable, and double click that shortcut icon (assuming you added all needed flags to the client setup).
4. Create a new shortcut to the FAH executable and add it to your 'Startup' file.

Normally, if everything is done correctly, the client will be folding along fine. To verify the client is progressing, open the task manager and make sure there is one instance of the multi-threaded FahCore_a3.exe in the list. Or you can open the fahlog.txt file to see the client's progress.



Installing additional clients on older Multi-core processors.


For each additional core or logical processor you must create an additional FAH folder. As you created your original FAH client in folder C:\FAH, you must now create C:\FAH2, C:\FAH3, etc. for each logical processor that you wish to run the client on.

Use the original procedure that you followed for your first client and duplicate the installation procedure that you followed Here with these exceptions:

At the installation question for:

Change advanced options [no] (yes/no)? yes

Answer yes, and then at:

Machine ID (1-8) [1]? 2

Answer 2 for a dual core processor. For every additional core for which you will be running another client you must increment the Machine ID by +1



by Scilicet See Profile edited by sortofageek See Profile
last modified: 2012-05-15 18:02:53