Folding Forum

Community driven support forum for Folding@home
https://foldingforum.org/

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

https://foldingforum.org/viewtopic.php?t=8109

Page 8 of 23

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

Posted: Tue Apr 14, 2009 2:07 pm
by rhavern
I've emailed two different outputs of the WMI script to you, hope it helps.

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

Posted: Tue Apr 14, 2009 5:15 pm
by Hyperlife
smoking2000 wrote:High performance GPU stuff does not match with running Linux, the driver mess for Nvidia cards on Linux is one aspect, having expensive GPUs in a headless server is another.
Actually, that's exactly what I have set up -- 3 GPUs folding headless under Linux, and it works fine.

New release of FCI: v1.5

Posted: Wed Apr 15, 2009 8:13 pm
by smoking2000
New release of FCI: v1.5

New features in this release include RRD based graphs for the EOC data, these graphs cover 1 year of history for each username.
This feature requires that the Perl module RRDs and its dependencies are installed. See the INSTALL documentation for more information how to install the new dependencies of FCI: RRDs & Date::Format (TimeDate).

New features in this release include RRD based graphs for the EOC data, these graphs cover 1 year of history for each username.

Also new in this release is WMI based hardware & OS info detection on Windows, besides the CPU, RAM & OS info already detected by previous FCI client versions, this version also includes the load (of the 1st CPU) together with the uptime. And it also reports the 1st GPU detected. A future release will support multiple CPUs & GPUs, but this requires more drastic changes in the framework.

The bug in fci-update-xml-files.pl where it would corrupt the XML files it updates if it did not find any client-data to process, has also been fixed in this release. You don't have to upload client-data before the first fci-update-xml-files.pl run anymore, but this is still recommended though.


The lastest FCI release (and previous releases) can be downloaded from the project website:
http://fci.bile.nl/?target=downloads.plc

Or you can use the direct link:
http://fci.bile.nl/downloads/fci-1.5.tar.gz

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

Posted: Thu Apr 16, 2009 5:58 pm
by rhavern
Is it necessary to update the server before the clients for everything to work correctly?

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

Posted: Thu Apr 16, 2009 6:09 pm
by smoking2000
An older FCI server will not use the additional data uploaded by the new FCI clients, so this is no problem. You can upgrade the client and/or server by appending the --upgrade argument to the install.pl command you used to install it the first time.

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

Posted: Fri Apr 17, 2009 11:57 am
by rhavern
During my 1.5 upgrade, I got this output, is it anything to worry about? The new perl modules had already been installed.

Code: Select all

<snip>
Changing back to directory: /var/tmp/fci-1.5

No support for extra, skipping.
No support for fci-analyse-clients.pl, skipping.
No support for fci-generate-queue-graphs-ng.pl, skipping.
Copying script: ./scripts/fci-generate-queue-graphs.pl -> /usr/local/bin/fci-generate-queue-graphs.pl
<snip>

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

Posted: Fri Apr 17, 2009 12:38 pm
by smoking2000
This is nothing to worry about, the installer simply reports that it will not install content from the scripts directory of the FCI tarball because it's not known to be required. This used to break the config.xml, so this check was added in FCI v1.0 on 2007-10-04.

The extra directory holds some scripts which may or may not be useful to FCI administrators, but they were useful to me at some point in time.
This directory holds three scripts currently:
* fci-update-known-projects.pl
* list-teamstats-files.pl
* windows-management-instrumentation.pl (last modified: 2009-04-13)

fci-update-known-projects.pl could be used to recreate the known-projects.xml by processing the content of the project-data directory of the FCI server. I used this before the installer preserved the xml-data directory content, to recreate the known-projects.xml. This script is not really usefull anymore these days, but it's not in the way either. It was last modified on 2008-12-25.

list-teamstats-files.pl checks which teamstats files are available on the Stanford webserver, when they were last modified, and their filesize. Example:

Code: Select all

$ ./scripts/extra/list-teamstats-files.pl | head -11
Downloading URL: http://fah-web.stanford.edu/teamstats/ ... Success
Total teams: 5041
Total files: 10082

Team : 0
 html: http://fah-web.stanford.edu/teamstats/team0.html 2009-04-17 04:32 (38.4M)
  txt: http://fah-web.stanford.edu/teamstats/team0.txt  2009-04-17 04:32 (12.4M)

