HFM.NET - Monitoring Application for Folding@Home v7

[7up1n3]

Figured it out. At some point after I last used HFM.NET, it was migrated to .NET v3.5 - which I hadn't installed on that particular webserver yet. Not surprisingly, HFM.NET ran just fine when it was using .NET v2 but not .NET v3.5. Changelogs FTW! :p

[PantherX]

I wanted to use Task Scheduler to start HFM.NET when I log in but it gives an error that HFM.NET has encountered a problem and is exiting. Some data that I got from Windows:

Code: Select all

Source
HFM.NET

Summary
APPCRASH

Date
‎20-‎Oct-‎10 9:11 AM

Status
Report sent

Description
Stopped working
Faulting Application Path:	C:\Users\PantherX\AppData\Roaming\Microsoft\Installer\{E03989B9-A4EF-4B97-9F5F-529315177A5B}\HFM.exe

Problem signature
Problem Event Name:	APPCRASH
Application Name:	HFM.exe
Application Version:	0.5.1.198
Application Timestamp:	4c27ea5b
Fault Module Name:	KERNELBASE.dll
Fault Module Version:	6.1.7600.16385
Fault Module Timestamp:	4a5bdfe0
Exception Code:	e0434f4d
Exception Offset:	000000000000aa7d
OS Version:	6.1.7600.2.0.0.256.1
Locale ID:	1033

Extra information about the problem
Bucket ID:	18404666

Code: Select all

Source
HFM.NET

Summary
APPCRASH

Date
‎20-‎Oct-‎10 9:05 AM

Status
Report sent

Description
Stopped working
Faulting Application Path:	C:\Users\PantherX\AppData\Roaming\Microsoft\Installer\{E03989B9-A4EF-4B97-9F5F-529315177A5B}\HFM.exe

Problem signature
Problem Event Name:	APPCRASH
Application Name:	HFM.exe
Application Version:	0.5.1.198
Application Timestamp:	4c27ea5b
Fault Module Name:	KERNELBASE.dll
Fault Module Version:	6.1.7600.16385
Fault Module Timestamp:	4a5bdfe0
Exception Code:	e0434f4d
Exception Offset:	000000000000aa7d
OS Version:	6.1.7600.2.0.0.256.1
Locale ID:	1033

I then resorted to placing the shortcut in the Startup folder. I am using the .msi Installer and the version is 0.5.1 Beta. Is this an already known issue?

[7im]

HFM can be configured to start automatically at login. You don't need to schedule it.

[harlam357]

Bingo... you can let HFM handle it, which it does by registry entry, or you can put a shortcut in the Startup Folder yourself.

Using Task Scheduler to start HFM... you never know what someone is going to do with your software.

What I don't understand is this: C:\Users\PantherX\AppData\Roaming\Microsoft\Installer\{E03989B9-A4EF-4B97-9F5F-529315177A5B}\HFM.exe

The exe should be here: \Program Files\HFM.NET\HFM.exe. That looks to have something to do with the registry entry the Windows Installer engine writes.

[PantherX]

I didn't really notice that setting until now.

Yes, harlem357, I did notice that and thought that it was weird. I had used the desktop shortcut in my first 2 attempts. However, now I have used the Program Files link and will restart the system to check it. I guess it would work.

I am just experiment to see what other possible ways there are to run F@h Clients + apps without much user intervention

UPDATE -> It works like a charm

[RAH]

Not sure if just me. I noticed the last couple of days that HFM isn't auto updating user/team stats.
Everything else seems to be working. Will check it out some more.

[harlam357]

Hi RAH,

You mean the EOC Stats? At the bottom of the HFM window? Working fine here... if there is an error it will be logged. Check the log file (Help menu) and/or the Messages (F7) window.

[harlam357]

New Version: 0.6.0 - Revision 249 - Beta - Download

I'm proud to bring you all two pretty big feature additions to this version of HFM. The first is the addition of the Work Unit History Viewer and Database. This database supersedes the CompletedUnits.csv file that has been written with information on completed work units prior to this version. Check the Tools menu.

You also have the option to Import your CompletedUnits.csv file so we don't leave all that good data you've been collecting with no where to go. There were some inconsistencies in the manner HFM wrote to the CompeltedUnits.csv file so I've done my best to write the Import to only process *Good* data that can be verified without a whole lot of fuss. The Import will weed out any duplicate entries in the file and also give you option to "fix-up" the entries in the file that were unable to be imported. Here are a couple likely scenarios:

