Ai, I somehow managed to incorrectly configure the path to the
rrdtool.

I figured that out after I replaced
$retval = $Shell->QueryRaw("{$this->RRDToolPath} graph
'{$filename}' {$query_string} 2>&1");
with
die("{$this->RRDToolPath} graph '{$filename}' {$query_string} 2>&1");
in the src/LibWebta/library/Data/RRD/class.RRDGraph.php file, viewed  /
server/statistics.php?
task=get_stats_image_url&farmid=1&watchername=MEMSNMP&graph_type=daily&role_name=_FARM
and then run that command in the terminal.

Tom, thanks for mentioning those 2 vardump lines. I've removed them
from the statistics.php and now it's output is:
{"type":"ok","msg":"http:\/\/ec2-xx-xx-xx-xxx.compute-1.amazonaws.com\/
stats\/1\/_FARM_MEMSNMP.daily.gif"}
The labels now stay at "Loading graphic. Please wait...", although if
I replace the \/ with / and open that URL the image loads just fine.

Thanks so much for all the assistance so far - greatly appreciated.

On Oct 16, 3:54 am, Pada <[email protected]> wrote:
> Thanks Tom
>
> I've now gone and installed my Scalr frontend on a Fedora Core 8
> system to check if it wasn't something related to my Ubuntu
> configuration. Instead of compiling rrdtool this time, I've simply
> installed it using yum.
>
> I've now checked within the statistics.php file, and it seems like it
> contains a few bugs/lines that should be there.
> Like the following 3 lines should be removed:
> $image_path = dirname(__FILE__)."/../temp/test.gif"
> $rrddbpath = dirname(__FILE__)."/../../temp/db.rrd";
> CONFIG::$RRD_GRAPH_STORAGE_TYPE = RRD_STORAGE_TYPE::LOCAL_FS;
>
> I've now configured my Scalr to save the images locally. The functions
> are creating the directories correctly (using the %FARM-ID% as a
> subdirectory), but its still not creating any graph files.
>
> I ran the following in the console and it did create a graph:
> /usr/bin/rrdtool graph - --imgformat=PNG --start=-86400 --end=-60 --
> title="Call Manager Publisher - Uptime" --base=1000 --height=120 --
> width=600 --alt-autoscale-max --lower-limit=0 --vertical-label="Hours"
> --slope-mode --font TITLE:12: --font AXIS:8: --font LEGEND:10: --font
> UNIT:8: DEF:a="/home/rrddata/1/_FARM/CPUSNMP/db.rrd":user:AVERAGE
> CDEF:cdefa=a,100,/,60,/,60,/ AREA:cdefa#00CF00FF:"Uptime Hours\:"
> GPRINT:cdefa:LAST:"%8.0lf\n" > graph.png
>
> I have no idea where to look for the error, because my Apache logs and
> Scalr event logs doesn't show any error close to the rrdtool not
> generating the graphs. The only errors appearing in my Apache log file
> are:
> PHP Warning:  Call-time pass-by-reference has been deprecated in /var/
> www/scalr/app/src/class.Scalr.php on line 153
> PHP Warning:  Call-time pass-by-reference has been deprecated in /var/
> www/scalr/app/src/queue_tasks/class.MigrateRoleTask.php on line 145
>
> Help would be appreciated very much. Even if you can point me to
> certain log files / code that I should check.
>
> Regards
> Chris
>
> On Oct 14, 2:54 pm, Tom <[email protected]> wrote:
>
> > Once the graphs are being produced, you'll still have to modify app/
> > www/server/statistics.php. It is supposed to output a json string only
> > containing the address of the graph image.
>
> > The "float(21474836480) int(1073743159)" you see is because of two
> > var_dump() calls on lines 9 and 15. Once you remove these lines, it
> > will output the json without the extra stuff and your graphs should
> > show up on the page.
>
> > On Oct 13, 2:37 pm, somer <[email protected]> wrote:
>
> > > Hi,
>
> > > perl -pi -e 's/RetrieveData/RetreiveData/g' cron/watchers/
> > > class.SNMPWatcher.php
>
> > > and then check that class.SNMPWatcher.php to have the correct value
> > > Retrieve must be corrected now.
>
> > > run it via php
>
> > > /usr/bin/php -q cron/cron.php --SNMPStatsPoller
>
> > > now you can use rrdgraph, check your s3 bucket to see if the gifs are
> > > there.
>
> > > I`m having the same issue still, invalid label but the graphs are
> > > produced in s3 bucket.
>
> > > Regards
>
> > > On 13 Ekim, 02:46, Pada <[email protected]> wrote:
>
> > > > Hi,
>
> > > > I'm struggling very much to get the Load Statistics working with Scalr
> > > > 1.1.0 on an Ubuntu 9.04 AMI. I've done everything according 
> > > > tohttp://wiki.scalr.net/Installation/Configuring_Load_Statisticshowever
> > > > I have no idea on how to verify that I've configured it correctly. My
> > > > phpinfo() page can be found 
> > > > here:http://ec2-75-101-202-153.compute-1.amazonaws.com/phpinfo.php
>
> > > > Secondly: I'm unsure on how to configure the "RRD statistics
> > > > settings".
> > > > My current configuration looks like follow:
>
> > > > > Path to rrdtool binary: /usr/local/rrdtool-1.3.8/bin/rrdtool
> > > > > Path to font: /usr/share/rrdtool/fonts/DejaVuSansMono-Roman.ttf
> > > > > Path to RRD database dir: /home/rrddata
> > > > > Statistics 
> > > > > URL:https://s3.amazonaws.com/pada-scalr-stats/%fid%/%rn%_%wn%.
> > > > > Store graphics in: Amazon S3
> > > > > Path to graphics: pada-scalr-stats
>
> > > > I have ensured that the rrdtool, the DejaVuSansMono-Roman.ttf font &
> > > > the rrdata folder exists at the paths that I have specified. I have
> > > > also added "public-read" to the class.RRDGraphProcess.php file.
>
> > > > Currently when I go to Load Statistics, I just get "Invalid label"
> > > > instead of images. When I try to load the actual image which AJAX just
> > > > interprets, I just get "float(21474836480) int(1073743159)
> > > > {"type":"error","msg":"Statistics not available yet"}"
> > > > I've checked the /home/rrddata folder, and it contains a folder with
> > > > the same name as my Farm ID, but its completely empty still.
>
> > > > Assistance would be greatly appreciated once again.
>
> > > > Regards
> > > > Chris

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"scalr-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/scalr-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to