Team : 1
 html: http://fah-web.stanford.edu/teamstats/team1.html 2009-04-17 04:34 (1.3M)
  txt: http://fah-web.stanford.edu/teamstats/team1.txt  2009-04-17 04:34 (401k)
This script was used for development of the teamstats related code early in the FCI history. It was last modified on 2006-03-19.

windows-management-instrumentation.pl is a recent edition (last modified: 2009-04-13), it's the script to dump the most important WMI data on Windows. Whenever a user will post that its Windows client data was wrongfully detected I will ask him/her to run this script for debugging purposes.

fci-analyse-clients.pl is an upcoming feature that has been in a partial completed stage of development from quite some time now. It checks for certain important event, like deleted WUs in the queue and reports this. But because FCI lacks the context awareness of the FAHlog events it's not really useful yet. The intention of this script is to report not just which errors were detected, but also the relevant FAHlog.txt lines, and if possible recommend solutions to fix this. This also depends on an improved FAHlog parser in FCI, but the FAHlog format is quite a piece of shit to parse meaningfully. I don't expect this script to be completed in the near future, several of the noticeable events are now already reported by FCI using the state markers, so I'm not in a hurry.

fci-generate-queue-graphs-ng.pl is another in development script, it was intended to replace the fci-generate-queue-graphs-ng.pl and adds a graph of the TPF similar to the graphs the now deceased FAHChart used to generate. I don't think I'll every finish this script, it will likely be replaced by RRD based graphs of the TPF once I have improved the FAHlog parsers to be aware of the date on which messages are logged. Or at least make an informed guess at which date they were logged on because the FAHlog doesn't log dates, only times, for each FAHlog line.

So nothing to worry about, if it were, the installer would have choked and thrown an error.

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

Posted: Mon Apr 20, 2009 10:45 am
by rhavern
Thanks for the explanation.

I've upgraded my client and servers to 1.5 some days ago and the rrd doesn't seem to be updating. I've got a single entry (the first one it appears) but it hasn't changed since then. Where should I be looking? Everything else seems to be functioning correctly, including the new WMI code.

Image

Many thanks!

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

Posted: Mon Apr 20, 2009 11:11 am
by smoking2000
The RRDs under the Usernames section are updated every 3 hours by the fci-update-eoc-stats.pl script.

By the looks of it, it appears to be functioning correctly. The last update was on 2009-04-20 08:40, the next update will be on 2009-04-20 11:40 which it's not yet.

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

Posted: Mon Apr 20, 2009 1:55 pm
by rhavern
Yes, it shows that the graph is updating but I don't think the values are correct. It seems very unlikely that my 24 hour average has stayed exactly the same for the past three days. My current stats according to FCI are:

Code: Select all

Credits	:	1112924
Work Units	:	6639
Team Rank	:	56
Rank	:	5141
24hr Avg	:	9263
But EOC shows:

Code: Select all

Team 	Rank         54  	
Project 	Points        4,969
Last 24hr 	Points 	8,428
24hr Avg 	Points  	8,944
Today 	Points  	1,876
Week 	Points  	11,114
Total 	WUs  	        1,141,940
As I am turning in about 9kPPD, the FCI numbers are a few days stale vs EOC. It appears that the first EOC update when the server went to v1.5 (Friday) is the last update that worked.

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

Posted: Mon Apr 20, 2009 2:26 pm
by smoking2000
RRDtool consolidates its Primary Date Points (the values added every update) using the AVERAGE value of a single PDP to create a Consolidated Data Point, it stores 8 such CDPs in the Round Robin Archive for the current day (1day RRA) [1 PDP every 3 hours, 1 PDP per CDP, so 8 CDPs cover 24 hours].

There is another RRA convering 1 week (7 days), it uses 8 PDPs to form one CDP, this CDP contains the AVERAGE of the 8 PDPs. And 7 such CDPs are stored in RRA for the current week (1week RRA) [8 PDPs per CDP, so 1 CDP covers 24 hours, and 7 CDPs cover 7 days]. But because the PDPs are consolidated using the AVERAGE consolidation function, minor ups and downs in the points_24hr_avg can vanish if your output is nearly constant. This could explain your flat line.