- p6701/6702 have an issue with a comma in the work unit name. You can safely remove the ENTIRE work unit name from those entries. The import completely ignores the work unit name value. Once the bad entries file is clean-up up you can Import that file and only those entries by performing another Import on that file.

You can find the WU Database file in the HFM Data Files. See the Help menu. The file name is WuHistory.db3. If don't feel like you got everything Imported the way you want you can simply delete that file and try again.

Example:

Code: Select all

BAD:  6701,p6701_VSD in POPC and water, neutralized,Windows SMP - Main Workstation,...

GOOD: 6701,,Windows SMP - Main Workstation,..

- International users are likely out of luck using the CompletedUnits.csv Import unless you want to script or hand convert your CompletedUnits.csv file to be formatted in United States English format. The issues here include decimal numbers written with commas and date values not in en-US format. I apologize to any of you this will effect but this Import is a one off deal and I made the decision to keep it simple and not attempt to write a bunch of code to fix this one time deal. The software is Beta and issues like this are the reason I continue to label it as such.

The second big addition is the ability to Merge Client Data from other instances of HFM. For example, you have clients running at work and would like to monitor them in conjunction with your clients running at home. However, you do not have access to all the log files over HTTP or FTP. The solution, the HFM instance at work can act as a data collector using the Web Generation option 'Copy Client Data to Target' to place a ClientData.dat file in a location exposed by a HTTP or FTP server. Then on your home machine you can use the Clients -> Merge Client Data option to point HFM to that data file. Once retrieved the clients monitored by the remote instance of HFM will be visible in the local instance IN A READ-ONLY FASHION. You cannot edit or otherwise control the remote clients. It's simply a data merge.

What else? FahMon Import support has been removed from the main code base. It is now available as a Plugin. Download and read the readme.txt file for instructions on getting it installed. There are also new hotkey options (Alt+O) and (Alt+P) to cycle the Bonus and PPD Calculation options respectively.


Check the HFM Google Code page for downloads and details on the changes. As always, if you need to find me quickly, see below. I usually answer pretty quickly.

---

Need help with HFM? Have a Feature Request? Please Join the Discussions. Post in the HFM Google Group.

http://groups.google.com/group/hfm-net

[Zagen30]

First off, very nice additions. I just wish I could get them to work properly!

When I go to import the csv file, it first says that there are thousands of repeat WUs, which I somewhat doubt because my machines are stable and almost never EUE, and as we all know duplicate WUs are almost never sent out.



Secondly, whether or not I save the 6701's/6702's to a separate csv or not (very handy feature, BTW), I get the following message:



Full text:

Code: Select all

HFM.NET v0.6.0.249

Microsoft Windows NT 6.1.7600.0

