FCI: Folding@Home Client Info (Web based client monitor)

[jimerickson]

how does one designate multiple client-name and fah-dir in fci-client.conf or on the command line? right now it only updates the smp2 client. my config file is as follows (could someone post their confg file?):

Code: Select all

#
# File: fci-client.conf
#
# fci-client.pl configuration file
#

# FCI Server URL - Parameter: --url
url: http://jimerickson.dyndns.org/fci/index.pl

# FCI Username - Parameter: --username
username: xxxxx

# FCI Password - Parameter: --password
password: xxxxxx

# FCI client name - Parameter: --name | --client (depricated)
client-name: gpu3
client-name: smp2

# Folding@Home client directory - Parameter: --dir
fah-dir: /home/gpu3/
fah-dir: /home/smp2/

# Verbose (Debug) Output - Parameter: --verbose
verbose: 1

[smoking2000]

See the help text of FCI client:

Code: Select all

$ fci-client.pl --help
fci-client.pl v1.5 with qd [qd released 13 March 2009 (fr 073)]

Usage: fci-client.pl [OPTIONS]

Options:
--url <url>           URL to POST the data to               (http://fci.fatalerrorgroup.com/index.pl)
--username <string>   Server authentication username        (bas)
--password <string>   Server authentication password        (somepass)
--useragent <name>    User-Agent string                     (fci-client/1.5)

--name <name>         Client name                           (osiris)
--dir <directory>     Folding@Home client directory         (/home/bas/software/folding/)
--skip-xyz            Don't upload the file current.xyz     (false)
--skip-client-cfg     Don't upload the file client.cfg      (false)
--skip-unitinfo       Don't upload the file unitinfo.txt    (false)
--skip-fahlog         Don't upload the file FAHlog.txt      (false)
--skip-fahlog-prev    Don't upload the file FAHlog-Prev.txt (false)
--skip-myfolding      Don't upload the file MyFolding.html  (false)

--fci-dir <directory> FCI directory                         (/home/bas/.fci/)
--qd <path>           Path to the qd executable             (/usr/local/bin/qd)
--qdinfo <path>       Path to the qdinfo.dat file           (/home/bas/.fci/qdinfo.dat)
--update-qd           Update the qd binary                  (false)
--no-qd-update        Don't update any qd files             (false)
--save-config         Save the configuration to file        (false)
--config-file <path>  Path to the configuration file        (/home/bas/.fci/fci-client.conf)

--verbose             Verbose (debug) output                (off)
--help                Print this information

To update your ~/.fci/fci-client.conf specify all arguments you want to save in the config file on the commandline and add --save-config:

Code: Select all

fci-client.pl --url http://example.com/fci/index.pl --name myclient-gpu --dir /home/user/folding-gpu/ --save-config

[jimerickson]

smoking2000

getting lots of mail from fci about not being able to connect to your website to update qd files (connection timed out). thought you might like to know.

[rhavern]

smoking2000

getting lots of mail from fci about not being able to connect to your website to update qd files (connection timed out). thought you might like to know.

+1, looks like it started yesterday

[rhavern]

Smoking2000, I'm getting some stats oddities. For some reason, some of the GPU clients are coming up with unlikely PPD and differing BPPD. As far as I'm aware, there aren't any GPU projects that use the quick return bonus.


EDIT2: I think this may not be related to FCI. Server2 seems to have gone insane WRT time. The built-in XP time service isn't man enough for the job it appears. I've installed a full NTP implementation and that seems to have solved it. The following two errors are still present.

EDIT:
Noted this in my mail
/usr/local/bin/fci-update-xml-files.pl --dir /var/www/fci/

Use of uninitialized value within @arguments in pattern match (m//) at /usr/local/bin/fci-update-xml-files.pl line 2844.
Use of uninitialized value within @arguments in pattern match (m//) at /usr/local/bin/fci-update-xml-files.pl line 2844.

and as previously reported
Error: Failed to retrieve URL! (http://linuxminded.xs4all.nl/software/q ... qdinfo.dat)
Server returned: 500 Can't connect to linuxminded.xs4all.nl:80 (connect: Connection timed out)

[Magic Michael]

Smoking' , could you please have a look at your webserver ? I get timeouts when I try to open a page like http://fci.bile.nl/?target=install.plc&os=Windows. Thanks.

[smoking2000]

My server crashed while I was on vacation in Hungary for the past 2,5 weeks. I just returned an hour ago and rebooted the server, it should work as expected again.

[smoking2000]

EDIT:
Noted this in my mail
/usr/local/bin/fci-update-xml-files.pl --dir /var/www/fci/

Use of uninitialized value within @arguments in pattern match (m//) at /usr/local/bin/fci-update-xml-files.pl line 2844.
Use of uninitialized value within @arguments in pattern match (m//) at /usr/local/bin/fci-update-xml-files.pl line 2844.

This has something to do with Arguments parsing from FAHlog. I'll need some Arguments: lines from the FAHlogs in question if you stil have those to debug this.

[rhavern]

What logs do you need? Happy to pass on whatever.

Hope you had a good vacation and welcome back.

[smoking2000]

I need the FAHlog.txt and/or FAHlog-Prev.txt from the clients in question, verbose output of fci-update-xml-files.pl will make it easier to determine which clients are affected.

My 7th time on the Sziget Festival was a major success, and driving through Germany on the Autobahn is wonderful. Especially compared to our Dutch highways which are infested by idiots that should have their license revoked.

[smoking2000]

For those of you also experiencing the "Use of uninitialized value within @arguments in pattern match (m//) at /usr/local/bin/fci-update-xml-files.pl line 2844." warning, this was fixed in SVN r113 and will be included the next release.

For now it's only available in Subversion.

[jimerickson]

getting this in my mail recently concerning /usr/local/bin/fci-update-stanford-files.pl --dir /var/www/fci/. am i doing something wrong?

Code: Select all

Warning: Cannot parse project line (psummary.html:309):
<tr bgcolor="#ffffff"> <td>10510</td><td>171.64.65.61</td><td>p10510_ntl9(1-56)_WT_300K</td><td>908</td><td>8.00</td><td>12.00</td><td>587.00</td><td>100</td><td>GROGPU2</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject.overusingIPswillbebanned?p=10510">Description</a></td><td><font size="-1">vvoelz</font></td><td>0.00</td></tr>
Warning: Cannot parse project line (psummary.html:310):
<tr bgcolor="#dfdfdf"> <td>10511</td><td>171.64.65.61</td><td>p10511_ntl9(1-56)_WT</td><td>908</td><td>8.00</td><td>12.00</td><td>587.00</td><td>100</td><td>GROGPU2</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject.overusingIPswillbebanned?p=10511">Description</a></td><td><font size="-1">vvoelz</font></td><td>0.00</td></tr>
Warning: Cannot parse project line (psummary.html:311):
<tr bgcolor="#ffffff"> <td>10512</td><td>171.64.65.61</td><td>p10512_ntl9(1-56)_WT</td><td>908</td><td>8.00</td><td>12.00</td><td>587.00</td><td>100</td><td>GROGPU2</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject.overusingIPswillbebanned?p=10512">Description</a></td><td><font size="-1">vvoelz</font></td><td>0.00</td></tr>
Warning: Cannot parse project line (psummary.html:312):
<tr bgcolor="#dfdfdf"> <td>10513</td><td>171.64.65.61</td><td>p10513_ntl9(1-56)_WT</td><td>908</td><td>8.00</td><td>12.00</td><td>587.00</td><td>100</td><td>GROGPU2</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject.overusingIPswillbebanned?p=10513">Description</a></td><td><font size="-1">vvoelz</font></td><td>0.00</td></tr>
Warning: Cannot parse project line (psummary.html:313):
<tr bgcolor="#ffffff"> <td>10514</td><td>171.64.65.61</td><td>p10514_ntl9(1-56)_WT</td><td>908</td><td>8.00</td><td>12.00</td><td>587.00</td><td>100</td><td>GROGPU2</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject.overusingIPswillbebanned?p=10514">Description</a></td><td><font size="-1">vvoelz</font></td><td>0.00</td></tr>
Warning: Cannot parse project line (psummary.html:314):
<tr bgcolor="#dfdfdf"> <td>10515</td><td>171.64.65.61</td><td>p10515_ntl9(1-56)_WT</td><td>908</td><td>8.00</td><td>12.00</td><td>587.00</td><td>100</td><td>GROGPU2</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject.overusingIPswillbebanned?p=10515">Description</a></td><td><font size="-1">vvoelz</font></td><td>0.00</td></tr>
Warning: Cannot parse project line (psummary.html:315):
<tr bgcolor="#ffffff"> <td>10516</td><td>171.64.65.61</td><td>p10516_ntl9(1-56)_WT</td><td>908</td><td>8.00</td><td>12.00</td><td>587.00</td><td>100</td><td>GROGPU2</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject.overusingIPswillbebanned?p=10516">Description</a></td><td><font size="-1">vvoelz</font></td><td>0.00</td></tr>

[smoking2000]

No, the characters used in the WU name changed with these projects, and the regex that parses the psummary pages had to be updated.

This was fixed in SVN r99 on June 15th, but like the @arguments fix this has not made it to the next release yet. I'm still working out some last issues, and my vacation did not speed up this process.

You can get the updated fci-update-stanford-files.pl from Subversion to parse these projects.

[jimerickson]

switched to svn r113 and it fixed the parsing problem. thanks! but now i am getting mails about fci-update-project-images.pl that state

Code: Select all

Error: Invalid trajectory ID! (r)

should i ignore these?

[smoking2000]

You can ignore them, but I'm interested to know why you're getting this error. Can you post the verbose output?