But if you want to know for sure if the script actually updates the RRD you need to append --verbose to your fci-update-eoc-stats.pl command, and see what its output reports in the cron emails that will be sent when the job is run. For cron to send the output of the scripts it runs via email, you need to have a working SMTP server installed with an /etc/aliases configuration which forwards email of the account to a real email account (since I assume your not running your own mailserver on the system too).

It's not recommended to run the fci-update-eoc-stats.pl manually, because the RRD expects updates every 3 hours, not more often. This will mess up the consolidation of the PDPs to CDPs because there are now more PDPs than expected in the heartbeat timeframe.

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

Posted: Mon Apr 20, 2009 3:14 pm
by rhavern
Okay, that possibly explains the graph being out, but the numbers I included were from the User Information column. Shouldn't those numbers be within an EOC update of correct, i.e. 3 hours?

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

Posted: Mon Apr 20, 2009 6:40 pm
by smoking2000
The number reported in the User Information section is the actual value in the EOC XML data. It should match


It could be that the hours on which fci-update-eoc-stats.pl is scheduled don't match up very well with the update cycle of EOC in your timezone.

The INSTALL documentation says:

Code: Select all

40 2,5,8,11,14,17,20,23 * * * /usr/local/bin/fci-update-eoc-stats.pl --dir /var/www/fci/
This corresponds to the following situation in my case:

Code: Select all

FCI cronjob time      | EOC stats update time
----------------------+----------------------
02:40 CET (00:40 UTC) | 18:00 CDT (23:00 UTC)
05:40 CET (03:40 UTC) | 21:00 CDT (02:00 UTC)
08:40 CET (06:40 UTC) | 00:00 CDT (05:00 UTC)
11:40 CET (09:40 UTC) | 03:00 CDT (08:00 UTC)
14:40 CET (12:40 UTC) | 06:00 CDT (11:00 UTC)
17:40 CET (15:40 UTC) | 09:00 CDT (14:00 UTC)
20:40 CET (18:40 UTC) | 12:00 CDT (17:00 UTC)
23:40 CET (21:40 UTC) | 15:00 CDT (20:00 UTC)
I think your timezone is GMT since you're in the UK, assuming this for your case, the situation is:

Code: Select all

FCI cronjob time      | EOC stats update time
----------------------+----------------------
02:40 GMT (02:40 UTC) | 21:00 CDT (02:00 UTC)
05:40 GMT (05:40 UTC) | 00:00 CDT (05:00 UTC)
08:40 GMT (08:40 UTC) | 03:00 CDT (08:00 UTC)
11:40 GMT (11:40 UTC) | 06:00 CDT (11:00 UTC)
14:40 GMT (14:40 UTC) | 09:00 CDT (14:00 UTC)
17:40 GMT (17:40 UTC) | 12:00 CDT (17:00 UTC)
20:40 GMT (20:40 UTC) | 15:00 CDT (20:00 UTC)
23:40 GMT (23:40 UTC) | 18:00 CDT (23:00 UTC)
This doesn't look like much lag between the EOC updates and the times your FCI cronjobs are scheduled. The 40 minutes past the whole hour time was chosen because it took the EOC server about 30 minutes to update the stats, so FCI would fetch the most recent data as possible.

To check if your FCI update jobs are scheduled inefficiently in regards to the EOC update times, see which timestamp is stored for the <Last_Update> element in your EOC XML after the next cronjob has run. The timestamp should match the most recent update shown of the EOC website.

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

Posted: Tue Apr 21, 2009 7:57 am
by rhavern
Yes, my last update in the graph is exactly as you thought it would be. However, none of the numbers have changed since I last posted:

Code: Select all

Username	:	rhavern
Team	:	14
Credits	:	1112924
Work Units	:	6639
Team Rank	:	56
Rank	:	5141
24hr Avg	:	9263
I ran fci-update-eoc-stats.pl manually with a --verbose:

Code: Select all

/usr/local/bin/fci-update-eoc-stats.pl --dir /var/www/fci/ --verbose
Changing working directory to: /var/www/fci/

Retrieving URL: http://folding.extremeoverclocking.com/xml/user_summary.php?un=rhavern&t=14 ... Success
rrdupdate eoc-data/rhavern-14.rrd
        --template Team_Rank:Overall_Rank:Points_24hr_Avg:Points:WUs
        1240294609:56:5076:9263:1113308:6640