Exception Thrown:
System.Data.SQLite.SQLiteException: SQLite error
near "s": syntax error
   at System.Data.SQLite.SQLite3.Prepare(SQLiteConnection cnn, String strSql, SQLiteStatement previous, UInt32 timeoutMS, String& strRemain)
   at System.Data.SQLite.SQLiteCommand.BuildNextCommand()
   at System.Data.SQLite.SQLiteDataReader.NextResult()
   at System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
   at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
   at HFM.Instances.UnitInfoDatabase.WriteUnitInfoToDatabase(SQLiteConnection con, HistoryEntry entry)
   at HFM.Instances.UnitInfoDatabase.ImportCompletedUnits(ICollection`1 entries)
   at HFM.Forms.HistoryPresenter.ImportCompletedUnitsClick()
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

When I first ran it about 5 WUs were imported out of over 5000. I managed to get almost all of the 670x's imported properly by editing the separate csv, but the WUs without that issue aren't being imported. The images above showing >5 WUs were taken after the 670x's were imported.

*EDIT*

The issue may be with the particular csv file. The above came from my desktop, which I tried first. I've also installed the new version on my laptop, which obviously has a different csv file, and importing the laptop's local record produced only a few duplicates. What's interesting is that the laptop and desktop are usually on the same network and monitor each other, so most of the WU information is the same (that doesn't explain the supposed 2200 duplicates though, as I imported the desktop csv to the desktop installation first). For fun, I tried importing the desktop's csv to the laptop installation and it reported the exact same number of duplicates as the desktop did.

If you'd like the finicky csv file I'd be happy to send it, though it is over a meg in size.

[PantherX]

An amazing addition but I simply cannot get it to work It gives me an error:

If you can tell me what I have to do, it would be great. BTW here is a sample line from the completedUnits.csv: (10512 & 6701)

Code: Select all

10512	p10512_ntl9(1-56)_WT	GPU2	D:\F@H GPU2\	PantherX	69411	GPU	GROGPU2	1.31	0:01:03	8050.29	29-Jun-10	3:08 PM	29-Jun-10	4:54 PM	587	100	908	(4/230/0)	
6701	p6701_VSD in POPC and water	 neutralized	SMP2	D:\F@H SMP\	PantherX	69411	SMP	GRO-A3	2.22	0:09:50	7633.86	28-Jun-10	10:35 PM	29-Jun-10	5:01 PM	5213	100	28637	(36/11/14)

EDIT, I decided to go poking around with a copy of the completedunit.csv and now I have this new error:

Code: Select all

HFM.NET v0.6.0.249

Microsoft Windows NT 6.1.7600.0

Exception Thrown:
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'frmUnitImport'.
   at System.Windows.Forms.Control.CreateHandle()
   at System.Windows.Forms.Form.CreateHandle()
   at System.Windows.Forms.Control.get_Handle()
   at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
   at harlam357.Windows.Forms.ProgressDialog.Process()
   at HFM.Forms.HistoryPresenter.ImportCompletedUnitsClick()
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Any idea what happened?

[PantherX]

If HFM.NET is giving you an error about importing the data, this is what you may have to do:

Fix for 670X WUs (MUST)

In order to successfully import the CompletedUnits.csv file into HFM.NET's Work Unit History, you will have to fix the data entry for Project 670X only.

Step 1: Open the CompletedUnits.csv file in MS Excel 2007 (make a copy of it and work from that to avoid any data loss!)

Step 2: Search for 6701 and 6702 in the ProjectID Column and changed the field in Work Unit Name from this in red rectangle:


Step 3: To this, in green rectangle:

Do remember that you have to shift the entire row one cell back to align it with the rest of the table.

Here is the unaccepted data format for Project 670X: (taken from the original CompletedUnits.csv file)

Code: Select all

6701	p6701_VSD in POPC and water	 neutralized	SMP2	D:\F@H SMP\	PantherX	69411	SMP	GRO-A3	2.19	0:09:16	8840.32	15-Jun-10	1:59 AM	15-Jun-10	5:27 PM	5689	100	28637	(25/6/1)

Here is the accepted data format for Project 670X: (taken from the modified CompletedUnits.csv file)

Code: Select all

6701		SMP2	D:\F@H SMP\	PantherX	69411	SMP	GRO-A3	2.19	0:09:16	8840.32	6-15-2010	1:59 AM	6-15-2010	5:27 PM	5689	100	28637	(25/6/1)

Once you have modified the CompletedUnits.csv file, try to import it into HFM.NET's Work Unit History. If it imports successfully, you can ignore the next step. You can safely ignore the "duplicate records not imported" message since it was a software glitch in the previous versions of HFM.NET that has been corrected in this new version.



Fix for Date Format (Depends)

If fixing the 670X WUs didn't work for you and you are still can't import the CompletedUnits.csv file, you may have to do these additional steps:

Step 1: Change the date format in the Download Date and Completion Date (Observed) from this in the red rectangle:


Step 2: To this, in the green rectangle:

I chose the entire column, right click on the selection -> Format Cells -> Number Tab -> Category Date -> Type 3-14-2001 (second last option in the table). My location was already set as English (United States)

Here is the unaccepted date format: (taken from the original CompletedUnits.csv file)

Code: Select all

5771	p5771_NTL9_370K	FH GPU2	D:\F@H GPU\	PantherX	69411	GPU	GROGPU2	1.31	0:00:40	7624.8	4/17/2010	1:26 PM	4/17/2010	2:33 PM	353	100	627	(3/231/282)

Here is the accepted date format: (taken from the modified CompletedUnits.csv file)

Code: Select all

5771	p5771_NTL9_370K	FH GPU2	D:\F@H GPU\	PantherX	69411	GPU	GROGPU2	1.31	0:00:40	7624.8	4-17-2010	1:26 PM	4-17-2010	2:33 PM	353	100	627	(3/231/282)

After making the above changes, save the file as .csv (MS Excel may give an error but I ignored it) and then imported it into HFM.NET's Work Unit History without any issue. You can safely ignore the "duplicate records not imported" message since it was a software glitch in the previous versions of HFM.NET that has been corrected in this new version. Enjoy the new features

Please note that the new WUs will be saved in WuHistory.db3 instead of CompletedUnits.csv file.

[harlam357]

First off, very nice additions. I just wish I could get them to work properly!

When I go to import the csv file, it first says that there are thousands of repeat WUs, which I somewhat doubt because my machines are stable and almost never EUE, and as we all know duplicate WUs are almost never sent out.

Secondly, whether or not I save the 6701's/6702's to a separate csv or not (very handy feature, BTW), I get the following message:

Full text:

Code: Select all

HFM.NET v0.6.0.249

Microsoft Windows NT 6.1.7600.0

Exception Thrown:
System.Data.SQLite.SQLiteException: SQLite error
near "s": syntax error
   at System.Data.SQLite.SQLite3.Prepare(SQLiteConnection cnn, String strSql, SQLiteStatement previous, UInt32 timeoutMS, String& strRemain)
   at System.Data.SQLite.SQLiteCommand.BuildNextCommand()
   at System.Data.SQLite.SQLiteDataReader.NextResult()
   at System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
   at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
   at HFM.Instances.UnitInfoDatabase.WriteUnitInfoToDatabase(SQLiteConnection con, HistoryEntry entry)
   at HFM.Instances.UnitInfoDatabase.ImportCompletedUnits(ICollection`1 entries)
   at HFM.Forms.HistoryPresenter.ImportCompletedUnitsClick()
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

