headers
Westlake, Simon | 2 Jan 2007 20:10

Font size increased

This is probably something very obvious, but I've searched the mailing
list archive and poked around in the config file and not seen anything
so here I am.

I setup Smokeping on an Ubuntu server today, which has a version in it's
package manager slightly older than the release version (2.0.8-3)

For some reason, the font on the graphs is too big and causes the text
to run over itself - you can see an example here:

http://vip.twcwi.com/graphs/116776478319374_-0h_-24h.png

I've never experienced this problem before and I've dug around in man
pages trying to figure out what's causing it to no avail. Can anyone
shed some light on this?

--
Simon Westlake
Time Warner Cable Business Class
Network Engineer
Ph: 414.908.4791 | Cell: 414.688.7956

-----------------------------------------
This E-mail and any of its attachments may contain Time Warner
Cable proprietary information, which is privileged, confidential,
or subject to copyright belonging to Time Warner Cable. This E-mail
is intended solely for the use of the individual or entity to which
it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination,
distribution, copying, or action taken in relation to the contents
(Continue reading)

Permalink | Reply | 3 comments |
headers
Tobias Oetiker | 2 Jan 2007 23:58
Picon
Gravatar

Re: Font size increased

Hi Simon,

Today Westlake, Simon wrote:

> For some reason, the font on the graphs is too big and causes the text
> to run over itself - you can see an example here:
>
> http://vip.twcwi.com/graphs/116776478319374_-0h_-24h.png

you graphs seem awfully 'non-wide' I think this is what causes the
problem. the graph size is configurable! also there were some
updates to the text layout in recent updates which may have a
positive effect on this problem ...

cheers
tobi

--

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten
http://it.oetiker.ch tobi <at> oetiker.ch ++41 62 213 9902
Permalink | Reply | 0 comments |
headers
mchandler | 3 Jan 2007 23:46
Picon

EchoPingHttps


I was trying to setup a probe for an https web server and I get the error
that echoping does not support ssl.  When I run echoping by itself, it says
it was compiled without ssl support.  Is there an RPM out there that was
compiled with ssl support?

If I have to compile it myself, does it make sense to go ahead and install
6.0 or will that work with smokeping?  I saw an email in the archive about
it, but I don't know if it needed a patch for smokeping.  Thanks in
advance.

Chandler Bing
Permalink | Reply | 1 comment |
headers
Westlake, Simon | 4 Jan 2007 15:17

Re: Font size increased

Thanks for the quick reply, Tobi. I had decreased the graph size in the
past to keep it equal to the width of my other RRD graphs (I display a
lot of them on the same page.) On the previous box I had it installed on
(Gentoo) the font was a lot smaller and didn't overrun, but this may be
attributed to different Smokeping versions. I increased the width for
now to fix it.

I'm hoping they will update the version of Smokeping in the Ubuntu
repositories soon so I can upgrade. I'm trying to use the version in the
package manager just to keep administration easier across multiple
servers.

How does Smokeping decide what font to use and what size the font will
be? Is this something that is hardcoded (and if so, I guess it must be
that I was running a different version before.) Or is it some
environment variable I could change? 

--
Simon Westlake
Time Warner Cable Business Class
Network Engineer
Ph: 414.908.4791 | Cell: 414.688.7956

-----Original Message-----
From: Tobias Oetiker [mailto:tobi <at> oetiker.ch] 
Sent: Tuesday, January 02, 2007 4:58 PM
To: Westlake, Simon
Cc: smokeping-users <at> list.ee.ethz.ch
Subject: Re: [smokeping-users] Font size increased
(Continue reading)

Permalink | Reply | 501 comments |
headers
Tobias Oetiker | 4 Jan 2007 19:27
Picon
Gravatar

Re: Font size increased

Hi Simon,

it may be that the space problem is due to the NEWER version of
rrdtool ... you may get away with hacking smokeping to use a
smaller font size with the new rrdtool ...

cheers
tobi

--

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten
http://it.oetiker.ch tobi <at> oetiker.ch ++41 62 213 9902
Permalink | Reply | 501 comments |
headers
Luc Moreault | 4 Jan 2007 22:15

Owamp Probe creation question

Hello,

