Folding Forum

Hey guys

I have a server running and now I would like to add it to the FahMon software. There is only the folding client running on the server (`no Apache or anything else).
It is installed in the root home directory and I think I cant add it by "\\IP\root\folding\fah6\"

What am I doing wrong?

I have installed the SMP Client for my Quad core CPU and the GPU2 for my 9800GT card.

FAHmon shows the progress and info for my CPU but I cannot get the GPU info to show. Is this a GPU2 problem or FAHmon problem.

I had it show the GPU briefly but once I restarted the client it would not show again.

Any ideas?

Which client? The Systray client keeps the folder Fahmon needs to monitor in a hidden folder. I don't remember the exact location.

uncle fuzzy wrote:Which client? The Systray client keeps the folder Fahmon needs to monitor in a hidden folder. I don't remember the exact location.

Open the directory called %APPDATA% and then the subfolder for the gpu. Note the full path name which changes for Vista vs. Seven. You should find the current FAHlog.txt there. Configure Fahmon to point to that location.

That did it.......folder was hidden but I found it with search.

Thank You

Both FahMon and HFM,NET have been stuck on an old WU for over 12 hours now. This is on a GPU systray client, which continues to chug away successfully completing WU after WU since the offending one (P5737 R1, C572, G163) has "stuck" both HFM,NET and FahMon. The log file shows that the offending WU successfully completed just after midnight (local time) more than 12 ours ago. Any idea on how to fix this?

FahMon messages states that my client "is stopped (The line "Folding@Home Client Shutdown." was found)

Muffel2k wrote:Hey guys

I have a server running and now I would like to add it to the FahMon software. There is only the folding client running on the server (`no Apache or anything else).
It is installed in the root home directory and I think I cant add it by "\\IP\root\folding\fah6\"

What am I doing wrong?

Most machines will not allow root to connect directly.
You really should create a new user for folding on that machine.
Running things as root is asking for a security problem.

Solved - I had the log directory pointing to the wrong place. Duh.

bcblues wrote:Both FahMon and HFM,NET have been stuck on an old WU for over 12 hours now. This is on a GPU systray client, which continues to chug away successfully completing WU after WU since the offending one (P5737 R1, C572, G163) has "stuck" both HFM,NET and FahMon. The log file shows that the offending WU successfully completed just after midnight (local time) more than 12 ours ago. Any idea on how to fix this?

FahMon messages states that my client "is stopped (The line "Folding@Home Client Shutdown." was found)

Does anyone have a link for a Ubuntu installer (9.04 and/or 10.10)? Or instructions for a Linux newbie for installing from the source package?

David

EDIT: Resolved: Instructions available at https://help.ubuntu.com/community/FoldingAtHome/FahMon worked for me -- there is a missing library in some other versions. However, Fahmon would not access the wine subdirectory with the gpu under Linux -- so I'm using HFM via network shares, which seems to be OK.

I seem to be having issues with fahmon reporting some bogus PPD on W7 x64. The reported PPD is much higher than what it should be. For example, it reports a constant 20-28k PPD for each of my GTX 560 Tis, and on occasion it thinks my SMP client is capable of 50k+ PPD. Started running HFM for comparison and the numbers I get there are more sane.

