New Posts  All Forums:Forum Nav:

Fahmon and V7

post #1 of 7
Thread Starter 
Hello all,
After leaving folding for some time I am finally able to contribute again. Im using my servers I3 2100 to fold. Im having a problem getting Fahmon to work with FAH version 7. Fahmon is installed on my desktop and V7 is on the server. Fahmon wants to point to "fahlog.txt" but v7 is creating "log.txt" What am I doing wrong. Im currently running Folding@home V 6.34 just so it plays nice together with fahmon.

Any suggestions?

Thanks!
My System
(14 items)
 
  
CPUMotherboardGraphicsRAM
Intel E9550 @ 4ghz 1.32v GA-EP45-UD3P EVGA GTX 570 8g GSkill PI Black DDR2 900 
Hard DriveHard DriveCoolingOS
WD 640g AAKS x2 Raid0 Corsair Force SSD Liquid Windows 7 64-Bit 
MonitorKeyboardPowerCase
Samsung 2443bwx Ducky Dragon  580w Mushkin Modded Antec 1200 
Mouse
RAT 7 
  hide details  
Reply
My System
(14 items)
 
  
CPUMotherboardGraphicsRAM
Intel E9550 @ 4ghz 1.32v GA-EP45-UD3P EVGA GTX 570 8g GSkill PI Black DDR2 900 
Hard DriveHard DriveCoolingOS
WD 640g AAKS x2 Raid0 Corsair Force SSD Liquid Windows 7 64-Bit 
MonitorKeyboardPowerCase
Samsung 2443bwx Ducky Dragon  580w Mushkin Modded Antec 1200 
Mouse
RAT 7 
  hide details  
Reply
post #2 of 7

I've never used fahmon, so I had to download it, and check it out.  It looks like it hasn't been updated in a while, and doesn't have support for v7.

 

I would suggest using HFM.net to monitor your progress.  You can download it here: https://code.google.com/p/hfm-net/

 

Once you have it installed, it's pretty easy to get a v7 client added.  There is a 'Client' Menu, then you go to 'Add Client (v7)', then you put in the IP of the workstation, and the password if you have one configured in v7.

 

It should work straight out of the box if you're installing it on the same workstation that is running the v7 client.

 

You don't have to though, if you want HFM.net running on another PC in your network, you will have to edit your v7 config to allow those other PCs on the network access.

post #3 of 7
HFM seems to be the new standard in FAH monitor. FAHMon used to be the standard years ago.

Just remembered.... V7 no longer supports reading the log file directly and instead requires getting info from the log via telnet messages. FAHControl and HFM both work this way.
post #4 of 7
Thread Starter 
Thanks for the help.

So Ive installed HFM on my desktop and V7 on the server. But im still having trouble getting the server to show up in HFM. Ive added my desktop(the monitoring system) ip into the config ip access field. So it now looks like this in the allow field:

127.0.0.1 192.168.1.199

What did I do wrong?
My System
(14 items)
 
  
CPUMotherboardGraphicsRAM
Intel E9550 @ 4ghz 1.32v GA-EP45-UD3P EVGA GTX 570 8g GSkill PI Black DDR2 900 
Hard DriveHard DriveCoolingOS
WD 640g AAKS x2 Raid0 Corsair Force SSD Liquid Windows 7 64-Bit 
MonitorKeyboardPowerCase
Samsung 2443bwx Ducky Dragon  580w Mushkin Modded Antec 1200 
Mouse
RAT 7 
  hide details  
Reply
My System
(14 items)
 
  
CPUMotherboardGraphicsRAM
Intel E9550 @ 4ghz 1.32v GA-EP45-UD3P EVGA GTX 570 8g GSkill PI Black DDR2 900 
Hard DriveHard DriveCoolingOS
WD 640g AAKS x2 Raid0 Corsair Force SSD Liquid Windows 7 64-Bit 
MonitorKeyboardPowerCase
Samsung 2443bwx Ducky Dragon  580w Mushkin Modded Antec 1200 
Mouse
RAT 7 
  hide details  
Reply
post #5 of 7
Quote:
Originally Posted by SDriver View Post

Thanks for the help.

So Ive installed HFM on my desktop and V7 on the server. But im still having trouble getting the server to show up in HFM. Ive added my desktop(the monitoring system) ip into the config ip access field. So it now looks like this in the allow field:

127.0.0.1 192.168.1.199

What did I do wrong?

 

After you made the change, did you restart the client?  Changes don't take effect until you completely stop the client, and restart it.  Because that sounds correct.

 

I typically make any changes needed in the config.xml file, I just find it easier.  I'll put in an IP range too, I have DHCP on on my router, so it ends up looking like this:

 

<command-allow v="127.0.0.1 192.168.1.100-192.168.1.200"/>
<command-allow-no-pass v="127.0.0.1 192.168.1.100-192.168.1.200"/>
<command-port v="36330"/>
post #6 of 7
Thread Starter 
OK, got it. Just had to add the local client in V7 and a restart did the trick.

Thanks!
My System
(14 items)
 
  
CPUMotherboardGraphicsRAM
Intel E9550 @ 4ghz 1.32v GA-EP45-UD3P EVGA GTX 570 8g GSkill PI Black DDR2 900 
Hard DriveHard DriveCoolingOS
WD 640g AAKS x2 Raid0 Corsair Force SSD Liquid Windows 7 64-Bit 
MonitorKeyboardPowerCase
Samsung 2443bwx Ducky Dragon  580w Mushkin Modded Antec 1200 
Mouse
RAT 7 
  hide details  
Reply
My System
(14 items)
 
  
CPUMotherboardGraphicsRAM
Intel E9550 @ 4ghz 1.32v GA-EP45-UD3P EVGA GTX 570 8g GSkill PI Black DDR2 900 
Hard DriveHard DriveCoolingOS
WD 640g AAKS x2 Raid0 Corsair Force SSD Liquid Windows 7 64-Bit 
MonitorKeyboardPowerCase
Samsung 2443bwx Ducky Dragon  580w Mushkin Modded Antec 1200 
Mouse
RAT 7 
  hide details  
Reply
post #7 of 7

Great!

New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Overclock.net Folding@Home Team