I am still trying to put up an Owping probe that could work with smokeping.  I took exemple from the
EchoPing.pm module.
Now my question is this :

Where are the smokeping config probe options taken in consideration ?

Is it in the probe module or at any higher level ?

Thank you very much.

Luc
Permalink | Reply | 1 comment |
headers
Niko Tyni | 5 Jan 2007 08:33
Picon
Picon

Re: Owamp Probe creation question

On Thu, Jan 04, 2007 at 04:15:24PM -0500, Luc Moreault wrote:

> I am still trying to put up an Owping probe that could work with smokeping.  I took exemple from the
EchoPing.pm module.
> Now my question is this :
> 
> Where are the smokeping config probe options taken in consideration ?
> 
> Is it in the probe module or at any higher level ?

Hi,

have a look at the smokeping_extend document, this is all explained there.
The EchoPing.pm module may be a bit confusing as an example, since there's
quite a lot of inheritance between the related classes going on.

Cheers,
--

-- 
Niko
Permalink | Reply | 0 comments |
headers
Niko Tyni | 5 Jan 2007 08:38
Picon
Picon

Re: EchoPingHttps

On Wed, Jan 03, 2007 at 02:46:38PM -0800, mchandler <at> solutions.canon.com wrote:

> I was trying to setup a probe for an https web server and I get the error
> that echoping does not support ssl.  When I run echoping by itself, it says
> it was compiled without ssl support.  Is there an RPM out there that was
> compiled with ssl support?
> 
> If I have to compile it myself, does it make sense to go ahead and install
> 6.0 or will that work with smokeping?  I saw an email in the archive about
> it, but I don't know if it needed a patch for smokeping.  Thanks in
> advance.

Hi,

I don't know about the RPM part, but you indeed need a small patch to use
echoping 6 and SSL with Smokeping. 

You can find the patch in 

 http://lists.ee.ethz.ch/smokeping-users/msg02058.html

Cheers,
--

-- 
Niko
Permalink | Reply | 0 comments |
headers
Luc Moreault | 5 Jan 2007 20:36

Re: Owamp Probe creation question

First of all, thanks for the hint Niko, I worked around the skel.pm module and i'm almost done with it.
I only need to parse my output in the array. I understand the skel.pm code almost in all its integrity but one
line (which gives me a compile time error).

open(P, $cmd 2>&1 |") or croak("fork:$!); #What is the $cmd variable ?

The compile time error is :

require Smokeping::probes::Owping failed: Global symbol "$cmd" requires explicit package name at
/usr/local/smokeping/lib/Smokeping/probes/Owping.pm line 118.
Compilation failed in require ar (eval 13) line 3.

Thank you,

Luc

-----Message d'origine-----
De : smokeping-users-bounce <at> list.ee.ethz.ch
[mailto:smokeping-users-bounce <at> list.ee.ethz.ch]De la part de Niko Tyni
Envoyé : 5 janvier 2007 02:34
À : smokeping-users <at> list.ee.ethz.ch
Objet : [smokeping-users] Re: Owamp Probe creation question

On Thu, Jan 04, 2007 at 04:15:24PM -0500, Luc Moreault wrote:

> I am still trying to put up an Owping probe that could work with smokeping.  I took exemple from the
EchoPing.pm module.
> Now my question is this :
> 
> Where are the smokeping config probe options taken in consideration ?
(Continue reading)

Permalink | Reply | 1 comment |
headers
Niko Tyni | 5 Jan 2007 20:48
Picon
Picon

Re: Owamp Probe creation question

On Fri, Jan 05, 2007 at 02:36:04PM -0500, Luc Moreault wrote:
> First of all, thanks for the hint Niko, I worked around the skel.pm module and i'm almost done with it.
> I only need to parse my output in the array. I understand the skel.pm code almost in all its integrity but one
line (which gives me a compile time error).
> 
> open(P, $cmd 2>&1 |") or croak("fork:$!); #What is the $cmd variable ?

That's the actual command line that's going to be executed, supposedly
glued together from the probe and target variables. Something like
(as a made-up example)

 my $cmd = "$binary -w $weight -c $count $target->{addr}";

The skel.pm module is indeed missing this; I'll add it for the next release.

Hope this helps,
--

-- 
Niko
Permalink | Reply | 0 comments |

Gmane