Results 1 to 20 of 629
04-29-09, 11:34 PM #1
* HFM.NET - Client Monitoring Application for Folding@Home *
HFM.NET - Client Monitoring Application for the Folding@Home Distributed Computing Project
Homepage on Google Code: http://code.google.com/p/hfm-net/
Please see the Homepage on Google Code for the latest version.
Google Group: http://groups.google.com/group/hfm-net/
Please see the Google Group for complete release notes, help, and support.
Last edited by harlam357; 10-31-09 at 03:18 PM.
04-29-09, 11:36 PM #2
Debugging clients that appear Hung (Red Status) is easy.
Just go to the Preferences -> Defaults -> Message Level -> Change it to 'Verbose'. Then refresh one of your clients again and check the Messages Window (Tools -> Show/Hide Messages Window).
[5/30/2009-2:58:13 PM] + HFM.Instances.ClientInstance.DetermineStatus (WinSMP - HTPC) [5/30/2009-2:58:13 PM] + - Retrieval Time (Date) ------- : 5/30/2009 2:58:13 PM [5/30/2009-2:58:13 PM] + - Time Of Last Frame (TimeSpan) : 14:51:53 [5/30/2009-2:58:13 PM] + - Offset (Minutes) ------------ : 0 [5/30/2009-2:58:13 PM] + - Time Of Last Frame (Adjusted) : 14:51:53 [5/30/2009-2:58:13 PM] + - Prior Day Adjustment -------- : False [5/30/2009-2:58:13 PM] + - Time Of Last Frame (Date) --- : 5/30/2009 2:51:53 PM [5/30/2009-2:58:13 PM] + - Terminal Time (Date) -------- : 5/30/2009 2:33:03 PM
This 'Offset' is used to determine the 'Status' of the client in question. In the above example you'll see that the Time Of Last Frame is later than Terminal Time. If this is the case, the client is deemed to be running. Terminal Time is calculated differently for GPU clients vs. CPU clients. However, in either case, the Time Of Last Frame must be later than the Terminal Time. If the opposite is true, then the client will be deemed Hung and will not show any progress percentage, TPF, PPD, etc.
In the case of a notfred's VM... you will want to check the 'Client is on Virtual Machine' option. Then Debug with the times as I've stated above.
What I would recommend you do is set the system time and UTC offset on your monitored machines to the correct time. If that is done, you won't have to set any 'Offset' value for your clients. Much simpler approach.
Last edited by harlam357; 06-05-09 at 01:05 PM.
04-29-09, 11:38 PM #3
04-30-09, 12:03 AM #4
Way to go, H!
Last edited by Adak; 04-30-09 at 12:49 PM.
04-30-09, 07:50 AM #5
It works great. The XP lag issue is a minor PITA, easily overcome by stopping the Primary GPU for a while or monitoring with a non GPU folder or a Vista machine. One of the best features that Harlam didn't mention enough is that HFM parses FahLog.txt, counts and reports the number of FINISHED, UNSTABLE_MACHINE and EARLY_UNIT_END occurrences. You can tell at a glance if you have a problem machine. THis is fantastic for monitoring the GPU2 client and even better than fantastic for monitoring a lot of clients.
04-30-09, 09:55 AM #6
Works great on my Vista x64 machine. Thanks again harlam for a job well done.
Question: Is my Virtual Client supposed to be red instead of green in the status? The log shows its folding but the status remains red?
04-30-09, 10:41 AM #7
Is this a standard VM or a notfred Virtual Appliance?
If the latter, you need to check the box in the host config dialog that says 'Client is on Virtual Machine'. notfred VMs report the machine's local time as UTC... In other words, there is no way to specify a timezone offset in the VM. Checking that option allows HFM to compensate for that.
Otherwise, if that is a standard VM and the timezone offset is set correctly... then the time on that machine is too far behind the machine running HFM... you can fix this by either:
- Correcting the time on the Virtual Machine.
- Using the 'Client Time Offset' setting in the Host Config Dialog. If the VM's time is behind the machine running HFM by 20 minutes, set this to -20.
My method for detmining 'Status' is a bit more stringent than FahMon I think... and I personally like it that way - I believe it's more accurate (once given the right information) and does not generate the false positives that FahMon does (again, once given the right information).
Last edited by harlam357; 04-30-09 at 10:47 AM.
04-30-09, 10:45 AM #8
My log in my vm reads 7:43 right now but its actually 10:43 so I guess its 3 hours behind?
I see the max value is -120 in the HFM though so I wouldn't able to fix it that way. I think I remember seeing something about getting VMtools to fix the time error?
Otherwise, awesome program I am loving it.
04-30-09, 11:11 AM #9
Very well done.Haswell Benching and Gaming: ASRock Z87 OC Formula : Intel i7 4770k w/ Phanteks PH-TC14 : 16GB 4x4GB G.Skill TridentX DDR3-2666 : 2x R9 290X
Other Components: Samsung 840 Evo 500GB SSD : 2TB Hitachi 7200rpm : Seasonic Platinum 1000W : Auria EQ276W 2560x1440, Crossover P27Q 2560x1440, Dell 2407WFP 1920x1200
04-30-09, 11:17 AM #10
Would you mind if I linked folks on our forum to this to try out? It looks sweet, and some of us have issues with FahMon.
04-30-09, 12:07 PM #11
awesome work man
MainRig: i7 3770K@4.4(1.25v) TR TrueSpirit120; 8GB G.Skill TridentX@2400 CL10; AsRock Z77 Ext6; noGPU
PlayRig: i3 firstname.lastname@example.org(1.4v) TR True120 on zipties; 4GB SuperTalent@1600 CL8; Asus P7P55D; Asus HD7870@1200/1250
What is The Bitcoin? Want The Bitcoin?
04-30-09, 12:09 PM #12
I set the min and max minutes to 120 respectively because if the client is that far off, then the time on that machine really needs set correctly. Really, I recommend that the time be set correctly anyway, resulting in no 'Offset' value being necessary. One will always need to check the box for 'Client is on Virtual Machine' when running a notfred VM, that cannot be helped... but the easiest thing to do with all monitored machines is just make sure they are syncing to some NTP server, then their times will be correct and you won't have any issues or need for an 'Offset' value.
It's publicly available... so I can't stop you anyway. But thank you for asking.
04-30-09, 12:49 PM #13
If you're going to post it on everyone's forums anyway, I'll just let you do it and have the honors.
04-30-09, 01:02 PM #14
Thank you kindly.
04-30-09, 01:58 PM #15
Fantastic Work there harlam357 on the HFM.NET v1.1 Biuld 10.
Sent you Email ,, but I see someone above has same issue with Notfreds VM, with the Time differences,
other than that Works like a Charm,
04-30-09, 02:27 PM #16
All of my machines are vista 32bit and so far it works great! I really like the additional stats over FAHMon.
Thanks Harlam!: Fold for Team 32
Lian Li PC-A70 Case
Intel 2600K @ 4.4 GHz 1.4 V
Prolimatech Megahalems Rev.B
ASUS P8P67 Deluxe
G.Skill 2x4GB 2133 MHz
Mushkin 240gb Chronos Deluxe
Corsair 620HX PSU
04-30-09, 02:41 PM #17
Jolly, got your e-mail. What is your UTC Offset? Are you +10 or +11?
Try playing with the 'Offset' value +60 or -60 (in addition to having 'Client is on Virtual Machine' checked) for one of the clients that is showing as Hung (Red).
Some machine(s) are just off by an hour... I know, people are going to have a time with this as FahMon is less stringent on time stamps. I may have to add an option similar to 'Ignore Async Clocks' (which makes things less stringent) to make things easier on folks.
Let me know on your UTC Offset and we'll get
youryou straightened out.
Last edited by harlam357; 04-30-09 at 03:27 PM.
04-30-09, 04:10 PM #18
04-30-09, 04:45 PM #19
Fantastic Kudos to Harlam357
Is there a way to round the numbers of the PPD and PPD/Mhz?
What do the completed #'s mean? When I started adding clients I was getting numbers from 0 to 131.
I have this running on Vista32OCForums Folding (Team32)
04-30-09, 05:33 PM #20
HFM parses the log of each instance and counts the number of times the word FINISHED occurred, which represents the number of completed WUs in the current log. It also counts the number of times the words UNSTABLE and EARLY occurred, which corresponds to the number of failed WUs in the current log.