folding stopped last month

[tadcook]

I've been running f@h for over six months, but somehow last month it stopped delivering any more work.

I tried uninstalling and re-installing the client, but no change.

If anyone can recommend tests to run or troubleshooting steps, I would appreciate it.

Below are hardware details and a log.

Windows 10 Pro, v1511
8 GB RAM
Intel i7-4790 CPU 64 bit, 3.6 GHz, quad-core
DSL network connection
Running latest version of folding@home

Code: Select all

06:51:24:
06:51:24:  <!-- Slot Control -->
06:51:24:  <power v='full'/>
06:51:24:
06:51:24:  <!-- User Information -->
06:51:24:  <team v='10566'/>
06:51:24:  <user v='K7RA'/>
06:51:24:
06:51:24:  <!-- Folding Slots -->
06:51:24:  <slot id='0' type='CPU'/>
06:51:24:</config>
06:51:24:Trying to access database...
06:51:24:Successfully acquired database lock
06:51:24:Enabled folding slot 00: READY cpu:8
06:51:25:WARNING:WU01:FS00:Past final deadline 2016-05-04T17:39:46Z, dumping
06:51:25:WU01:FS00:Cleaning up
06:51:25:WU00:FS00:Starting
06:51:25:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/ProgramData/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 704 -lifeline 2064 -checkpoint 15 -np 8 -service
06:51:25:WU00:FS00:Started FahCore on PID 3244
06:51:25:WU00:FS00:Core PID:3292
06:51:25:WU00:FS00:FahCore 0xa4 started
06:51:26:WU00:FS00:0xa4:
06:51:26:WU00:FS00:0xa4:*------------------------------*
06:51:26:WU00:FS00:0xa4:Folding@Home Gromacs GB Core
06:51:26:WU00:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
06:51:26:WU00:FS00:0xa4:
06:51:26:WU00:FS00:0xa4:Preparing to commence simulation
06:51:26:WU00:FS00:0xa4:- Looking at optimizations...
06:51:26:WU00:FS00:0xa4:- Created dyn
06:51:26:WU00:FS00:0xa4:- Files status OK
06:51:26:WU00:FS00:0xa4:- Expanded 1216882 -> 2905520 (decompressed 238.7 percent)
06:51:26:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=1216882 data_size=2905520, decompressed_data_size=2905520 diff=0
06:51:26:WU00:FS00:0xa4:- Digital signature verified
06:51:26:WU00:FS00:0xa4:
06:51:26:WU00:FS00:0xa4:Project: 11639 (Run 1, Clone 296, Gen 8)
06:51:26:WU00:FS00:0xa4:
06:51:26:WU00:FS00:0xa4:Assembly optimizations on if available.
06:51:26:WU00:FS00:0xa4:Entering M.D.
06:51:32:WU00:FS00:0xa4:Mapping NT from 8 to 8 
06:51:32:WU00:FS00:0xa4:Completed 0 out of 1250000 steps  (0%)
06:55:46:WU00:FS00:0xa4:Completed 12500 out of 1250000 steps  (1%)
06:59:56:WU00:FS00:0xa4:Completed 25000 out of 1250000 steps  (2%)
07:04:00:WU00:FS00:0xa4:Completed 37500 out of 1250000 steps  (3%)
07:08:03:WU00:FS00:0xa4:Completed 50000 out of 1250000 steps  (4%)
07:11:59:WU00:FS00:0xa4:Completed 62500 out of 1250000 steps  (5%)
07:15:46:WU00:FS00:0xa4:Completed 75000 out of 1250000 steps  (6%)
07:19:37:WU00:FS00:0xa4:Completed 87500 out of 1250000 steps  (7%)
07:23:25:WU00:FS00:0xa4:Completed 100000 out of 1250000 steps  (8%)

Mod edit: added Code tags to log file

[Joe_H]

Welcome to the folding support forum.

The portion of your log file shows your client picking up a WU after dumping the previous one which was past its final deadline. It is not enough to give any information as to why you apparently were not getting assignments. That information is possibly available in the older logs saved in the F@H data folder.