I too have some PPD issue with FahMon version 2.3.99.4 but version 2.3.399.3 worked fine for some donors (I didn't try it). Maybe you can give it a try if you want.

Using FahMon version 2.3.99.4 on Windows 7 64bit. I have an iMac client storing it's work data and logs on a share accessible to Windows. The iMac is using AFP to write data, but the line endings seem to match the other clients. Anyway, Windows FahMon doesn't appear to be able to provide project information for the iMac client. It works fine for Linux clients (both native and VMWare), as well as Windows SMP and GPU clients running locally. Has anyone else seen this issue?

I can provide screenshots and data files if necessary.

Hello all!,

It appears that when I installed FAHMon (2.3.99.3 or 2.3.99.4) in Win2000 with SP4, it gives me an error saying it is not a valid Win32 application. Can someone please help me get this running so I can monitor my client on this system?

Thanks in advanced,

COOLDUDEGAMER

Hello,

After a long hiatus I'm slowly getting back into doing some folding. To begin, I decided to first update the software on the WinXP machine. Leaving the old software in place, I started fresh with a new directory layout. I updated the GPU2 v6.23 console client for the HD3850 card to the new GPU3 v6.41r2 console client. That seems to be working fine. Next, I updated FahMon v2.3.99.1 to FahMon v2.3.99.4 and added a new GPU3 console client entry. Everything appears to be working fine with FahMon except for the ETA and the PPD column calculations. No matter how long the client runs, these columns never update.

After a couple of hours of playing with settings and doing searches, I decided to try something different. The Win7 laptop still has the old software installed (GPU2 v6.23 and FahMon v2.3.99.1). On the laptop, I started the old FahMon, edited the old HD3850 client entry to point it to the new GPU3 location over the LAN on the WinXP machine and the ETA and the PPD appear in old FahMon v2.3.99.1 on the laptop. I decided to try the reverse. I started the laptop's old GPU2 console client and on the WinXP machine I added the client to point over the LAN to the laptop's GPU2 console client. Now the new FahMon is listing two clients, but both ETA and PPD columns are not updating. Apparently, the ETA and PPD work in the old FahMon for both GPU2 and GPU3, but neither GPU2 or GPU3 ETA and PPD work in the new FahMon.

I've compared the settings of both FahMon programs and with the exception the Project URL under the Advance tab, they have identical settings. Based on all of this, it seems to me that there is a ETA and PPD issue with the new v2.3.99.4 FahMon.

Anyone have any suggestions as to why the old FahMon works correctly and the new FahMon doesn't?

I should have made it clearer in the last post that I do not use the FahMon installer package. All installs of FahMon have been from the ZIP archive. Every time FahMon is started, it is done so from a Command window using the -L switch. IMO, that feature should be an option inside the program's preferences so that it's always available regardless of how FahMon is started.

Moved the FahMon v2.3.99.4 directory out of the way. Then unpacked the FahMon v2.3.99.3 ZIP package and started FahMon. As soon as I added the GPU3 console client for the HD3850, the box turned "green". The ETA and PPD appeared.

Moved the FahMon v2.3.99.3 directory out of the way. Then unpacked the FahMon v2.3.99.4 ZIP package and started FahMon. As soon as I added the GPU3 console client for the HD3850, the box turned "yellow". The ETA and PPD didn't appear.

Since the Message window doesn't display any errors with FahMon v2.3.99.4 running, I unchecked "Log error messages only" under the Advance tab. Besides a "Triggered auto-reload of local clients", the following appeared multiple times:

• [08/06/11 - 13:39:16.653] Reloading HD3850
• [08/06/11 - 13:39:16.684] HD3850 has an unknown state (Unable to find a complete frame)
• [08/06/11 - 13:39:16.684] Cannot determine frame number for HD3850 (this isn't a problem)
• [08/06/11 - 13:39:16.684] Finished Reloading HD3850

Swapping the 2.3.99.4 directory for the 2.3.99.3 directory and again I unchecked "Log error messages only" under the Advance tab. Besides a "Triggered auto-reload of local clients", the following appeared multiple times:

• [08/06/11 - 14:07:43.013] Reloading HD3850
• [08/06/11 - 14:07:43.028] HD3850 is on frame 22
• [08/06/11 - 14:07:43.028] Finished Reloading HD3850

Since both have the wrong date, it's not August, that can't be it. Although, if it's not the wrong date and it's a date format thing, a more universal date format such as yyyy-mm-dd would improve readability tremendously. In any case, the frame count increased as expected with each iteration.

I don't know if 2.3.99.3 just doesn't display as much information as v2.3.99.4 or that despite the "this isn't a problem" indicator, v2.3.99.4 IS indicating a problem. Clearly, the messages are different, even though the client and the FahMon preferences are the same.