FahMon (multi-platform app to monitor various F@h clients)

[jrweiss]

Update: I was able to find out by myself how to get everything to work properly and have succeeded to compile and install FahMon.
I'm completing a couple of Boinc WUs and will launch F@H and FahMon later today for the first time on the Linux box.

How did you solve the libcurl problem? I'm stuck there even after installing libcurl...

[Tynat]

I too have seen FahMon v2.3.99.1 running under WinXP SP2 indicate that either one or both of the paths to the clients are wrong. Upon checking the client's paths, they're filled in with garbage. It appears that FahMon is corrupting parts of it's own preferences, since neither the client or FahMon's install has changed since there respective original installs. I've not had it were I couldn't correct the problem by using the Edit Client function to point FahMon back to the correct client path. After correcting the client path problem, it stays correct for quite awhile.

A more recent and happening more frequent problem is that FahMon is reporting that one or both clients have Hung. The first time this happened both clients were Hung. I restarted FahMon, but that didn't correct the problem. I then restarted both FAH clients and this seemed to fix the problem.

At this very moment, FahMon is reporting that the CPU Console client has Hung, but checking the console shows that the client is progressing normally and that includes FahMon reporting the percentage completed as increasing. Oops, make that both clients are now reported as Hung. There doesn't appear to be anything out of the ordinary in FahMon's Messages Window.

I'm running one CPU Console client and one GPU Console client and both are v6.23. If it matters, the CPU Console client is currently working on Project: 4442 (Run 789, Clone 0, Gen 49) and the GPU Console client is currently working on Project: 5737 (Run 2, Clone 10, Gen 468).

I read that the Hung problem might have something to do with the system clock. I've had the computer's clock synced with Atomic NTP time servers every 3 hours for years and it currently shows the correct time as it was updated 1.5 hours ago. However, we did just go through a time change (lost an hour), and while my computer's clock is accurate, the problem does seem to have cropped up since this time change. I don't know if this is a bi-yearly event as I wasn't running FAH when we last gained an hour.

[bollix47]

@Tynat .... a couple of things you could try:

Go into FahMon preferences and click on the monitoring tab ... put a check mark in the box next to ignore asynchronous clocks.

Also, under the system tab ensure the box next to Manually set timezone to UTC is NOT checked.

[uncle fuzzy]

I do set my time manually. Both Europe and the US changed to winter/standard time in the past 2 weeks. If your computers displayed time differs from FahMons internal set time, manual or auto, you'll see a hung client, even though it continues to process.

[Tynat]

Bingo! The first and only thing I did was remove the check mark from 'Manually set timezone to UTC' and that did the trick. Instantly after clicking the OK button both clients now have green icons. Funny how each client worked for awhile before independently getting Hung at different times.

I don't think it's now necessary, but should I still change 'Ignore asynchronous clocks' under the Monitor tab?

Thanks.

[bollix47]

I think you can leave 'ignore asynchronous clocks' unchecked. Since you are syncing your computers to the atomic clock they should all have the same time anyway. Glad the other preference 'fixed' your problem. It's okay to use the manually set option but you would have to change the offset when the clocks change in the spring and the fall. IMHO it's easier to just leave it unchecked.

[uncle fuzzy]

I think you can leave 'ignore asynchronous clocks' unchecked. Since you are syncing your computers to the atomic clock they should all have the same time anyway. Glad the other preference 'fixed' your problem. It's okay to use the manually set option but you would have to change the offset when the clocks change in the spring and the fall. IMHO it's easier to just leave it unchecked.

I ran into problems when the US changed WHEN they went to and from Daylight Saving Time. My computers also had to be reset. If they including the new offset in an update. I may be able to stop setting them manually.

[Tynat]

Will do. Thanks.

[DonMarkoni]

WHy doesn't FahMon save any settings

- window position
- configuration of fields within window
- columns to display

This is really lame and annoying, any help is appreciated thanks

AFAIK, only window position is not saved. Column choice, column width and everything else is saved.

[7im]

What version of Windows? Windows 7 might not play nice, etc.

[7im]

Sorry, I don't download anything that I don't know where it came from, no offense.

[bruce]

Where did you install FahMon? If the application cannot write to the installation directory, it won't save anything, and Vista/Win7 protect ProgramFiles from unauthorized changes.

[k1wi]

Personally, I'd never even notice if it did or did not save where I put the windows, I rarely close the thing

[Tynat]

Well that could have been put into a code box.

Anyway, here FahMon saves the window size, location and "Work Unit Information" panel width. What it doesn't save by default is the size of the new columns that were recently added. I can spread them apart and the next time FahMon opens all the new columns are completely collapsed. BTW, most of the new column information is redundant and can be found in the "Work Unit Information" panel.

The trick to getting the columns to save is that they have to be activated and not just spread apart. You could say that there is a bug which doesn't hide a column when the column is inactivated (unchecked). So, to save the columns you have to right-click on any column, and then "activate" it, then spread it apart. Or spread it apart and then "activate" it. Either way, the next time you open FahMon, the columns should all be saved.

[Tynat]

Also there's an asterisk next to the PPD listing for my GPU client what does that mean?

Read this here.