rrdgraph eoc-data/rhavern-14-Points_24hr_Avg-1day-small.png
        --start -24hours
        --end 1240294609
        --vertical-label "Points 24hr Avg"
        --width 300
        --height 100
        --imgformat PNG
        DEF:Points_24hr_Avg=eoc-data/rhavern-14.rrd:Points_24hr_Avg:AVERAGE
        LINE1:Points_24hr_Avg#0000FF:Points 24hr Avg
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 397x168
Averages: 
rrdgraph eoc-data/rhavern-14-Team_Rank-1day.png
        --start -24hours
        --end 1240294609
        --title "rhavern (14) - Team Rank"
        --vertical-label "Team Rank"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Team_Rank=eoc-data/rhavern-14.rrd:Team_Rank:AVERAGE
        LINE1:Team_Rank#0000FF:Team Rank
        GPRINT:Team_Rank:AVERAGE:Avg\: %.2lf %s
        GPRINT:Team_Rank:MIN:Min\: %.2lf %s
        GPRINT:Team_Rank:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x268
Averages: 
rrdgraph eoc-data/rhavern-14-Team_Rank-1week.png
        --start -168hours
        --end 1240294609
        --title "rhavern (14) - Team Rank"
        --vertical-label "Team Rank"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Team_Rank=eoc-data/rhavern-14.rrd:Team_Rank:AVERAGE
        LINE1:Team_Rank#0000FF:Team Rank
        GPRINT:Team_Rank:AVERAGE:Avg\: %.2lf %s
        GPRINT:Team_Rank:MIN:Min\: %.2lf %s
        GPRINT:Team_Rank:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x268
Averages: 
rrdgraph eoc-data/rhavern-14-Team_Rank-1month.png
        --start -744hours
        --end 1240294609
        --title "rhavern (14) - Team Rank"
        --vertical-label "Team Rank"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Team_Rank=eoc-data/rhavern-14.rrd:Team_Rank:AVERAGE
        LINE1:Team_Rank#0000FF:Team Rank
        GPRINT:Team_Rank:AVERAGE:Avg\: %.2lf %s
        GPRINT:Team_Rank:MIN:Min\: %.2lf %s
        GPRINT:Team_Rank:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x268
Averages: 
rrdgraph eoc-data/rhavern-14-Team_Rank-1year.png
        --start -8784hours
        --end 1240294609
        --title "rhavern (14) - Team Rank"
        --vertical-label "Team Rank"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Team_Rank=eoc-data/rhavern-14.rrd:Team_Rank:AVERAGE
        LINE1:Team_Rank#0000FF:Team Rank
        GPRINT:Team_Rank:AVERAGE:Avg\: %.2lf %s
        GPRINT:Team_Rank:MIN:Min\: %.2lf %s
        GPRINT:Team_Rank:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x268
Averages: 
rrdgraph eoc-data/rhavern-14-Overall_Rank-1day.png
        --start -24hours
        --end 1240294609
        --title "rhavern (14) - Overall Rank"
        --vertical-label "Overall Rank"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Overall_Rank=eoc-data/rhavern-14.rrd:Overall_Rank:AVERAGE
        LINE1:Overall_Rank#0000FF:Overall Rank
        GPRINT:Overall_Rank:AVERAGE:Avg\: %.2lf %s
        GPRINT:Overall_Rank:MIN:Min\: %.2lf %s
        GPRINT:Overall_Rank:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x268
Averages: 
rrdgraph eoc-data/rhavern-14-Overall_Rank-1week.png
        --start -168hours
        --end 1240294609
        --title "rhavern (14) - Overall Rank"
        --vertical-label "Overall Rank"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Overall_Rank=eoc-data/rhavern-14.rrd:Overall_Rank:AVERAGE
        LINE1:Overall_Rank#0000FF:Overall Rank
        GPRINT:Overall_Rank:AVERAGE:Avg\: %.2lf %s
        GPRINT:Overall_Rank:MIN:Min\: %.2lf %s
        GPRINT:Overall_Rank:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x268
Averages: 
rrdgraph eoc-data/rhavern-14-Overall_Rank-1month.png
        --start -744hours
        --end 1240294609
        --title "rhavern (14) - Overall Rank"
        --vertical-label "Overall Rank"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Overall_Rank=eoc-data/rhavern-14.rrd:Overall_Rank:AVERAGE
        LINE1:Overall_Rank#0000FF:Overall Rank
        GPRINT:Overall_Rank:AVERAGE:Avg\: %.2lf %s
        GPRINT:Overall_Rank:MIN:Min\: %.2lf %s
        GPRINT:Overall_Rank:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x268
