[smokeping-users] smoketrace for dummies help please

[David Tomic]

Well ... I've just had one last crack at it, and despite my most valiant 
efforts I'm still not having any luck.

Loading the tr.html page directly in the browser just gives me a 
completely blank screen. [The source code is still there, but it's just 
not doing anything.]

I don't see an error message anywhere, either in my browser, or the 
apache logs, so the page doesn't appear to be doing anything at all.

Does that point to any really obvious errors/mistakes that I might have 
made?




Tobias Oetiker wrote:
> Hi Jsg,
>
> I expected that there were going to be some questions ...
> veryfingint the js I included with version 2.4.0 I  found that my
> release script actualy was doing bad damage to it ... I am working
> on 2.4.1 now, and will also address some of your points below in
> the install instructions in the process ... thanks for spending the
> time testing the beast ...
>
> Today jsg at internode.on.net wrote:
>
>   
>> Hi guys,
>>
>> I've managed the upgrade to smokeping 2.4.0 without any major dramas,
>> but I simply can NOT for the life of me get the smoketrace part of it up
>> and running.
>>
>> I'm very much a novice when it comes to all this scripting stuff, so I
>> think I might be in need of some pretty basic help.
>>
>> Can anybody please spare me the time/patience to walk me through EXACTLY
>> what needs to be done, step by step?
>>
>> Obviously I've tried reading the documentation ... but I'm still really
>> struggling with it.
>>
>> Here's what's laid out in the documentation.
>>
>> 1. Copy htdocs/script/Tr.js to your smokeping web directory.
>>
>> I'm not sure which path this is actually referring to?
>> All my images etc are stored in /var/www/smokeping but my smokeping.cgi
>> file is in /usr/lib/cgi-bin.  The latter is also where you're sent when
>> you actually load smokeping in the browser.  IE
>> myurl.com/cgi-bin/smokeping.cgi.
>>     
>
> Tr.js must be stored somewhere that the browser can read it ...
>   
>> 2. Copy and edit htdocs/tr.html to your smokeping web directory. Make
>> sure the path to Tr.js is correct.
>>     
>
> tr.html must be stored in the same location as tr.cgi, and this can
> not be cgi-bin since that location will prevent tr.html from being
> sent to the browser ..
>
>   
>> 3. Copy htdocs/resource into the directory where you put tr.html.
>>
>> Those should both be simple enough, once I know which directory it's
>> actually talking about! :p
>>     
>
> the directory is irrelevant as long as the browser can read it, and
> tr.cgi gets executed ...
>   
>> 4. Copy and edit htdocs/tr.cgi.dist to the directory where you put
>> tr.html and change its name to tr.cgi. Make sure tr.cgi to adjust the
>> use lib line to point to the smokeping per lib directory, as you did
>> with smokeping.cgi. Make sure the webserver actually executes the tr.cgi
>> script.
>>
>> Is that supposed to be "perl" lib directory?
>>     
>
>   
>> smokeping.cgi lists "use lib qw(/usr/share/perl5/smokeping);"  ... is
>> that what I should be using?
>>     
>
> yep
>
>
>   
>> I'm also confused by the qooxdoo folder included in the smokeping
>> package.  I don't see it mentioned in any of the documentation anywhere,
>> so I'm not sure if I'm supposed to be doing anything with it?
>>     
>
> this is the source of the qooxdoo application, for people who like
> to hack on it ...
>
> cheers
> tobi
>
>
>   
>> ANY help would be really greatly appreciated!
>>
>>
>> _______________________________________________
>> smokeping-users mailing list
>> smokeping-users at lists.oetiker.ch
>> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>>
>>
>>     
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20080613/4dcc51c1/attachment-0001.html 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Attached Message Part
Url: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20080613/4dcc51c1/attachment-0001.ksh