Additional useful information is the beginning section of your log that you have clipped off. That shows the system information as the client sees it.

P.S. The log also shows that you have not entered a passkey. That is not required, but without a passkey you only get the base points and no bonus points for completing a WU quickly.

[bruce]

Code: Select all

06:51:24:Enabled folding slot 00: READY cpu:8
06:51:25:WARNING:WU01:FS00:Past final deadline 2016-05-04T17:39:46Z, dumping

FAH assignments have firm deadlines. If it's assigned to someone who does not complete it before it expires, it will be assigned to someone else to prevent that series of assignments from stalling.

For a WU to expire on a system that has 8 CPUs, you must be folding only a few hours a week. It's likely that if you computer is on and FAH is running a bit more, you'll make the deadlines and your credits will resume.

(With detailed logs, it would be easier to determine if my guess is accurate.)

[tadcook]

I have the machine running 24x7, and when folding was still working it seemed this machine was delivering a lot of work.

I didn't realize I hadn't posted the entire log. Here it is:

Code: Select all

*********************** Log Started 2016-04-23T04:57:12Z ***********************
04:57:12:************************* Folding@home Client *************************
04:57:12:      Website: http://folding.stanford.edu/
04:57:12:    Copyright: (c) 2009-2014 Stanford University
04:57:12:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
04:57:12:         Args: 
04:57:12:       Config: <none>
04:57:12:******************************** Build ********************************
04:57:12:      Version: 7.4.4
04:57:12:         Date: Mar 4 2014
04:57:12:         Time: 20:26:54
04:57:12:      SVN Rev: 4130
04:57:12:       Branch: fah/trunk/client
04:57:12:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
04:57:12:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
04:57:12:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
04:57:12:     Platform: win32 XP
04:57:12:         Bits: 32
04:57:12:         Mode: Release
04:57:12:******************************* System ********************************
04:57:12:          CPU: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
04:57:12:       CPU ID: GenuineIntel Family 6 Model 60 Stepping 3
04:57:12:         CPUs: 8
04:57:12:       Memory: 7.88GiB
04:57:12:  Free Memory: 5.18GiB
04:57:12:      Threads: WINDOWS_THREADS
04:57:12:   OS Version: 6.2
04:57:12:  Has Battery: false
04:57:12:   On Battery: false
04:57:12:   UTC Offset: -7
04:57:12:          PID: 8488
04:57:12:          CWD: C:/Program Files (x86)/FAHClient
04:57:12:           OS: Windows 10 Pro
04:57:12:      OS Arch: AMD64
04:57:12:         GPUs: 0
04:57:12:         CUDA: Not detected
04:57:12:Win32 Service: false
04:57:12:***********************************************************************
04:57:12:<config>
04:57:12:  <!-- Folding Slots -->
04:57:12:</config>
04:57:12:Connecting to assign-GPU.stanford.edu:80
04:57:12:Updated GPUs.txt
04:57:12:Read GPUs.txt
04:57:12:Trying to access database...
04:57:12:Successfully acquired database lock
04:57:12:Enabled folding slot 00: PAUSED cpu:7 (not configured)
04:58:13:Saving configuration to config.xml
04:58:13:<config>
04:58:13:  <!-- Folding Slots -->
04:58:13:  <slot id='0' type='CPU'/>
04:58:13:</config>
04:58:13:Set client configured
04:58:13:WU00:FS00:Connecting to 171.67.108.45:8080
04:58:13:WU00:FS00:Connecting to 171.67.108.45:8080
04:58:14:WU00:FS00:Assigned to work server 171.67.108.158
04:58:14:WU00:FS00:Requesting new work unit for slot 00: READY cpu:7 from 171.67.108.158
04:58:14:WU00:FS00:Connecting to 171.67.108.158:8080
04:58:15:WU00:FS00:Downloading 807.14KiB
04:58:16:WU00:FS00:Download complete
04:58:16:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:9038 run:166 clone:1 gen:50 core:0xa4 unit:0x00000044ab436c9e56982a2223ee0009
04:58:16:WU00:FS00:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah
04:58:16:WU00:FS00:Connecting to web.stanford.edu:80
04:58:16:WU00:FS00:FahCore a4: Downloading 2.89MiB
04:58:20:WU00:FS00:FahCore a4: Download complete
04:58:20:WU00:FS00:Valid core signature
04:58:20:WU00:FS00:Unpacked 9.59MiB to cores/web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe
04:58:21:WU00:FS00:Starting
04:58:21:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" "C:/Program Files (x86)/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe" -dir 00 -suffix 01 -version 704 -lifeline 8488 -checkpoint 15 -np 7
04:58:21:WU00:FS00:Started FahCore on PID 6352
04:58:21:WU00:FS00:Core PID:7180
04:58:21:WU00:FS00:FahCore 0xa4 started
04:58:21:WU00:FS00:0xa4:
04:58:21:WU00:FS00:0xa4:*------------------------------*
04:58:21:WU00:FS00:0xa4:Folding@Home Gromacs GB Core
04:58:21:WU00:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
04:58:21:WU00:FS00:0xa4:
04:58:21:WU00:FS00:0xa4:Preparing to commence simulation
04:58:21:WU00:FS00:0xa4:- Looking at optimizations...
04:58:21:WU00:FS00:0xa4:- Created dyn
04:58:21:WU00:FS00:0xa4:- Files status OK
04:58:21:WU00:FS00:0xa4:- Expanded 825998 -> 1402860 (decompressed 169.8 percent)
04:58:21:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=825998 data_size=1402860, decompressed_data_size=1402860 diff=0
04:58:21:WU00:FS00:0xa4:- Digital signature verified
04:58:21:WU00:FS00:0xa4:
04:58:21:WU00:FS00:0xa4:Project: 9038 (Run 166, Clone 1, Gen 50)
04:58:21:WU00:FS00:0xa4:
04:58:21:WU00:FS00:0xa4:Assembly optimizations on if available.
04:58:21:WU00:FS00:0xa4:Entering M.D.
04:58:27:WU00:FS00:0xa4:Mapping NT from 7 to 7 
04:58:27:WU00:FS00:0xa4:Completed 0 out of 250000 steps  (0%)
04:59:52:WU00:FS00:0xa4:Completed 2500 out of 250000 steps  (1%)
05:00:43:WARNING:Console control signal 2 on PID 8488
05:00:43:Exiting, please wait. . .