When I first ran it about 5 WUs were imported out of over 5000. I managed to get almost all of the 670x's imported properly by editing the separate csv, but the WUs without that issue aren't being imported. The images above showing >5 WUs were taken after the 670x's were imported.

*EDIT*

The issue may be with the particular csv file. The above came from my desktop, which I tried first. I've also installed the new version on my laptop, which obviously has a different csv file, and importing the laptop's local record produced only a few duplicates. What's interesting is that the laptop and desktop are usually on the same network and monitor each other, so most of the WU information is the same (that doesn't explain the supposed 2200 duplicates though, as I imported the desktop csv to the desktop installation first). For fun, I tried importing the desktop's csv to the laptop installation and it reported the exact same number of duplicates as the desktop did.

If you'd like the finicky csv file I'd be happy to send it, though it is over a meg in size.

Hi Zagen,

Thanks for the feedback.

Don't worry about the number of duplicate WUs. This has nothing to do with your clients or setups, the duplicates were a bug in the CompletedUnits.csv writing code. I had several users notice this and it was an issue I wanted to address to the user with the import as a part of the import result message. Since the data is much more accessible in its new database a check is now made against the database to ensure duplicates are not written during the normal HFM data retrieval cycle.

I'm also sorry about your troubles... and quite disappointed. I had hoped this feature would go off without a hitch. I had guys with 10+ megabyte csv files import their data and I had no one experience any exception. The one you've seen appears to be a format issue with the SQL command used to import the data to the database. This could easily have something to do with the data pulled from the csv file. But I can't verify that without the same inputs.

I assume the laptop's csv didn't produce this exception?

Please do send me both your csv files. You can find me at gmail.com... same user name I use here. I'll see if I can reproduce the issue.

[harlam357]

SUCCESS Finally, I was able to get HFM.NET to import my data, well most of it anyways because it gave a message that I had 23 duplicate WUs which I highly doubt (is there a way harlam357 to read the log to see which fields were duplicate?) since I haven't encountered more than 10 errors on my system.

If HFM.NET is giving you an error about importing the data, this is what I did:

...

Now I just have one question, new WUs will be saved in WuHistory.db3 instead of CompletedUnits.csv, right?

Hey Panther,

Thanks for the instructions! This will really help people out. I'll repeat regarding the duplicates, don't worry about it. It's not your setup/client/machine but my code that is at fault.

I don't know why I didn't think about reformatting the column in Excel, that is much easier. See, a couple simple steps and the data file is compatible with the import. This is why I didn't jump through hoops trying to catch every condition in the code.

Yes, the WU Database supersedes the CompletedUnits.csv file. The data is no longer written to the csv file, only the database. I will be adding some Export options in future versions to allow you to pull the data and do whatever you want to with it externally. That just wasn't on the radar for this first revision however.

Please also send me an email at gmail.com. Same user name as here... I have something I'd like to discuss.

[Zagen30]

I assume the laptop's csv didn't produce this exception?

It did not. I've sent you both files.

[harlam357]

Got 'em and reproduced on my install... have to wait when I have some time to debug. It definitely has to do with a value coming from the CompletedUnits.csv and the SQL string I'm using to insert into the database.