Averages: 
rrdgraph eoc-data/rhavern-14-Overall_Rank-1year.png
        --start -8784hours
        --end 1240294609
        --title "rhavern (14) - Overall Rank"
        --vertical-label "Overall Rank"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Overall_Rank=eoc-data/rhavern-14.rrd:Overall_Rank:AVERAGE
        LINE1:Overall_Rank#0000FF:Overall Rank
        GPRINT:Overall_Rank:AVERAGE:Avg\: %.2lf %s
        GPRINT:Overall_Rank:MIN:Min\: %.2lf %s
        GPRINT:Overall_Rank:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x268
Averages: 
rrdgraph eoc-data/rhavern-14-Points_24hr_Avg-1day.png
        --start -24hours
        --end 1240294609
        --title "rhavern (14) - Points 24hr Avg"
        --vertical-label "Points 24hr Avg"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Points_24hr_Avg=eoc-data/rhavern-14.rrd:Points_24hr_Avg:AVERAGE
        LINE1:Points_24hr_Avg#0000FF:Points 24hr Avg
        GPRINT:Points_24hr_Avg:AVERAGE:Avg\: %.2lf %s
        GPRINT:Points_24hr_Avg:MIN:Min\: %.2lf %s
        GPRINT:Points_24hr_Avg:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x268
Averages: 
rrdgraph eoc-data/rhavern-14-Points_24hr_Avg-1week.png
        --start -168hours
        --end 1240294609
        --title "rhavern (14) - Points 24hr Avg"
        --vertical-label "Points 24hr Avg"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Points_24hr_Avg=eoc-data/rhavern-14.rrd:Points_24hr_Avg:AVERAGE
        LINE1:Points_24hr_Avg#0000FF:Points 24hr Avg
        GPRINT:Points_24hr_Avg:AVERAGE:Avg\: %.2lf %s
        GPRINT:Points_24hr_Avg:MIN:Min\: %.2lf %s
        GPRINT:Points_24hr_Avg:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x268
Averages: 
rrdgraph eoc-data/rhavern-14-Points_24hr_Avg-1month.png
        --start -744hours
        --end 1240294609
        --title "rhavern (14) - Points 24hr Avg"
        --vertical-label "Points 24hr Avg"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Points_24hr_Avg=eoc-data/rhavern-14.rrd:Points_24hr_Avg:AVERAGE
        LINE1:Points_24hr_Avg#0000FF:Points 24hr Avg
        GPRINT:Points_24hr_Avg:AVERAGE:Avg\: %.2lf %s
        GPRINT:Points_24hr_Avg:MIN:Min\: %.2lf %s
        GPRINT:Points_24hr_Avg:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x268
Averages: 
rrdgraph eoc-data/rhavern-14-Points_24hr_Avg-1year.png
        --start -8784hours
        --end 1240294609
        --title "rhavern (14) - Points 24hr Avg"
        --vertical-label "Points 24hr Avg"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Points_24hr_Avg=eoc-data/rhavern-14.rrd:Points_24hr_Avg:AVERAGE
        LINE1:Points_24hr_Avg#0000FF:Points 24hr Avg
        GPRINT:Points_24hr_Avg:AVERAGE:Avg\: %.2lf %s
        GPRINT:Points_24hr_Avg:MIN:Min\: %.2lf %s
        GPRINT:Points_24hr_Avg:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x268
Averages: 
rrdgraph eoc-data/rhavern-14-Points-1day.png
        --start -24hours
        --end 1240294609
        --title "rhavern (14) - Points"
        --vertical-label "Points"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Points=eoc-data/rhavern-14.rrd:Points:AVERAGE
        LINE1:Points#0000FF:Points
        GPRINT:Points:AVERAGE:Avg\: %.2lf %s
        GPRINT:Points:MIN:Min\: %.2lf %s
        GPRINT:Points:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x254
Averages: 
rrdgraph eoc-data/rhavern-14-Points-1week.png
        --start -168hours
        --end 1240294609
        --title "rhavern (14) - Points"
        --vertical-label "Points"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Points=eoc-data/rhavern-14.rrd:Points:AVERAGE
        LINE1:Points#0000FF:Points
        GPRINT:Points:AVERAGE:Avg\: %.2lf %s
        GPRINT:Points:MIN:Min\: %.2lf %s
        GPRINT:Points:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x254