Mod edit: added Code tags to log file

[tadcook]

Welcome to the folding support forum.

The portion of your log file shows your client picking up a WU after dumping the previous one which was past its final deadline. It is not enough to give any information as to why you apparently were not getting assignments. That information is possibly available in the older logs saved in the F@H data folder.

I see only one log, and it is in C:\Program Files(x86)\FAHClient\logs\

I don't see any folder marked "F@H data".

[Joe_H]

From the log it appears that you did not follow the recommended method for installing the F@H client. The log files and other data files would normally be located in a path similar to this - C:/Users/Anonymous/AppData/Roaming/FAHClient, and not under C:/Program Files (x86)/FAHClient. Older logs would be located in a folder called 'logs'. There may be permissions problems with the client files stored under the Program Files location, so the log file folder may or may not be there.

[bruce]

Microsoft requires special permissions to put programs in the \Program Files* directory. (I suppose it's an attempt to minimize the possibility of a malware attack.) Good programming practice suggests that data should always be separate from programs. The normal installation procedure puts FAH's programs there but by default, it puts the data files elsewhere, typically like Joe_H says.

Your installation should have created shortuts in a directory called \all programs\FAHClient which can start FAHClient, FAHControl, Web_Control, or FAHViewer with the proper file accesses ... as well as a link to FAH's data directory. Of course if you used the installation option to start FAH automatically, you won't need to use Folding@home (aka. FAHClient) to start it manually.

If you double-click FAHClient, the data file associations will NOT be initialized properly, plus you'll need Admin privileges because you'll be attempting to create DATA files in C:\Program Files(x86)\FAHClient\logs\

More information is available at http://folding.stanford.edu/home/guide, together with links to specific instructions for each type of OS that's supported.

[tadcook]

Thanks everyone. I will reinstall.