Page 26 of 52
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Tue Jun 12, 2012 1:58 pm
by harlam357
Well... I can see how you got confused. Let me clear it up for ya.
When setting up a "local path" type legacy client all the Test Connection button does is verify that the directory that was entered does indeed exist. It does not check for client artifact files like FAHlog.txt, queue.dat, etc. that are necessary to obtain a reading from a client. Test Connection is much, much more useful when validating a connection for HTTP or FTP based legacy clients, since those define completely remote resources. In those cases an actual client connection is made to a remote server to validate the given server, path, user, pass combination; but even in those two cases the test does not attempt to validate that artifact files like FAHlog.txt, queue.dat, etc. are present. I leave knowing where to point HFM up to the user.
Glad you got it working.
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Tue Jun 12, 2012 2:46 pm
by bruce
Perhaps the message could say something like: Directory found; active client files not found.
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Thu Jun 21, 2012 2:11 am
by compdewd
Has it been suggested that HFM could link to other 3rd party stats sites rather than just EOC? Searching didn't bring up anything of the like. The reason I ask is because EOC does not provide my stats because I am part of team 0 and am out of the first 2000 that it keeps track of. Kakao Stats does keep track of me so it would be nice if HFM could include them as an option as well
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Thu Jun 21, 2012 4:20 am
by GreyWhiskers
Another suggestion. It seems like the HFM WU History Viewer revalues its database each time it comes up with the then-current ProjectSummary data. There was a recent event where an SMP Project had its deadline shortened because the QRB was overly generous. It seems that HFM WU History Viewer recomputed all the already completed projects with the new ProjSummary values.
Does the V7 Client interface pass on the actual points, as reported in the log, to the remote client interface software? If so, could that be permanently stored in the HFM Database vs. recomputing?
Great, great product - I feel I have a much better oversight into how my folding farm is doing.
GW.
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Fri Jun 22, 2012 12:04 pm
by Fahrenheit451
I think I found a bug, but I'm not sure if it is a HFM or a FAH client bug:
Since I have removed my GPU (GTX 560Ti) from my 2nd system (i7 2600) due to a faulty air cooler, HFM (v0.9.0) shows a strange behavior for this system.
All information about the processed (SMP) WU incl. download date, ETA and estimated points, etc. are shown correct, except the status bar and the no. of completed WUs. The value for the completed WUs stay at 0 and the status bar seems sometimes to show the correct progress and sometimes it stay at 0% even if the WU is nearly finished. Is it depending on the WU, if the status bar shows the correct progress? I never saw this behavior before.
The FAH client is v7.1.50 and runs on a Win 7 Ultimate 64 machine. HFM access this client from a remote machine (Win Vista Ultimate 32).
Currently I don't have connected the Win 7 machine with a display using the IGP of the i7, and use only a VNC viewer. Could this be the reason?
Or is HFM confused by the v7 client? I checked the log file of the v7 client and it reports for the former GPU slot four times per second: "ERROR:Exception: Option 'gpu-index' has no default and is not set.". The part of logfile for the SMP client (slot 1) now jumps only between WU00 and WU01 since the last WU02 has been finished. WU02 was started before I had to remove the gfx card and when both clients (GPU and SMP) were folding. Please find below the part of the logfile for the SMP WUs.
Code: Select all
*********************** Log Started 2012-06-20T07:20:43Z ***********************
07:20:43:WU02:FS01:Starting
07:20:43:WU02:FS01:Running FahCore: D:\FAHClient_V7/FAHCoreWrapper.exe C:/ProgramData/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 02 -suffix 01 -version 701 -lifeline 2412 -checkpoint 15 -np 8
07:20:43:WU02:FS01:Started FahCore on PID 2028
07:20:43:WU02:FS01:Core PID:884
07:20:43:WU02:FS01:FahCore 0xa4 started
07:20:44:WU02:FS01:0xa4:
07:20:44:WU02:FS01:0xa4:*------------------------------*
07:20:44:WU02:FS01:0xa4:Folding@Home Gromacs GB Core
07:20:44:WU02:FS01:0xa4:Version 2.27 (Dec. 15, 2010)
07:20:44:WU02:FS01:0xa4:
07:20:44:WU02:FS01:0xa4:Preparing to commence simulation
07:20:44:WU02:FS01:0xa4:- Ensuring status. Please wait.
07:20:53:WU02:FS01:0xa4:- Looking at optimizations...
07:20:53:WU02:FS01:0xa4:- Working with standard loops on this execution.
07:20:53:WU02:FS01:0xa4:- Previous termination of core was improper.
07:20:53:WU02:FS01:0xa4:- Going to use standard loops.
07:20:53:WU02:FS01:0xa4:- Files status OK
07:20:53:WU02:FS01:0xa4:- Expanded 56161 -> 211504 (decompressed 376.6 percent)
07:20:53:WU02:FS01:0xa4:Called DecompressByteArray: compressed_data_size=56161 data_size=211504, decompressed_data_size=211504 diff=0
07:20:53:WU02:FS01:0xa4:- Digital signature verified
07:20:53:WU02:FS01:0xa4:
07:20:53:WU02:FS01:0xa4:Project: 7012 (Run 0, Clone 159, Gen 32)
07:20:53:WU02:FS01:0xa4:
07:20:53:WU02:FS01:0xa4:Entering M.D.
07:20:59:WU02:FS01:0xa4:Using Gromacs checkpoints
07:20:59:WU02:FS01:0xa4:Mapping NT from 8 to 8
07:20:59:WU02:FS01:0xa4:Resuming from checkpoint
07:20:59:WU02:FS01:0xa4:Verified 02/wudata_01.log
07:20:59:WU02:FS01:0xa4:Verified 02/wudata_01.trr
07:20:59:WU02:FS01:0xa4:Verified 02/wudata_01.xtc
07:20:59:WU02:FS01:0xa4:Verified 02/wudata_01.edr
07:20:59:WU02:FS01:0xa4:Completed 4500001 out of 10000000 steps (45%)
<SNIP>
09:22:01:WU02:FS01:0xa4:Completed 9900000 out of 10000000 steps (99%)
09:22:02:WU00:FS01:Connecting to assign3.stanford.edu:8080
09:22:03:WU00:FS01:News: Welcome to Folding@Home
09:22:03:WU00:FS01:Assigned to work server 129.74.85.15
09:22:03:WU00:FS01:Requesting new work unit for slot 01: RUNNING smp:8 from 129.74.85.15
09:22:03:WU00:FS01:Connecting to 129.74.85.15:8080
09:22:03:WU00:FS01:Downloading 39.68KiB
09:22:04:WU00:FS01:Download complete
09:22:04:WU00:FS01:Received Unit: id:00 state:DOWNLOAD error:OK project:10090 run:3 clone:1 gen:144 core:0xa4 unit:0x000001450001329c4dfb5126046f1812
09:22:04:WU00:FS01:Downloading project 10090 description
09:22:04:WU00:FS01:Connecting to fah-web.stanford.edu:80
09:22:04:WU00:FS01:Project 10090 description downloaded successfully
09:24:13:WU02:FS01:0xa4:Completed 10000000 out of 10000000 steps (100%)
09:24:13:WU02:FS01:0xa4:DynamicWrapper: Finished Work Unit: sleep=10000
09:24:23:WU02:FS01:0xa4:
09:24:23:WU02:FS01:0xa4:Finished Work Unit:
09:24:23:WU02:FS01:0xa4:- Reading up to 2179176 from "02/wudata_01.trr": Read 2179176
09:24:23:WU02:FS01:0xa4:trr file hash check passed.
09:24:23:WU02:FS01:0xa4:- Reading up to 225804 from "02/wudata_01.xtc": Read 225804
09:24:23:WU02:FS01:0xa4:xtc file hash check passed.
09:24:23:WU02:FS01:0xa4:edr file hash check passed.
09:24:23:WU02:FS01:0xa4:logfile size: 80017
09:24:23:WU02:FS01:0xa4:Leaving Run
09:24:23:WU02:FS01:0xa4:- Writing 2509469 bytes of core data to disk...
09:24:24:WU02:FS01:0xa4:Done: 2508957 -> 1966027 (compressed to 78.3 percent)
09:24:24:WU02:FS01:0xa4: ... Done.
09:24:24:WU02:FS01:0xa4:- Shutting down core
09:24:24:WU02:FS01:0xa4:
09:24:24:WU02:FS01:0xa4:Folding@home Core Shutdown: FINISHED_UNIT
09:24:25:WU02:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
09:24:25:WU02:FS01:Sending unit results: id:02 state:SEND error:OK project:7012 run:0 clone:159 gen:32 core:0xa4 unit:0x0000004d0001329c4dfb980c5dc84cd5
09:24:25:WU02:FS01:Uploading 1.88MiB to 129.74.85.15
09:24:25:WU02:FS01:Connecting to 129.74.85.15:8080
09:24:25:WU00:FS01:Starting
09:24:25:WU00:FS01:Running FahCore: D:\FAHClient_V7/FAHCoreWrapper.exe C:/ProgramData/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 701 -lifeline 2412 -checkpoint 15 -np 8
09:24:25:WU00:FS01:Started FahCore on PID 3700
09:24:25:WU00:FS01:Core PID:4676
09:24:25:WU00:FS01:FahCore 0xa4 started
09:24:25:WU00:FS01:0xa4:
09:24:25:WU00:FS01:0xa4:*------------------------------*
09:24:25:WU00:FS01:0xa4:Folding@Home Gromacs GB Core
09:24:25:WU00:FS01:0xa4:Version 2.27 (Dec. 15, 2010)
09:24:25:WU00:FS01:0xa4:
09:24:25:WU00:FS01:0xa4:Preparing to commence simulation
09:24:25:WU00:FS01:0xa4:- Looking at optimizations...
09:24:25:WU00:FS01:0xa4:- Created dyn
09:24:25:WU00:FS01:0xa4:- Files status OK
09:24:25:WU00:FS01:0xa4:- Expanded 40116 -> 206316 (decompressed 514.2 percent)
09:24:25:WU00:FS01:0xa4:Called DecompressByteArray: compressed_data_size=40116 data_size=206316, decompressed_data_size=206316 diff=0
09:24:25:WU00:FS01:0xa4:- Digital signature verified
09:24:25:WU00:FS01:0xa4:
09:24:25:WU00:FS01:0xa4:Project: 10090 (Run 3, Clone 1, Gen 144)
09:24:25:WU00:FS01:0xa4:
09:24:25:WU00:FS01:0xa4:Assembly optimizations on if available.
09:24:25:WU00:FS01:0xa4:Entering M.D.
09:24:31:WU02:FS01:Upload 20.00%
09:24:31:WU00:FS01:0xa4:Mapping NT from 8 to 8
09:24:31:WU00:FS01:0xa4:Completed 0 out of 10000000 steps (0%)
09:24:37:WU02:FS01:Upload 43.32%
09:24:43:WU02:FS01:Upload 63.32%
09:24:49:WU02:FS01:Upload 83.31%
09:24:54:WU02:FS01:Upload complete
09:24:54:WU02:FS01:Server responded WORK_ACK (400)
09:24:54:WU02:FS01:Final credit estimate, 797.00 points
09:24:54:WU02:FS01:Cleaning up
09:31:19:WU00:FS01:0xa4:Completed 100000 out of 10000000 steps (1%)
<SNIP>
20:37:08:WU00:FS01:0xa4:Completed 9900000 out of 10000000 steps (99%)
20:37:09:WU01:FS01:Connecting to assign3.stanford.edu:8080
20:37:10:WU01:FS01:News: Welcome to Folding@Home
20:37:10:WU01:FS01:Assigned to work server 171.67.108.60
20:37:10:WU01:FS01:Requesting new work unit for slot 01: RUNNING smp:8 from 171.67.108.60
20:37:10:WU01:FS01:Connecting to 171.67.108.60:8080
20:37:11:WU01:FS01:Downloading 468.57KiB
20:37:14:WU01:FS01:Download complete
20:37:14:WU01:FS01:Received Unit: id:01 state:DOWNLOAD error:OK project:8046 run:34 clone:46 gen:7 core:0xa4 unit:0x000000076652edcc4fd9362a9909049c
20:43:57:WU00:FS01:0xa4:Completed 10000000 out of 10000000 steps (100%)
20:43:57:WU00:FS01:0xa4:DynamicWrapper: Finished Work Unit: sleep=10000
20:44:07:WU00:FS01:0xa4:
20:44:07:WU00:FS01:0xa4:Finished Work Unit:
20:44:07:WU00:FS01:0xa4:- Reading up to 2128272 from "00/wudata_01.trr": Read 2128272
20:44:07:WU00:FS01:0xa4:trr file hash check passed.
20:44:07:WU00:FS01:0xa4:- Reading up to 118776 from "00/wudata_01.xtc": Read 118776
20:44:07:WU00:FS01:0xa4:xtc file hash check passed.
20:44:07:WU00:FS01:0xa4:edr file hash check passed.
20:44:07:WU00:FS01:0xa4:logfile size: 81902
20:44:07:WU00:FS01:0xa4:Leaving Run
20:44:09:WU00:FS01:0xa4:- Writing 2353422 bytes of core data to disk...
20:44:10:WU00:FS01:0xa4:Done: 2352910 -> 12799 (compressed to 0.5 percent)
20:44:10:WU00:FS01:0xa4: ... Done.
20:44:10:WU00:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
20:44:10:WU00:FS01:Sending unit results: id:00 state:SEND error:OK project:10090 run:3 clone:1 gen:144 core:0xa4 unit:0x000001450001329c4dfb5126046f1812
20:44:10:WU00:FS01:Uploading 13.00KiB to 129.74.85.15
20:44:10:WU00:FS01:Connecting to 129.74.85.15:8080
20:44:10:WU01:FS01:Starting
20:44:10:WU01:FS01:Running FahCore: D:\FAHClient_V7/FAHCoreWrapper.exe C:/ProgramData/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 01 -suffix 01 -version 701 -lifeline 2412 -checkpoint 15 -np 8
20:44:10:WU01:FS01:Started FahCore on PID 3868
20:44:10:WU01:FS01:Core PID:1044
20:44:10:WU01:FS01:FahCore 0xa4 started
20:44:11:WU00:FS01:Upload complete
20:44:11:WU00:FS01:Server responded WORK_ACK (400)
20:44:11:WU00:FS01:Final credit estimate, 2503.00 points
20:44:11:WU00:FS01:Cleaning up
20:44:11:WU01:FS01:0xa4:
20:44:11:WU01:FS01:0xa4:*------------------------------*
20:44:11:WU01:FS01:0xa4:Folding@Home Gromacs GB Core
20:44:11:WU01:FS01:0xa4:Version 2.27 (Dec. 15, 2010)
20:44:11:WU01:FS01:0xa4:
20:44:11:WU01:FS01:0xa4:Preparing to commence simulation
20:44:11:WU01:FS01:0xa4:- Looking at optimizations...
20:44:11:WU01:FS01:0xa4:- Created dyn
20:44:11:WU01:FS01:0xa4:- Files status OK
20:44:11:WU01:FS01:0xa4:- Expanded 479300 -> 1077500 (decompressed 224.8 percent)
20:44:11:WU01:FS01:0xa4:Called DecompressByteArray: compressed_data_size=479300 data_size=1077500, decompressed_data_size=1077500 diff=0
20:44:11:WU01:FS01:0xa4:- Digital signature verified
20:44:11:WU01:FS01:0xa4:
20:44:11:WU01:FS01:0xa4:Project: 8046 (Run 34, Clone 46, Gen 7)
20:44:11:WU01:FS01:0xa4:
20:44:11:WU01:FS01:0xa4:Assembly optimizations on if available.
20:44:11:WU01:FS01:0xa4:Entering M.D.
20:44:17:WU01:FS01:0xa4:Mapping NT from 8 to 8
20:44:17:WU01:FS01:0xa4:Completed 0 out of 250000 steps (0%)
<SNIP>
21:33:37:WU01:FS01:0xa4:Completed 250000 out of 250000 steps (100%)
21:33:37:WU01:FS01:0xa4:DynamicWrapper: Finished Work Unit: sleep=10000
21:33:38:WU00:FS01:Connecting to assign3.stanford.edu:8080
21:33:38:WU00:FS01:News: Welcome to Folding@Home
21:33:38:WU00:FS01:Assigned to work server 129.74.85.15
21:33:38:WU00:FS01:Requesting new work unit for slot 01: RUNNING smp:8 from 129.74.85.15
21:33:38:WU00:FS01:Connecting to 129.74.85.15:8080
21:33:39:WU00:FS01:Downloading 53.03KiB
21:33:39:WU00:FS01:Download complete
21:33:39:WU00:FS01:Received Unit: id:00 state:DOWNLOAD error:OK project:10085 run:1 clone:7 gen:96 core:0xa4 unit:0x000001100001329c4ddbf665763d5448
21:33:40:WU00:FS01:Downloading project 10085 description
21:33:40:WU00:FS01:Connecting to fah-web.stanford.edu:80
21:33:41:WU00:FS01:Project 10085 description downloaded successfully
21:33:47:WU01:FS01:0xa4:
21:33:47:WU01:FS01:0xa4:Finished Work Unit:
21:33:47:WU01:FS01:0xa4:- Reading up to 596076 from "01/wudata_01.trr": Read 596076
21:33:47:WU01:FS01:0xa4:trr file hash check passed.
21:33:47:WU01:FS01:0xa4:- Reading up to 352964 from "01/wudata_01.xtc": Read 352964
21:33:47:WU01:FS01:0xa4:xtc file hash check passed.
21:33:47:WU01:FS01:0xa4:edr file hash check passed.
21:33:47:WU01:FS01:0xa4:logfile size: 23163
21:33:47:WU01:FS01:0xa4:Leaving Run
21:33:48:WU01:FS01:0xa4:- Writing 977791 bytes of core data to disk...
21:33:48:WU01:FS01:0xa4:Done: 977279 -> 929683 (compressed to 95.1 percent)
21:33:48:WU01:FS01:0xa4: ... Done.
21:33:48:WU01:FS01:0xa4:- Shutting down core
21:33:48:WU01:FS01:0xa4:
21:33:48:WU01:FS01:0xa4:Folding@home Core Shutdown: FINISHED_UNIT
21:33:48:WU01:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
21:33:48:WU01:FS01:Sending unit results: id:01 state:SEND error:OK project:8046 run:34 clone:46 gen:7 core:0xa4 unit:0x000000076652edcc4fd9362a9909049c
21:33:48:WU01:FS01:Uploading 908.39KiB to 171.67.108.60
21:33:48:WU01:FS01:Connecting to 171.67.108.60:8080
21:33:49:WU00:FS01:Starting
21:33:49:WU00:FS01:Running FahCore: D:\FAHClient_V7/FAHCoreWrapper.exe C:/ProgramData/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 701 -lifeline 2412 -checkpoint 15 -np 8
21:33:49:WU00:FS01:Started FahCore on PID 4024
21:33:49:WU00:FS01:Core PID:2612
21:33:49:WU00:FS01:FahCore 0xa4 started
21:33:49:WU00:FS01:0xa4:
21:33:49:WU00:FS01:0xa4:*------------------------------*
21:33:49:WU00:FS01:0xa4:Folding@Home Gromacs GB Core
21:33:49:WU00:FS01:0xa4:Version 2.27 (Dec. 15, 2010)
21:33:49:WU00:FS01:0xa4:
21:33:49:WU00:FS01:0xa4:Preparing to commence simulation
21:33:49:WU00:FS01:0xa4:- Looking at optimizations...
21:33:49:WU00:FS01:0xa4:- Created dyn
21:33:49:WU00:FS01:0xa4:- Files status OK
21:33:49:WU00:FS01:0xa4:- Expanded 53791 -> 201448 (decompressed 374.5 percent)
21:33:49:WU00:FS01:0xa4:Called DecompressByteArray: compressed_data_size=53791 data_size=201448, decompressed_data_size=201448 diff=0
21:33:49:WU00:FS01:0xa4:- Digital signature verified
21:33:49:WU00:FS01:0xa4:
21:33:49:WU00:FS01:0xa4:Project: 10085 (Run 1, Clone 7, Gen 96)
21:33:49:WU00:FS01:0xa4:
21:33:49:WU00:FS01:0xa4:Assembly optimizations on if available.
21:33:49:WU00:FS01:0xa4:Entering M.D.
21:33:54:WU01:FS01:Upload 35.23%
21:33:55:WU00:FS01:0xa4:Mapping NT from 8 to 8
21:33:55:WU00:FS01:0xa4:Completed 0 out of 10000000 steps (0%)
21:34:00:WU01:FS01:Upload 84.54%
21:34:03:WU01:FS01:Upload complete
21:34:03:WU01:FS01:Server responded WORK_ACK (400)
21:34:03:WU01:FS01:Final credit estimate, 678.00 points
21:34:03:WU01:FS01:Cleaning up
21:35:55:WU00:FS01:0xa4:Completed 100000 out of 10000000 steps (1%)
<SNIP>
00:53:04:WU00:FS01:0xa4:Completed 9900000 out of 10000000 steps (99%)
00:53:05:WU01:FS01:Connecting to assign3.stanford.edu:8080
00:53:06:WU01:FS01:News: Welcome to Folding@Home
00:53:06:WU01:FS01:Assigned to work server 171.67.108.58
00:53:06:WU01:FS01:Requesting new work unit for slot 01: RUNNING smp:8 from 171.67.108.58
00:53:06:WU01:FS01:Connecting to 171.67.108.58:8080
00:53:06:WU01:FS01:Downloading 479.79KiB
00:53:09:WU01:FS01:Download complete
00:53:09:WU01:FS01:Received Unit: id:01 state:DOWNLOAD error:OK project:8047 run:494 clone:0 gen:13 core:0xa4 unit:0x0000000e6652edca4fda247cc007e267
00:53:09:WU01:FS01:Downloading project 8047 description
00:53:09:WU01:FS01:Connecting to fah-web.stanford.edu:80
00:53:09:WU01:FS01:Project 8047 description downloaded successfully
00:55:05:WU00:FS01:0xa4:Completed 10000000 out of 10000000 steps (100%)
00:55:05:WU00:FS01:0xa4:DynamicWrapper: Finished Work Unit: sleep=10000
00:55:15:WU00:FS01:0xa4:
00:55:15:WU00:FS01:0xa4:Finished Work Unit:
00:55:15:WU00:FS01:0xa4:- Reading up to 2081004 from "00/wudata_01.trr": Read 2081004
00:55:15:WU00:FS01:0xa4:trr file hash check passed.
00:55:15:WU00:FS01:0xa4:- Reading up to 216932 from "00/wudata_01.xtc": Read 216932
00:55:15:WU00:FS01:0xa4:xtc file hash check passed.
00:55:15:WU00:FS01:0xa4:edr file hash check passed.
00:55:15:WU00:FS01:0xa4:logfile size: 79219
00:55:15:WU00:FS01:0xa4:Leaving Run
00:55:19:WU00:FS01:0xa4:- Writing 2401627 bytes of core data to disk...
00:55:20:WU00:FS01:0xa4:Done: 2401115 -> 1788196 (compressed to 74.4 percent)
00:55:20:WU00:FS01:0xa4: ... Done.
00:55:20:WU00:FS01:0xa4:- Shutting down core
00:55:20:WU00:FS01:0xa4:
00:55:20:WU00:FS01:0xa4:Folding@home Core Shutdown: FINISHED_UNIT
00:55:20:WU00:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
00:55:20:WU00:FS01:Sending unit results: id:00 state:SEND error:OK project:10085 run:1 clone:7 gen:96 core:0xa4 unit:0x000001100001329c4ddbf665763d5448
00:55:20:WU00:FS01:Uploading 1.71MiB to 129.74.85.15
00:55:20:WU00:FS01:Connecting to 129.74.85.15:8080
00:55:20:WU01:FS01:Starting
00:55:20:WU01:FS01:Running FahCore: D:\FAHClient_V7/FAHCoreWrapper.exe C:/ProgramData/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 01 -suffix 01 -version 701 -lifeline 2412 -checkpoint 15 -np 8
00:55:20:WU01:FS01:Started FahCore on PID 352
00:55:20:WU01:FS01:Core PID:928
00:55:20:WU01:FS01:FahCore 0xa4 started
00:55:21:WU01:FS01:0xa4:
00:55:21:WU01:FS01:0xa4:*------------------------------*
00:55:21:WU01:FS01:0xa4:Folding@Home Gromacs GB Core
00:55:21:WU01:FS01:0xa4:Version 2.27 (Dec. 15, 2010)
00:55:21:WU01:FS01:0xa4:
00:55:21:WU01:FS01:0xa4:Preparing to commence simulation
00:55:21:WU01:FS01:0xa4:- Looking at optimizations...
00:55:21:WU01:FS01:0xa4:- Created dyn
00:55:21:WU01:FS01:0xa4:- Files status OK
00:55:21:WU01:FS01:0xa4:- Expanded 490788 -> 1145324 (decompressed 233.3 percent)
00:55:21:WU01:FS01:0xa4:Called DecompressByteArray: compressed_data_size=490788 data_size=1145324, decompressed_data_size=1145324 diff=0
00:55:21:WU01:FS01:0xa4:- Digital signature verified
00:55:21:WU01:FS01:0xa4:
00:55:21:WU01:FS01:0xa4:Project: 8047 (Run 494, Clone 0, Gen 13)
00:55:21:WU01:FS01:0xa4:
00:55:21:WU01:FS01:0xa4:Assembly optimizations on if available.
00:55:21:WU01:FS01:0xa4:Entering M.D.
00:55:26:WU00:FS01:Upload 21.98%
00:55:27:WU01:FS01:0xa4:Mapping NT from 8 to 8
00:55:27:WU01:FS01:0xa4:Completed 0 out of 250000 steps (0%)
00:55:32:WU00:FS01:Upload 43.97%
00:55:38:WU00:FS01:Upload 65.95%
00:55:44:WU00:FS01:Upload 87.93%
00:55:47:WU00:FS01:Upload complete
00:55:47:WU00:FS01:Server responded WORK_ACK (400)
00:55:47:WU00:FS01:Final credit estimate, 4599.00 points
00:55:47:WU00:FS01:Cleaning up
00:55:58:WU01:FS01:0xa4:Completed 2500 out of 250000 steps (1%)
<SNIP>
01:45:35:WU01:FS01:0xa4:Completed 250000 out of 250000 steps (100%)
01:45:35:WU01:FS01:0xa4:DynamicWrapper: Finished Work Unit: sleep=10000
01:45:36:WU00:FS01:Connecting to assign3.stanford.edu:8080
01:45:37:WU00:FS01:News: Welcome to Folding@Home
01:45:37:WU00:FS01:Assigned to work server 171.67.108.58
01:45:37:WU00:FS01:Requesting new work unit for slot 01: RUNNING smp:8 from 171.67.108.58
01:45:37:WU00:FS01:Connecting to 171.67.108.58:8080
01:45:37:WU00:FS01:Downloading 479.01KiB
01:45:40:WU00:FS01:Download complete
01:45:40:WU00:FS01:Received Unit: id:00 state:DOWNLOAD error:OK project:8047 run:328 clone:7 gen:10 core:0xa4 unit:0x0000000b6652edca4fda201c6f22e5a1
01:45:45:WU01:FS01:0xa4:
01:45:45:WU01:FS01:0xa4:Finished Work Unit:
01:45:45:WU01:FS01:0xa4:- Reading up to 595644 from "01/wudata_01.trr": Read 595644
01:45:45:WU01:FS01:0xa4:trr file hash check passed.
01:45:45:WU01:FS01:0xa4:- Reading up to 352812 from "01/wudata_01.xtc": Read 352812
01:45:45:WU01:FS01:0xa4:xtc file hash check passed.
01:45:45:WU01:FS01:0xa4:edr file hash check passed.
01:45:45:WU01:FS01:0xa4:logfile size: 23243
01:45:45:WU01:FS01:0xa4:Leaving Run
01:45:48:WU01:FS01:0xa4:- Writing 977287 bytes of core data to disk...
01:45:48:WU01:FS01:0xa4:Done: 976775 -> 929338 (compressed to 95.1 percent)
01:45:48:WU01:FS01:0xa4: ... Done.
01:45:48:WU01:FS01:0xa4:- Shutting down core
01:45:48:WU01:FS01:0xa4:
01:45:48:WU01:FS01:0xa4:Folding@home Core Shutdown: FINISHED_UNIT
01:45:48:WU01:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
01:45:48:WU01:FS01:Sending unit results: id:01 state:SEND error:OK project:8047 run:494 clone:0 gen:13 core:0xa4 unit:0x0000000e6652edca4fda247cc007e267
01:45:48:WU01:FS01:Uploading 908.06KiB to 171.67.108.58
01:45:48:WU01:FS01:Connecting to 171.67.108.58:8080
01:45:48:WU00:FS01:Starting
01:45:48:WU00:FS01:Running FahCore: D:\FAHClient_V7/FAHCoreWrapper.exe C:/ProgramData/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 701 -lifeline 2412 -checkpoint 15 -np 8
01:45:48:WU00:FS01:Started FahCore on PID 3768
01:45:48:WU00:FS01:Core PID:4160
01:45:48:WU00:FS01:FahCore 0xa4 started
<SNIP>
Appreciate your help.
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Fri Jun 22, 2012 12:15 pm
by PantherX
Fahrenheit451 wrote:...The FAH client is v7.1.50...
Any particular reason that you haven't upgraded to V7.1.52?
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Fri Jun 22, 2012 12:23 pm
by Fahrenheit451
No. Probably because it works fine and I never had trouble with this client version before
But I will update to the latest FAH client version when the next WU has been finished.
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Fri Jun 22, 2012 5:28 pm
by harlam357
compdewd wrote:Has it been suggested that HFM could link to other 3rd party stats sites rather than just EOC? Searching didn't bring up anything of the like. The reason I ask is because EOC does not provide my stats because I am part of team 0 and am out of the first 2000 that it keeps track of. Kakao Stats does keep track of me so it would be nice if HFM could include them as an option as well
Does Kakao have a publicly available xml feed?
GreyWhiskers wrote:Another suggestion. It seems like the HFM WU History Viewer revalues its database each time it comes up with the then-current ProjectSummary data. There was a recent event where an SMP Project had its deadline shortened because the QRB was overly generous. It seems that HFM WU History Viewer recomputed all the already completed projects with the new ProjSummary values.
Does the V7 Client interface pass on the actual points, as reported in the log, to the remote client interface software? If so, could that be permanently stored in the HFM Database vs. recomputing?
Great, great product - I feel I have a much better oversight into how my folding farm is doing.
Yes, you are correct. The currently loaded project info is used to calculate the points seen in the WU History Viewer. This is how the different variations in PPD and Credit are shown to the user. As many know, the bonus calculation needs to know the total length of time from WU assignment to submission. The first two options for viewing PPD and Credit are two variations on estimating this total time.
Bonus based on Download Time - Total length of time from Download to WU Completion
Bonus based on Frame Time - Average Frame Time for the WU (multiplied by) the Number of Frames
No Bonus - Base PPD and Credit numbers are displayed
This is why the final PPD and Credit are not directly stored in the Database, just the frame time. I need to do some work with the Database in the next, next version (a reliability update is coming soon) and I'll consider fully capturing the final PPD and Credit values.
It's been asked in the past that the actual time of Upload Completion be captured but this has proven problematic with v6 and since the information on previous WUs disappears in the v7 data once the unit is uploaded that is not an option for v7 either. That also falls into your question on whether the v7 interface transmits the final points estimate as seen in the log file. I believe the answer is no. Someone correct me if I am wrong. Could I try to get it from the log? Possibly, but to this point HFM doesn't pay any attention to the PPD and Credit values that come from v7. That logic was already built in HFM for v6 and that's the way I plan on keeping it.
Thanks for the kind words GW! I certainly appreciate it!
@Fahrenheit451 - Can you send me your entire log.txt file from the FAHClient and the entire HFM.log file (Help > View HFM.NET Data Files)?
To answer a few of your questions, the Completed Count has two views (Current Run and Total) - see the View menu. The Current Run view should yield a number for a v7 client, this is the total number since the client was last started. The Total view will always show 0 since there is currently no counting mechanism in the v7 client. The v6 client reports this total number in the log after every WU completes and I capture the number from there. I'm going to fix this for all client types by querying the WU History database in lieu of looking at the log file itself. I just haven't had time to make those adjustments yet.
As far as the 0% progress goes... if you see the correct log segment in the HFM log viewer and the frame progress lines are green it should be showing the progress correctly. There is a speed issue with transferring the log file from the v7 client to HFM and it looks like it's on my side of the fence. So, after starting HFM if a v7 client takes a while to before it shows the correct progress, that's probably what's going on. It may take a few minutes to get in sync. I've started looking at the speed issue more closely and it's the last thing I want to fix before the next HFM update.
If that's not the issue, let me just look at your logs and I'll see what they say... you can find me at gmail.com.
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Sat Jun 23, 2012 1:51 am
by Fahrenheit451
@harlam357: I sent you the log files to your gmail account.
Regarding the no. of completed WUs: I knew that HFM can only count the v7 WUs since the last start of the client. IIRC you wrote it somewhere earlier in this thread. I normally use only the "Current run" view, and this value currently stays @ 0, although I have finished more than one WU. Therefore I have sent you also a screenshot of HFM and the v7 client.
@PantherX: I have now updated to v7.1.52 and processed three WUs in the meantime, but there was no change in the behavior I have described above.
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Sat Jun 23, 2012 4:31 am
by PantherX
Fahrenheit451 wrote:...@PantherX: I have now updated to v7.1.52 and processed three WUs in the meantime, but there was no change in the behavior I have described above.
I skim read harlam357's post and the gist that I got was the (temporary) issue is on HFM.NET's side instead of FAHClient and would be fixed in the next release. If that isn't the case, then it might be a bug in V7 which would require further analysis.
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Sat Jun 23, 2012 3:07 pm
by Fahrenheit451
A preliminary result: I added today a replacement GTX 560Ti to the PC and HFM and FAH seems to work now as expected. Therefore I assume it is a FAH client issue which causes that HFM is not working properly.
These are my next planned steps:
When the second GPU WU has been finished I will remove the GPU again and check if HFM and FAH show the above described behavior.
If they do, I will re-install FAH v7.1.52 over the current v7.1.52, but won't keep the old config file in use as I did when I installed v7.1.52 over v7.1.50. Then FAH should not find the GPU and also not setup a GPU slot. In the current setup GPU is auto-assigned to slot 00 and SMP to slot 01.
When I checked the FAH logfiles yesterday I found the messages: "GPUs: 0", "CUDA: Not detected" which was correct, as I had no gfx card installed. Later in the file I found these information: "16:57:43:ERROR:Exception: No more GPUs" and "16:57:43:ERROR:Exception: Option 'gpu-index' has no default and is not set.". See the log file below:
Code: Select all
*********************** Log Started 2012-06-22T16:57:42Z ***********************
16:57:42:************************* Folding@home Client *************************
16:57:42: Website: http://folding.stanford.edu/
16:57:42: Copyright: (c) 2009-2012 Stanford University
16:57:42: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
16:57:42: Args: --lifeline 4180 --command-port=36330
16:57:42: Config: C:/ProgramData/FAHClient/config.xml
16:57:42:******************************** Build ********************************
16:57:42: Version: 7.1.52
16:57:42: Date: Mar 20 2012
16:57:42: Time: 19:37:42
16:57:42: SVN Rev: 3515
16:57:42: Branch: fah/trunk/client
16:57:42: Compiler: Intel(R) C++ MSVC 1500 mode 1200
16:57:42: Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
16:57:42: /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT
16:57:42: Platform: win32 XP
16:57:42: Bits: 32
16:57:42: Mode: Release
16:57:42:******************************* System ********************************
16:57:42: CPU: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
16:57:42: CPU ID: GenuineIntel Family 6 Model 42 Stepping 7
16:57:42: CPUs: 8
16:57:42: Memory: 7.85GiB
16:57:42: Free Memory: 6.48GiB
16:57:42: Threads: WINDOWS_THREADS
16:57:42: On Battery: false
16:57:42: UTC offset: 2
16:57:42: PID: 3440
16:57:42: CWD: C:/ProgramData/FAHClient
16:57:42: OS: Windows 7 Ultimate
16:57:42: OS Arch: AMD64
16:57:42: GPUs: 0
16:57:42: CUDA: Not detected
16:57:42:Win32 Service: false
16:57:42:***********************************************************************
16:57:42:<config>
16:57:42: <service-description v='Folding@home Client'/>
16:57:42: <service-restart v='true'/>
16:57:42: <service-restart-delay v='5000'/>
16:57:42:
16:57:42: <!-- Client Control -->
16:57:42: <cycle-rate v='4'/>
16:57:42: <cycles v='-1'/>
16:57:42: <data-directory v='.'/>
16:57:42: <disable-project-lookup v='false'/>
16:57:42: <exec-directory v='D:\FAHClient_V7'/>
16:57:42: <exit-when-done v='false'/>
16:57:42: <threads v='4'/>
16:57:42:
16:57:42: <!-- Configuration -->
16:57:42: <config-rotate v='true'/>
16:57:42: <config-rotate-dir v='configs'/>
16:57:42: <config-rotate-max v='16'/>
16:57:42:
16:57:42: <!-- Debugging -->
16:57:42: <assignment-servers>
16:57:42: assign3.stanford.edu:8080 assign4.stanford.edu:80
16:57:42: </assignment-servers>
16:57:42: <capture-directory v='capture'/>
16:57:42: <capture-sockets v='false'/>
16:57:42: <debug-sockets v='false'/>
16:57:42: <exception-locations v='true'/>
16:57:42: <gpu-assignment-servers>
16:57:42: assign-GPU.stanford.edu:80 assign-GPU.stanford.edu:8080
16:57:42: </gpu-assignment-servers>
16:57:42: <stack-traces v='false'/>
16:57:42:
16:57:42: <!-- Error Handling -->
16:57:42: <max-slot-errors v='5'/>
16:57:42: <max-unit-errors v='5'/>
16:57:42:
16:57:42: <!-- FahCore Control -->
16:57:42: <checkpoint v='15'/>
16:57:42: <core-dir v='cores'/>
16:57:42: <core-priority v='idle'/>
16:57:42: <cpu-affinity v='false'/>
16:57:42: <cpu-usage v='100'/>
16:57:42: <no-assembly v='false'/>
16:57:42:
16:57:42: <!-- Folding Slot Configuration -->
16:57:42: <client-subtype v='STDCLI'/>
16:57:42: <client-type v='advanced'/>
16:57:42: <cpu-species v='X86_PENTIUM_II'/>
16:57:42: <cpu-type v='AMD64'/>
16:57:42: <cpus v='-1'/>
16:57:42: <cuda-index v='0'/>
16:57:42: <gpu v='true'/>
16:57:42: <gpu-usage v='100'/>
16:57:42: <max-packet-size v='big'/>
16:57:42: <opencl-index v='0'/>
16:57:42: <os-species v='UNKNOWN'/>
16:57:42: <os-type v='WIN32'/>
16:57:42: <project-key v='0'/>
16:57:42: <smp v='true'/>
16:57:42:
16:57:42: <!-- Logging -->
16:57:42: <log v='log.txt'/>
16:57:42: <log-color v='false'/>
16:57:42: <log-crlf v='true'/>
16:57:42: <log-date v='false'/>
16:57:42: <log-date-periodically v='21600'/>
16:57:42: <log-debug v='true'/>
16:57:42: <log-domain v='false'/>
16:57:42: <log-header v='true'/>
16:57:42: <log-level v='true'/>
16:57:42: <log-no-info-header v='true'/>
16:57:42: <log-redirect v='false'/>
16:57:42: <log-rotate v='true'/>
16:57:42: <log-rotate-dir v='logs'/>
16:57:42: <log-rotate-max v='16'/>
16:57:42: <log-short-level v='false'/>
16:57:42: <log-simple-domains v='true'/>
16:57:42: <log-thread-id v='false'/>
16:57:42: <log-thread-prefix v='true'/>
16:57:42: <log-time v='true'/>
16:57:42: <log-to-screen v='true'/>
16:57:42: <log-truncate v='false'/>
16:57:42: <verbosity v='5'/>
16:57:42:
16:57:42: <!-- Network -->
16:57:42: <proxy v=':8080'/>
16:57:42: <proxy-enable v='false'/>
16:57:42: <proxy-pass v=''/>
16:57:42: <proxy-user v=''/>
16:57:42:
16:57:42: <!-- Process Control -->
16:57:42: <child v='false'/>
16:57:42: <daemon v='false'/>
16:57:42: <pid v='false'/>
16:57:42: <pid-file v='Folding@home Client.pid'/>
16:57:42: <respawn v='false'/>
16:57:42: <service v='false'/>
16:57:42:
16:57:42: <!-- Remote Command Server -->
16:57:42: <command-address v='0.0.0.0'/>
16:57:42: <command-allow v='127.0.0.1,192.168.2.0/24'/>
16:57:42: <command-allow-no-pass v='127.0.0.1,192.168.2.0/24'/>
16:57:42: <command-deny v='0.0.0.0/0'/>
16:57:42: <command-deny-no-pass v='0.0.0.0/0'/>
16:57:42: <command-port v='36330'/>
16:57:42:
16:57:42: <!-- Slot Control -->
16:57:42: <max-shutdown-wait v='60'/>
16:57:42: <pause-on-battery v='false'/>
16:57:42: <pause-on-start v='false'/>
16:57:42:
16:57:42: <!-- User Information -->
16:57:42: <machine-id v='0'/>
16:57:42: <passkey v='********************************'/>
16:57:42: <team v='0'/>
16:57:42: <user v='superduper4711'/>
16:57:42:
16:57:42: <!-- Work Unit Control -->
16:57:42: <dump-after-deadline v='true'/>
16:57:42: <max-queue v='16'/>
16:57:42: <max-units v='0'/>
16:57:42: <next-unit-percentage v='99'/>
16:57:42:
16:57:42: <!-- Folding Slots -->
16:57:42: <slot id='0' type='GPU'/>
16:57:42: <slot id='1' type='SMP'>
16:57:42: <client-type v='advanced'/>
16:57:42: <cpus v='-1'/>
16:57:42: <max-packet-size v='big'/>
16:57:42: </slot>
16:57:42:</config>
16:57:43:Trying to access database...
16:57:43:Successfully acquired database lock
16:57:43:ERROR:Exception: No more GPUs
16:57:43:Enabled folding slot 01: READY smp:8
16:57:43:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:43:Started thread 6 on PID 3440
16:57:43:Started thread 4 on PID 3440
16:57:43:Started thread 5 on PID 3440
16:57:43:Started thread 3 on PID 3440
16:57:43:Started thread 1 on PID 3440
16:57:43:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:43:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:43:WU00:FS01:Connecting to assign3.stanford.edu:8080
16:57:43:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:43:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:43:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:43:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:43:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:44:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:44:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:44:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:44:WU00:FS01:News: Welcome to Folding@Home
16:57:44:WU00:FS01:Assigned to work server 129.74.85.15
16:57:44:WU00:FS01:Requesting new work unit for slot 01: READY smp:8 from 129.74.85.15
16:57:44:WU00:FS01:Connecting to 129.74.85.15:8080
16:57:44:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:45:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:45:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:45:WU00:FS01:Downloading 51.53KiB
16:57:45:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:45:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:45:WU00:FS01:Download complete
16:57:45:WU00:FS01:Received Unit: id:00 state:DOWNLOAD error:OK project:7007 run:3 clone:25 gen:89 core:0xa4 unit:0x000000bc0001329c4dfb914faaeb7a91
16:57:45:WU00:FS01:Starting
16:57:45:WU00:FS01:Running FahCore: D:\FAHClient_V7/FAHCoreWrapper.exe C:/ProgramData/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 701 -lifeline 3440 -checkpoint 15 -np 8
16:57:45:WU00:FS01:Started FahCore on PID 3984
16:57:45:Started thread 7 on PID 3440
16:57:46:WU00:FS01:Core PID:3688
16:57:46:WU00:FS01:FahCore 0xa4 started
16:57:46:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:46:WU00:FS01:Downloading project 7007 description
16:57:46:WU00:FS01:Connecting to fah-web.stanford.edu:80
16:57:46:Server connection id=1 on 0.0.0.0:36330 from 127.0.0.1
16:57:46:Started thread 8 on PID 3440
16:57:46:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:46:WU00:FS01:0xa4:
16:57:46:WU00:FS01:0xa4:*------------------------------*
16:57:46:WU00:FS01:0xa4:Folding@Home Gromacs GB Core
16:57:46:WU00:FS01:0xa4:Version 2.27 (Dec. 15, 2010)
16:57:46:WU00:FS01:0xa4:
16:57:46:WU00:FS01:0xa4:Preparing to commence simulation
16:57:46:WU00:FS01:0xa4:- Looking at optimizations...
16:57:46:WU00:FS01:0xa4:- Created dyn
16:57:46:WU00:FS01:0xa4:- Files status OK
16:57:46:WU00:FS01:0xa4:- Expanded 52256 -> 207472 (decompressed 397.0 percent)
16:57:46:WU00:FS01:0xa4:Called DecompressByteArray: compressed_data_size=52256 data_size=207472, decompressed_data_size=207472 diff=0
16:57:46:WU00:FS01:0xa4:- Digital signature verified
16:57:46:WU00:FS01:0xa4:
16:57:46:WU00:FS01:0xa4:Project: 7007 (Run 3, Clone 25, Gen 89)
16:57:46:WU00:FS01:0xa4:
16:57:46:WU00:FS01:0xa4:Assembly optimizations on if available.
16:57:46:WU00:FS01:0xa4:Entering M.D.
16:57:46:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:46:WU00:FS01:Project 7007 description downloaded successfully
16:57:46:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:47:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:47:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:47:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:47:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:48:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:48:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:48:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:48:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:49:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:49:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:49:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:49:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:50:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:50:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:50:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:50:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:51:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:51:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:51:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:51:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:52:ERROR:Exception: Option 'gpu-index' has no default and is not set.
16:57:52:WU00:FS01:0xa4:Mapping NT from 8 to 8
16:57:52:WU00:FS01:0xa4:Completed 0 out of 10000000 steps (0%)
16:57:52:ERROR:Exception: Option 'gpu-index' has no default and is not set.
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Sun Jun 24, 2012 9:52 pm
by baqban324
Hyperlife wrote:7im wrote:Developer work on this was already proceding without a ticket. Harlam had communicated this directly to Joe. Now you can track the work's progress directly...
Ticket # 872
Thanks. Good to see this is being addressed.
I remember when Hyperlife was mentioning the log segfault problem happening for FAHControl too. I finally got around to testing this on my computer, but I don't have a second host to run a remote client on so it was just locally. I never had any problems with the local client, even for logs in the MB range.
Currently the ticket is registered as a bug in FAHControl with mixed clients, but could it actually be in how FAHClient handles large transmissions over a remote connection? That could explain why it happens for both FAHControl & HFM.NET and according to the ticket note by calxalot, it can happen even if both the client and monitor are running on OSX. Maybe the log transmission overruns other threads if the buffer doesn't get emptied quick enough? If it's a problem unique to POSIX threads, it could also explain why Windows doesn't seem to be affected.
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Wed Jun 27, 2012 4:57 pm
by GreyWhiskers
Quick question on syntax of query filters for the WU History Viewer
I can easily create a filter for:
- an exact match to any of the columns, or
- do a numerical greater or less match or
- do a composite query with the second or subsequent rows IMPLICIT AND
- do a range query using two rows (e.g., ProjectID ≥8020 and a second row ProjectID≤8025)
But, can we do a non-numeric wild card match , e.g., not an exact match to the whole field but filter name by, e.g., HP* for the various names for my HP computer slots?
Thanks.
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Thu Jun 28, 2012 3:19 am
by harlam357
@F451 - ok, I know what's going on... there is 8MB worth of log file with the large majority of it filled with
ERROR:Exception: Option 'gpu-index' has no default and is not set as you mentioned previously. That's not the FAHClient's fault. HFM should handle this but the idea that there would be so many error messages to sift through was never in the design... it's tough to design for something that you don't know is a possibility.
Here's the long and short of it... as you've now seen, placing the gpu back in the system gets rid of this error message and HFM starts working as expected. The reason, v0.9.0 will only hold so much v7 log in memory to try and keep memory consumption down. For other reasons besides this, I've since found the arbitrary value (about 512k) I used for this internal log buffer to be too small (it's already much, much larger in my latest closed beta - I am working on an update). So as these error messages keep coming across the wire from the v7 client HFM dumps the older parts of the log. The thought here is... log that is old (512k ago) should be of no concern anymore. That theory is blown out of the water though when these
ERROR:Exception messages are written 4 times a second... geeze.
However, that "old" log contained the start of the WU and the frame completion information and thus HFM wasn't able to find the log lines associated with the WU that was in progress as reported by the v7 client. If HFM cannot find the log section in its internal log buffer you'll see a line like this printed in the HFM's log file:
! (FAH Box One Slot 01) Could not find log section for slot 1. Cannot update frame data for this slot. It's telling you there that the proper log section cannot be found... thus HFM defaults to pulling frame time information from the benchmarks (which is what happens when the status of a client is RunningNoFrameTimes == Yellow).
So... more long than short of it. Thank you for bringing this to my attention and I apologize for the length of time it took me to respond.
@GW - not yet... but wildcards are something I have on the plan. The WU History View needs an overhaul in general and that capability, along with specifying AND / OR for the boolean logic, is something I've wanted to implement for some time. Time... yeah, that's what I need... can anyone loan me some of theirs? This is an open source project... it's certainly open to contributions.
Re: HFM.NET - Monitoring Application for Folding@Home v6/v7
Posted: Thu Jun 28, 2012 10:12 pm
by Fahrenheit451
harlam357 wrote:
So... more long than short of it. Thank you for bringing this to my attention and I apologize for the length of time it took me to respond.
No worries! You have the dev work, I can only add my experiences.
You might be right, that HFM should be able to handle such large log files, but IMHO the log of the FAH client should not report these error exceptions in this way. Isn't it possible to log nothing for the GPU slot when FAH don't found a GPU at start? But I think this question should better be asked in the FAH Client thread.
However, thank you for your reply.