Averages: 
rrdgraph eoc-data/rhavern-14-Points-1month.png
        --start -744hours
        --end 1240294609
        --title "rhavern (14) - Points"
        --vertical-label "Points"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Points=eoc-data/rhavern-14.rrd:Points:AVERAGE
        LINE1:Points#0000FF:Points
        GPRINT:Points:AVERAGE:Avg\: %.2lf %s
        GPRINT:Points:MIN:Min\: %.2lf %s
        GPRINT:Points:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x254
Averages: 
rrdgraph eoc-data/rhavern-14-Points-1year.png
        --start -8784hours
        --end 1240294609
        --title "rhavern (14) - Points"
        --vertical-label "Points"
        --width 550
        --height 175
        --imgformat PNG
        DEF:Points=eoc-data/rhavern-14.rrd:Points:AVERAGE
        LINE1:Points#0000FF:Points
        GPRINT:Points:AVERAGE:Avg\: %.2lf %s
        GPRINT:Points:MIN:Min\: %.2lf %s
        GPRINT:Points:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x254
Averages: 
rrdgraph eoc-data/rhavern-14-WUs-1day.png
        --start -24hours
        --end 1240294609
        --title "rhavern (14) - WUs"
        --vertical-label "WUs"
        --width 550
        --height 175
        --imgformat PNG
        DEF:WUs=eoc-data/rhavern-14.rrd:WUs:AVERAGE
        LINE1:WUs#0000FF:WUs
        GPRINT:WUs:AVERAGE:Avg\: %.2lf %s
        GPRINT:WUs:MIN:Min\: %.2lf %s
        GPRINT:WUs:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x254
Averages: 
rrdgraph eoc-data/rhavern-14-WUs-1week.png
        --start -168hours
        --end 1240294609
        --title "rhavern (14) - WUs"
        --vertical-label "WUs"
        --width 550
        --height 175
        --imgformat PNG
        DEF:WUs=eoc-data/rhavern-14.rrd:WUs:AVERAGE
        LINE1:WUs#0000FF:WUs
        GPRINT:WUs:AVERAGE:Avg\: %.2lf %s
        GPRINT:WUs:MIN:Min\: %.2lf %s
        GPRINT:WUs:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x254
Averages: 
rrdgraph eoc-data/rhavern-14-WUs-1month.png
        --start -744hours
        --end 1240294609
        --title "rhavern (14) - WUs"
        --vertical-label "WUs"
        --width 550
        --height 175
        --imgformat PNG
        DEF:WUs=eoc-data/rhavern-14.rrd:WUs:AVERAGE
        LINE1:WUs#0000FF:WUs
        GPRINT:WUs:AVERAGE:Avg\: %.2lf %s
        GPRINT:WUs:MIN:Min\: %.2lf %s
        GPRINT:WUs:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x254
Averages: 
rrdgraph eoc-data/rhavern-14-WUs-1year.png
        --start -8784hours
        --end 1240294609
        --title "rhavern (14) - WUs"
        --vertical-label "WUs"
        --width 550
        --height 175
        --imgformat PNG
        DEF:WUs=eoc-data/rhavern-14.rrd:WUs:AVERAGE
        LINE1:WUs#0000FF:WUs
        GPRINT:WUs:AVERAGE:Avg\: %.2lf %s
        GPRINT:WUs:MIN:Min\: %.2lf %s
        GPRINT:WUs:MAX:Max\: %.2lf %s
        COMMENT:Last Update\: 2009-04-21 07\:16\:49
Image Size: 647x254
Averages: 

Saving eoc-stats XML file ...
Successfully saved eoc-stats XML file

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

Posted: Tue Apr 21, 2009 8:25 am
by smoking2000
The numbers in the rrdupdate seem to be correct as expected, 24hr Avg: 9263 reported in the User Information section, and also updated in the RRD. The 9263 value also corresponds to the 9.26 k reported for the Avg, Min & Max values of your EOC RRD graphs.

We just had another EOC update, did it use the new value 9006 for your 24hr avg?
All times are UTC
Page 8 of 23

Powered by phpBB® Forum Software © phpBB Limited