Nabble - RRDTool

Re: Requesting help with glib install

2009-11-07T09:23:13Z

>>> Marc Powell <marc@...> 11/7/2009 9:44 AM >>>

> It looks like it's unable to create the directory '/usr/local/share'.
> Are you doing this as a user who has permissions to do so?

> Do you have other restrictions such that you couldn't do that

> (SELinux maybe?)
>

I thought that too. I'm performing the installation as root,

and SELinux is disabled.

The directory already exists, but that shouldn't be a big

deal because the /usr/local/share directory is pretty

common.

Paul

************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee.  If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission.  If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy.  This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act.  You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission.  The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: Requesting help with glib install

2009-11-07T06:44:03Z

On Nov 7, 2009, at 8:23 AM, PAUL WILLIAMSON wrote:

> Trying to install smokepipng, but obviously I need rrdtool
> first. It's been a while since I did an install, and I'm
> running into problems with installing glib. This is the error:
>
> Making install in po
> make[1]: Entering directory `/downloads/glib-2.0.7/po'
> if test -r ".././mkinstalldirs"; then \
> .././mkinstalldirs /usr/local/share; \
> [snip]
> /bin/sh: .././mkinstalldirs: Permission denied

It looks like it's unable to create the directory '/usr/local/share'.
Are you doing this as a user who has permissions to do so? Do you have
other restrictions such that you couldn't do that (SELinux maybe?)

--
Marc

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Requesting help with glib install

2009-11-07T06:23:18Z

Trying to install smokepipng, but obviously I need rrdtool

first. It's been a while since I did an install, and I'm

running into problems with installing glib. This is the error:

Making install in po
make[1]: Entering directory `/downloads/glib-2.0.7/po'
if test -r ".././mkinstalldirs"; then \
.././mkinstalldirs /usr/local/share; \
else \
/bin/sh ../mkinstalldirs /usr/local/share; \
fi
/bin/sh: .././mkinstalldirs: Permission denied
make[1]: *** [install-data-yes] Error 126
make[1]: Leaving directory `/downloads/glib-2.0.7/po'
make: *** [install-recursive] Error 1

I've been pulling my hair out for the last few days. I'm

hoping someone can help me out.

Running RedHat ES4.

Thanks,

Paul

************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee.  If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission.  If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy.  This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act.  You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission.  The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: patch to do vertical gradients

2009-11-06T06:49:28Z

On Fri, Nov 6, 2009 at 7:20 AM, Mark Mills <extremely@...> wrote:
> If it was used to carry information, one that might help would be scale
> differences. I have had issues in the past where my boss at the time
> freaked out when a graph spiked and we had to point out that the one he
> was looking at had spiked from bits to kbits... not from mbits to gbits.
> ;-) A way to color the scale in the area (logarithmically?) would help
> when scanning graphs quickly. It wouldn't give the same cool fire effect
> but "ripples" in the area paint could effectively replace the need for
> grid lines.

Thats one of the reasons I wrote it. A negative height would be
aligned to the x axis, so that increasing values on the line change to
the next color, ie a gradient from green to red. Of course, to be
really useful, I would need to change it so that the height was
relative to the data set, and not given in pixels. I'll have to see
how to do that. gfx_area_fit maybe?

> I'd also recommend that the default second color be set to the graph
> background color with the transparency set to 0x20 and not be forced to
> #000000. Might as well make it do something cool by default no matter
> what color scheme they use.

Maybe. I figured it didn't matter much what the color was if the alpha
was zero. That way it always appeared to fade into whatever is behind
it, be it the background or another AREA. I'll have to play with it
and see what it looks like.

> Also, I'm jealous of Rian because I've been wanting to write this patch
> for like 5-6 years and never had the time. ;-) It looks even better than
> I hoped. I'm looking forward to this being in the main build.

All the heavy lifting is done by cairo :D. All I did was allow the
source pattern to be a gradient as well as a solid color. I think the
other option is to make the source pattern another image.

--
rian

_______________________________________________
rrd-developers mailing list
rrd-developers@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers

From forum: RRDTool - Dev

Re: patch to do vertical gradients

2009-11-06T06:20:54Z

Tobias Oetiker wrote:
>>> thanks for this ... it looks cool ... quersion though, is there
>>> some information carying capability in this feature ?
>>>
If it was used to carry information, one that might help would be scale
differences. I have had issues in the past where my boss at the time
freaked out when a graph spiked and we had to point out that the one he
was looking at had spiked from bits to kbits... not from mbits to gbits.
;-) A way to color the scale in the area (logarithmically?) would help
when scanning graphs quickly. It wouldn't give the same cool fire effect
but "ripples" in the area paint could effectively replace the need for
grid lines.

I'd also recommend that the default second color be set to the graph
background color with the transparency set to 0x20 and not be forced to
#000000. Might as well make it do something cool by default no matter
what color scheme they use.

Also, I'm jealous of Rian because I've been wanting to write this patch
for like 5-6 years and never had the time. ;-) It looks even better than
I hoped. I'm looking forward to this being in the main build.

--mark

_______________________________________________
rrd-developers mailing list
rrd-developers@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers

From forum: RRDTool - Dev

Re: rrdtool 1.4.x without graphing support?

2009-11-06T00:42:23Z

Hi Tobi,

On Thu, Nov 05, 2009 at 11:56:10PM +0100, Tobias Oetiker wrote:

> Today Sebastian Harl wrote:
> > On Thu, Nov 05, 2009 at 05:53:20AM +0100, Tobias Oetiker wrote:
> > > Yesterday Ulf Zimmermann wrote:
> > > > Anyone got an idea how much work would be involved to build/patch
> > > > rrdtool 1.4.x to remove graphing support? Library dependency for
> > > > EL4 is just hell at this point. And as I need librrd, I am not
> > > > sure how far I can work with a static build to work with collectd
> > > > together.
> > >
> > > you may want to try the appended patch.
> >
> > > +if BUILD_RRDGRAPH
> > > +RRD_C_FILES += rrd_graph.c \
> > > + rrd_graph_helper.c \
> > > + rrd_xport.c \
> > > + rrd_gfx.c \
> > > + pngsize.c
> > > +endif
> > [?]
> >
> > NB: RRD_C_FILES is later used to specify the source files for librrd.
> >
> > In case this patch is supposed to be included in RRDtool, please note
> > that it provides an easy way to build RRDtool with a different API /
> > ABI. Hence, it requires a different SONAME version (or even better: a
> > different SONAME -- which would be easier to implement as well).
>
> this patch is not the library split or anything like this ... it
> is simply an attempt to help ulf ...

That's what I though -- I just wanted to make sure we don't miss this
issue ;-)

> note that there are already similar configure options for libdbi
> which enable/disable functionality without changeing the library
> version ...

Darn, I did not notice that so far :-/

This is not a good thing either (imho). One could argue that taking care
of appropriate SONAME version changes is the responsibility of distrib-
utors. However, this will create problems for users if done differently
on different distributions.

> after doing this initial version, and thinking about it I think
> adding stub versions of the public graph functions which set
> rrd_error when called would be a nicer variant ... leaving the
> library interface in place ...

This would keep the API unchanged but it *does* change the ABI (the
semantic of some functions would change -- dramatically even), thus
still requiring a SONAME version change.

> > Anyway, rather than including this (imho) somewhat hackish way, I'd
> > rather go for splitting the library as discussed before (librrd /
> > librrdgraph). I'm willing to provide a patch for that targeted at
> > RRDtool 1.5 (it will probably require a SONAME version bump, thus, it
> > should imho not be included in 1.4 -- I'd also provide patches for
> > reverse dependencies known to be affected by that).
>
> yes, a split of the library for 1.5 would be cool ... I would
> propose the following split:
>
> librrdclient - access to rrdcached functions - no deps

Sure, why not …

> librrdcore - core rrdtool functions (create/update) - no deps

You've been talking about an API-redesign scheduled for 1.5 -- any
specific plans for that yet?

Also, as of now, this lib would depend on libdbi. If we want to split
that out as well, librrdcore would still depend on that unless
rrd_fetch() would be split into two functions. Another approach would be
to introduce "backend-drivers" (i.e., one handling files, one handling
SQL databases thru dbi, etc.). Those drivers could then be loaded
dynamically by rrd_fetch(). IIrc, somebody has proposed a "virtual file-
system layer" some time ago -- what happened to that?

> librrdcached - rrdcached - glib

What's that supposed to include and what purpose is it going to serve?
Do you want to make rrd_daemon.c:main available thru the/a library? I
don't see any benefits from that.

> librrdgraph - graphing - cairo pango

That's the most important one ;-)

> librrd - compat layer - librrdclient librrdcore librrdcached librrdgraph

I'm still unsure about details like "does that change the ABI?", etc.
(see a previous E-mail in a different discussion on that topic) but, I
guess, it might make live a bit easier for users who compile stuff them-
selves (rather than having their distributor take care of that), so
(*shrug*) why not … ;-)

> configure could then automatically disable the bits of rrdtool
> which can not be built due to libraries missing

NB: "bits" as in "single libraries", rather than features of one library

Cheers,
Sebastian

--
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

signature.asc (204 bytes) Download Attachment

From forum: RRDTool - User

Re: rrdtool 1.4.x without graphing support?

2009-11-05T14:56:10Z

Hi Sebastian,

Today Sebastian Harl wrote:

> Hi,
>
> On Thu, Nov 05, 2009 at 05:53:20AM +0100, Tobias Oetiker wrote:
> > Yesterday Ulf Zimmermann wrote:
> > > Anyone got an idea how much work would be involved to build/patch
> > > rrdtool 1.4.x to remove graphing support? Library dependency for
> > > EL4 is just hell at this point. And as I need librrd, I am not
> > > sure how far I can work with a static build to work with collectd
> > > together.
> >
> > you may want to try the appended patch.
>
> > +if BUILD_RRDGRAPH
> > +RRD_C_FILES += rrd_graph.c \
> > + rrd_graph_helper.c \
> > + rrd_xport.c \
> > + rrd_gfx.c \
> > + pngsize.c
> > +endif
> [?]
>
> NB: RRD_C_FILES is later used to specify the source files for librrd.
>
> In case this patch is supposed to be included in RRDtool, please note
> that it provides an easy way to build RRDtool with a different API /
> ABI. Hence, it requires a different SONAME version (or even better: a
> different SONAME -- which would be easier to implement as well).

this patch is not the library split or anything like this ... it
is simply an attempt to help ulf ...

note that there are already similar configure options for libdbi
which enable/disable functionality without changeing the library
version ...

after doing this initial version, and thinking about it I think
adding stub versions of the public graph functions which set
rrd_error when called would be a nicer variant ... leaving the
library interface in place ...

> Anyway, rather than including this (imho) somewhat hackish way, I'd
> rather go for splitting the library as discussed before (librrd /
> librrdgraph). I'm willing to provide a patch for that targeted at
> RRDtool 1.5 (it will probably require a SONAME version bump, thus, it
> should imho not be included in 1.4 -- I'd also provide patches for
> reverse dependencies known to be affected by that).

yes, a split of the library for 1.5 would be cool ... I would
propose the following split:

librrdclient - access to rrdcached functions - no deps
librrdcore - core rrdtool functions (create/update) - no deps
librrdcached - rrdcached - glib
librrdgraph - graphing - cairo pango

librrd - compat layer - librrdclient librrdcore librrdcached librrdgraph

configure could then automatically disable the bits of rrdtool
which can not be built due to libraries missing

cheers
tobi

--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi@... ++41 62 775 9902 / sb: -9900

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: rrdtool 1.4.x without graphing support?

2009-11-05T14:44:28Z

Hi Ulf,

Today Ulf Zimmermann wrote:

> > -----Original Message-----
> > From: Tobias Oetiker [mailto:tobi@...]
> > Sent: Wednesday, November 04, 2009 8:53 PM
> > To: Ulf Zimmermann
> > Cc: rrd-users@...
> > Subject: Re: [rrd-users] rrdtool 1.4.x without graphing support?
> >
> > Hi Ulf,
> >
> > Yesterday Ulf Zimmermann wrote:
> >
> > > Anyone got an idea how much work would be involved to build/patch
> > > rrdtool 1.4.x to remove graphing support? Library dependency for
> > > EL4 is just hell at this point. And as I need librrd, I am not
> > > sure how far I can work with a static build to work with collectd
> > > together.
> >
> > you may want to try the appended patch.
> >
> > cheers
> > tobi
>
> Trying to look at the patch, I got another question. Configure.ac
> is set to check for glib-2.0, by using glib_check_version, which
> wasn't added until glib 2.6. EL4 unfortunatly only has glib
> 2.4.7. Trying to determine what functions from glib 2.x are used.
> Also the glib check is inside of the block of cairo and pango, is
> glib used for graphing too?

glib is a dependency of pango, it is not used directly by the
graphing code ...

the cached uses it though ...

cheers
tobi
>
> Ulf.
>
>

--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi@... ++41 62 775 9902 / sb: -9900

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: rrdtool 1.4.x without graphing support?

2009-11-05T12:43:31Z

> -----Original Message-----
> From: Tobias Oetiker [mailto:tobi@...]
> Sent: Wednesday, November 04, 2009 8:53 PM
> To: Ulf Zimmermann
> Cc: rrd-users@...
> Subject: Re: [rrd-users] rrdtool 1.4.x without graphing support?
>
> Hi Ulf,
>
> Yesterday Ulf Zimmermann wrote:
>
> > Anyone got an idea how much work would be involved to build/patch
> > rrdtool 1.4.x to remove graphing support? Library dependency for
> > EL4 is just hell at this point. And as I need librrd, I am not
> > sure how far I can work with a static build to work with collectd
> > together.
>
> you may want to try the appended patch.
>
> cheers
> tobi

Trying to look at the patch, I got another question. Configure.ac is set to check for glib-2.0, by using glib_check_version, which wasn't added until glib 2.6. EL4 unfortunatly only has glib 2.4.7. Trying to determine what functions from glib 2.x are used. Also the glib check is inside of the block of cairo and pango, is glib used for graphing too?

Ulf.

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: patch to do vertical gradients

2009-11-05T12:10:35Z

Hi Rian,

Today Rian Shelley wrote:

> This time i remembered to attach the patch :D
>
>
> > thanks for this ... it looks cool ... quersion though, is there
> > some information carying capability in this feature ?
>
> Not really. For the most part, I wanted to add some control over how
> the AREA's were drawn, especially when you have two of them on the
> same graph that keep covering one another, it makes it easier for the
> eye to pick out the two graphs, as opposed to simply using an alpha,
> which gives a solid color that can be mis-interpreted as another
> graph.
>
> I also wanted the ability to make it so that peak values could be
> highlighted in a different color if desired, as in a cpu graph going
> from green through yellow to red.
>
> I haven't thought about making it carry information, although it might
> be neat to show temporal distribution of an average value (ie, turn
> the dataset on its side, and make it represent color instead of
> displacement). I don't really know how to get into that, since all
> I've played with so far is the drawing code.
>
> >
> > can you please also add a patch for the documentation ?
>
> Hopefully the attached patch will suffice.

great ... thanks very much
tobi

>
>
> --
> rian
>

--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi@... ++41 62 775 9902 / sb: -9900

_______________________________________________
rrd-developers mailing list
rrd-developers@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers

From forum: RRDTool - Dev

Re: patch to do vertical gradients

2009-11-05T11:33:34Z

This time i remembered to attach the patch :D

> thanks for this ... it looks cool ... quersion though, is there
> some information carying capability in this feature ?

Not really. For the most part, I wanted to add some control over how
the AREA's were drawn, especially when you have two of them on the
same graph that keep covering one another, it makes it easier for the
eye to pick out the two graphs, as opposed to simply using an alpha,
which gives a solid color that can be mis-interpreted as another
graph.

I also wanted the ability to make it so that peak values could be
highlighted in a different color if desired, as in a cpu graph going
from green through yellow to red.

I haven't thought about making it carry information, although it might
be neat to show temporal distribution of an average value (ie, turn
the dataset on its side, and make it represent color instead of
displacement). I don't really know how to get into that, since all
I've played with so far is the drawing code.

>
> can you please also add a patch for the documentation ?

Hopefully the attached patch will suffice.

--
rian

[grad_doc.patch]

diff -crB rrdtool-1.3.8/doc/rrdgraph_graph.pod ../rrdtool-1.3.8/doc/rrdgraph_graph.pod *** rrdtool-1.3.8/doc/rrdgraph_graph.pod Sat Feb 21 02:43:58 2009 --- ../rrdtool-1.3.8/doc/rrdgraph_graph.pod Thu Nov 5 12:23:08 2009 *************** *** 262,267 **** --- 262,275 ---- See B<LINE>, however the area between the x-axis and the line will be filled. + =head3 B<GRAD>B<:>I<value>[B<#>I<color1>[B<#>I<color2>B<:>I<height>][B<:>[I<legend>][B<:STACK>]] + + Similar to B<AREA>, except the area between the line and the x-axis will contain a gradient from color1 to color2. + + The I<height> parameter can create three different behaviors. If I<height> > 0, then the gradient is a fixed height, starting at the line going down. If I<height> < 0, then the gradient starts at fixed height above the x-axis, going down to the x-axis. If I<height> == 0, then the gradient goes from the line to x-axis. + + If not present, I<color2> defaults to #00000000 and I<height> defaults to 50. + =head3 B<TICK>B<:>I<vname>B<#>I<rrggbb>[I<aa>][B<:>I<fraction>[B<:>I<legend>]] Plot a tick mark (a vertical line) for each value of I<vname> that is

_______________________________________________
rrd-developers mailing list
rrd-developers@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers

From forum: RRDTool - Dev

Re: patch to do vertical gradients

2009-11-05T11:32:20Z

> thanks for this ... it looks cool ... quersion though, is there
> some information carying capability in this feature ?

Not really. For the most part, I wanted to add some control over how
the AREA's were drawn, especially when you have two of them on the
same graph that keep covering one another, it makes it easier for the
eye to pick out the two graphs, as opposed to simply using an alpha,
which gives a solid color that can be mis-interpreted as another
graph.

I also wanted the ability to make it so that peak values could be
highlighted in a different color if desired, as in a cpu graph going
from green through yellow to red.

I haven't thought about making it carry information, although it might
be neat to show temporal distribution of an average value (ie, turn
the dataset on its side, and make it represent color instead of
displacement). I don't really know how to get into that, since all
I've played with so far is the drawing code.

>
> can you please also add a patch for the documentation ?

Hopefully the attached patch will suffice.

--
rian

_______________________________________________
rrd-developers mailing list
rrd-developers@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers

From forum: RRDTool - Dev

patch to do vertical gradients

2009-11-05T10:08:39Z

Somebody on the irc channel suggested that I post this patch here. The
patch is against rrdtool 1.3.8.

This adds the GRAD element, which acts more or less like an AREA,
except you can specify a second color and a height which is used to
create a gradient from one color to the next.

I also attached an example graph that uses this patch. The gradients
in it are generated with these commands:

GRAD:ips#4444ff:half\\ firewall\\ states
GRAD:Bin#00cc00#0099441f:0:incoming\\ bandwidth

The syntax is
vname-or-value[#color[#color:gradientheight][:legend]][:STACK]

if the second color is missing, it is assumed to be #00000000 and the
gradientheight defaults to 50

gradientheight can actually produce 3 kinds of results depending on its value:
gradientheight > 0
generates a fixed-height gradient from the data point down. (fire style)
gradientheight < 0
generates a fixed-height gradient from the 0 line to the data
point. (fixed style)
gradientheight == 0
generates a gradient that is stretched from the data point to the 0 line.
this is what the example image is using.

I would appreciate any comments or suggestions.

--
rian

[grad.patch]

diff -crB rrdtool-1.3.8/src/rrd_gfx.c ../rrdtool-1.3.8/src/rrd_gfx.c *** rrdtool-1.3.8/src/rrd_gfx.c Tue May 19 07:45:05 2009 --- ../rrdtool-1.3.8/src/rrd_gfx.c Thu Nov 5 10:17:01 2009 *************** *** 105,110 **** --- 106,147 ---- cairo_line_to(cr, x, y); } + /* add a point to a line or to an area */ + void gfx_add_rect_fadey( + image_desc_t *im, + double x1,double y1, + double x2,double y2, + double py, + gfx_color_t color1, + gfx_color_t color2, + double height) + { + cairo_t *cr = im->cr; + + cairo_new_path(cr); + gfx_area_fit(im, &x1, &y1); + gfx_area_fit(im, &x2, &y2); + cairo_line_to(cr, x1, y1); + cairo_line_to(cr, x1, y2); + cairo_line_to(cr, x2, y2); + cairo_line_to(cr, x2, y1); + cairo_close_path(cr); + cairo_pattern_t* p; + if (height < 0) { + p = cairo_pattern_create_linear(x1,y1,x2,y1+height); + } else if (height > 0) { + p = cairo_pattern_create_linear(x1,(y2+py)/2+height,x2,(y2+py)/2); + } else { + p = cairo_pattern_create_linear(x1,y1,x2,(y2+py)/2); + } + //cairo_pattern_t* p = cairo_pattern_create_linear(x1,py+50,x2,py); + cairo_pattern_add_color_stop_rgba(p, 1, color1.red,color1.green,color1.blue,color1.alpha); + cairo_pattern_add_color_stop_rgba(p, 0, color2.red,color2.green,color2.blue,color2.alpha); + cairo_set_source(cr, p); + cairo_pattern_destroy(p); + cairo_fill(cr); + } + void gfx_close_path( image_desc_t *im) { diff -crB rrdtool-1.3.8/src/rrd_graph.c ../rrdtool-1.3.8/src/rrd_graph.c *** rrdtool-1.3.8/src/rrd_graph.c Tue May 19 07:45:05 2009 --- ../rrdtool-1.3.8/src/rrd_graph.c Thu Nov 5 10:19:45 2009 *************** *** 227,232 **** --- 227,233 ---- conv_if(VRULE, GF_VRULE); conv_if(LINE, GF_LINE); conv_if(AREA, GF_AREA); + conv_if(GRAD, GF_GRAD); conv_if(STACK, GF_STACK); conv_if(TICK, GF_TICK); conv_if(TEXTALIGN, GF_TEXTALIGN); *************** *** 1176,1182 **** /* memory for the processed data */ for (i = 0; i < im->gdes_c; i++) { if ((im->gdes[i].gf == GF_LINE) || ! (im->gdes[i].gf == GF_AREA) || (im->gdes[i].gf == GF_TICK)) { if ((im->gdes[i].p_data = (rrd_value_t*)(malloc((im->xsize + 1) * sizeof(rrd_value_t)))) == NULL) { rrd_set_error("malloc data_proc"); --- 1177,1185 ---- /* memory for the processed data */ for (i = 0; i < im->gdes_c; i++) { if ((im->gdes[i].gf == GF_LINE) || ! (im->gdes[i].gf == GF_AREA) || ! (im->gdes[i].gf == GF_GRAD) || ! (im->gdes[i].gf == GF_TICK)) { if ((im->gdes[i].p_data = (rrd_value_t*)(malloc((im->xsize + 1) * sizeof(rrd_value_t)))) == NULL) { rrd_set_error("malloc data_proc"); *************** *** 1197,1202 **** --- 1200,1206 ---- switch (im->gdes[ii].gf) { case GF_LINE: case GF_AREA: + case GF_GRAD: case GF_TICK: if (!im->gdes[ii].stack) paintval = 0.0; *************** *** 1576,1581 **** --- 1580,1586 ---- break; case GF_LINE: case GF_AREA: + case GF_GRAD: case GF_TICK: graphelement = 1; break; *************** *** 3208,3213 **** --- 3213,3219 ---- break; case GF_LINE: case GF_AREA: + case GF_GRAD: /* fix data points at oo and -oo */ for (ii = 0; ii < im->xsize; ii++) { if (isinf(im->gdes[i].p_data[ii])) { *************** *** 3306,3311 **** --- 3312,3319 ---- cairo_stroke(im->cr); cairo_restore(im->cr); } else { + double lastx=0; + double lasty=0; int idxI = -1; double *foreY = (double *) malloc(sizeof(double) * im->xsize * 2); *************** *** 3336,3347 **** [cntI + 1], 4)) { cntI++; } ! gfx_new_area(im, ! backX[0], backY[0], ! foreX[0], foreY[0], ! foreX[cntI], ! foreY[cntI], im->gdes[i].col); ! while (cntI < idxI) { lastI = cntI; cntI++; while (cntI < idxI --- 3344,3360 ---- [cntI + 1], 4)) { cntI++; } ! if (im->gdes[i].gf != GF_GRAD) { ! gfx_new_area(im, ! backX[0], backY[0], ! foreX[0], foreY[0], ! foreX[cntI], ! foreY[cntI], im->gdes[i].col); ! } else { ! lastx = foreX[cntI]; ! lasty = foreY[cntI]; ! } ! while (cntI < idxI) { lastI = cntI; cntI++; while (cntI < idxI *************** *** 3357,3365 **** + 1], 4)) { cntI++; } ! gfx_add_point(im, foreX[cntI], foreY[cntI]); } ! gfx_add_point(im, backX[idxI], backY[idxI]); while (idxI > 1) { lastI = idxI; idxI--; --- 3370,3401 ---- + 1], 4)) { cntI++; } ! if (im->gdes[i].gf != GF_GRAD) { ! gfx_add_point(im, foreX[cntI], foreY[cntI]); ! } else { ! gfx_add_rect_fadey(im, ! lastx, foreY[0], ! foreX[cntI], foreY[cntI], lasty, ! im->gdes[i].col, ! im->gdes[i].col2, ! im->gdes[i].gradheight ! ); ! lastx = foreX[cntI]; ! lasty = foreY[cntI]; ! } } ! if (im->gdes[i].gf != GF_GRAD) { ! gfx_add_point(im, backX[idxI], backY[idxI]); ! } else { ! gfx_add_rect_fadey(im, ! lastx, foreY[0], ! backX[idxI], backY[idxI], lasty, ! im->gdes[i].col, ! im->gdes[i].col2, ! im->gdes[i].gradheight); ! lastx = backX[idxI]; ! lasty = backY[idxI]; ! } while (idxI > 1) { lastI = idxI; idxI--; *************** *** 3376,3386 **** - 1], 4)) { idxI--; } ! gfx_add_point(im, backX[idxI], backY[idxI]); } idxI = -1; drawem = 0; ! gfx_close_path(im); } if (drawem != 0) { drawem = 0; --- 3412,3434 ---- - 1], 4)) { idxI--; } ! if (im->gdes[i].gf != GF_GRAD) { ! gfx_add_point(im, backX[idxI], backY[idxI]); ! } else { ! gfx_add_rect_fadey(im, ! lastx, foreY[0], ! backX[idxI], backY[idxI], lasty, ! im->gdes[i].col, ! im->gdes[i].col2, ! im->gdes[i].gradheight); ! lastx = backX[idxI]; ! lasty = backY[idxI]; ! } } idxI = -1; drawem = 0; ! if (im->gdes[i].gf != GF_GRAD) ! gfx_close_path(im); } if (drawem != 0) { drawem = 0; *************** *** 3574,3579 **** --- 3622,3632 ---- im->gdes[im->gdes_c - 1].col.green = 0.0; im->gdes[im->gdes_c - 1].col.blue = 0.0; im->gdes[im->gdes_c - 1].col.alpha = 0.0; + im->gdes[im->gdes_c - 1].col2.red = 0.0; + im->gdes[im->gdes_c - 1].col2.green = 0.0; + im->gdes[im->gdes_c - 1].col2.blue = 0.0; + im->gdes[im->gdes_c - 1].col2.alpha = 0.0; + im->gdes[im->gdes_c - 1].gradheight = 50.0; im->gdes[im->gdes_c - 1].legend[0] = '\0'; im->gdes[im->gdes_c - 1].format[0] = '\0'; im->gdes[im->gdes_c - 1].strftm = 0; diff -crB rrdtool-1.3.8/src/rrd_graph.h ../rrdtool-1.3.8/src/rrd_graph.h *** rrdtool-1.3.8/src/rrd_graph.h Fri Dec 26 01:05:03 2008 --- ../rrdtool-1.3.8/src/rrd_graph.h Thu Nov 5 10:36:52 2009 *************** *** 51,57 **** #define GRIDWIDTH 0.4 enum gf_en { GF_PRINT = 0, GF_GPRINT, GF_COMMENT, GF_HRULE, GF_VRULE, GF_LINE, ! GF_AREA, GF_STACK, GF_TICK, GF_TEXTALIGN, GF_DEF, GF_CDEF, GF_VDEF, GF_SHIFT, GF_XPORT }; --- 51,57 ---- #define GRIDWIDTH 0.4 enum gf_en { GF_PRINT = 0, GF_GPRINT, GF_COMMENT, GF_HRULE, GF_VRULE, GF_LINE, ! GF_AREA,GF_GRAD, GF_STACK, GF_TICK, GF_TEXTALIGN, GF_DEF, GF_CDEF, GF_VDEF, GF_SHIFT, GF_XPORT }; *************** *** 156,162 **** long ds; /* data source number */ enum cf_en cf; /* consolidation function */ enum cf_en cf_reduce; /* consolidation function for reduce_data() */ ! struct gfx_color_t col; /* graph color */ char format[FMT_LEG_LEN + 5]; /* format for PRINT AND GPRINT */ char legend[FMT_LEG_LEN + 5]; /* legend */ int strftm; /* should the VDEF legend be formated with strftime */ --- 156,163 ---- long ds; /* data source number */ enum cf_en cf; /* consolidation function */ enum cf_en cf_reduce; /* consolidation function for reduce_data() */ ! struct gfx_color_t col, col2; /* graph color */ ! double gradheight; char format[FMT_LEG_LEN + 5]; /* format for PRINT AND GPRINT */ char legend[FMT_LEG_LEN + 5]; /* legend */ int strftm; /* should the VDEF legend be formated with strftime */ *************** *** 424,429 **** --- 425,449 ---- double x, double y); + /* create a rect that has a gradient from color1 to color2 in height pixels + * height > 0: + * gradient starts at top and goes down a fixed number of pixels (fire style) + * height < 0: + * gradient starts at bottom and goes up a fixed number of pixels (constant style) + * height == 0: + * gradient is stretched between two points + */ + void gfx_add_rect_fadey( + image_desc_t *im, + double x1,double y1, + double x2,double y2, + double py, + gfx_color_t color1, + gfx_color_t color2, + double height); + + + /* close current path so it ends at the same point as it started */ void gfx_close_path( image_desc_t *im); diff -crB rrdtool-1.3.8/src/rrd_graph_helper.c ../rrdtool-1.3.8/src/rrd_graph_helper.c *** rrdtool-1.3.8/src/rrd_graph_helper.c Tue May 19 07:45:05 2009 --- ../rrdtool-1.3.8/src/rrd_graph_helper.c Thu Nov 5 10:38:27 2009 *************** *** 532,538 **** graph_desc_t *const gdp, image_desc_t *const im) { ! int i, j, k; int colorfound = 0; char tmpstr[MAX_VNAME_LEN + 10]; /* vname#RRGGBBAA\0 */ static int spacecnt = 0; --- 532,538 ---- graph_desc_t *const gdp, image_desc_t *const im) { ! int i, j, k, j2; int colorfound = 0; char tmpstr[MAX_VNAME_LEN + 10]; /* vname#RRGGBBAA\0 */ static int spacecnt = 0; *************** *** 567,576 **** rrd_set_error("Cannot parse line '%s'", line); return 1; } ! ! j = i; while (j > 0 && tmpstr[j] != '#') j--; if (j) { tmpstr[j] = '\0'; --- 567,588 ---- rrd_set_error("Cannot parse line '%s'", line); return 1; } ! ! j = i; while (j > 0 && tmpstr[j] != '#') j--; + //see if there is a second color + j2 = j-1; + while (j2 > 0 && tmpstr[j2] != '#') + j2--; + if (j && j2) { //yes, swap j and j2, so that j is first color, j2 is second + int tmp = j; + j = j2; + j2 = tmp; + tmpstr[j2] = '\0'; + } else { + j2 = 0; + } if (j) { tmpstr[j] = '\0'; *************** *** 578,585 **** /* We now have: * tmpstr[0] containing vname * tmpstr[j] if j!=0 then containing color ! * i size of vname + color * j if j!=0 then size of vname */ /* Number or vname ? --- 590,599 ---- /* We now have: * tmpstr[0] containing vname * tmpstr[j] if j!=0 then containing color ! * tmpstr[j2] if j2!=0 then containing second color ! * i size of vname * j if j!=0 then size of vname + * j2 if j2!=0 then size of vname + first color */ /* Number or vname ? *************** *** 644,649 **** --- 658,690 ---- dprintf("- parsed color %0.0f,%0.0f,%0.0f,%0.0f\n", gdp->col.red, gdp->col.green, gdp->col.blue, gdp->col.alpha); colorfound = 1; + if (j2) { //second color? + j2++; + dprintf("- examining second color '%s'\n", &tmpstr[j2]); + //TODO: maybe rrd_parse_color should take a pointer to gdp->col instead of gdp + struct gfx_color_t firstcol = gdp->col; + if (rrd_parse_color(&tmpstr[j2], gdp)) { + rrd_set_error("Could not parse color in '%s'", &tmpstr[j2]); + return 1; + } + dprintf("- parsed color %0.0f,%0.0f,%0.0f,%0.0f\n", gdp->col.red, + gdp->col.green, gdp->col.blue, gdp->col.alpha); + gdp->col2 = gdp->col; + gdp->col = firstcol; + //we now have a mandatory grid height + (*eaten) += i; + if (line[*eaten] != '\0') { + (*eaten)++; + } + dprintf("- examining gradient height\n"); + i = scan_for_col(&line[*eaten], MAX_VNAME_LEN + 9, tmpstr); + sscanf(tmpstr, "%lf%n", &gdp->gradheight, &j); + if (i != j) { + rrd_set_error("Could not parse gradient height in '%s'", tmpstr); + return 1; + } + dprintf("- parsed gradientheight %0.0f\n", gdp->gradheight); + } } else { dprintf("- no color present in '%s'\n", tmpstr); } *************** *** 1113,1118 **** --- 1154,1160 ---- case GF_HRULE: /* value#color[:legend] */ case GF_LINE: /* vname-or-value[#color[:legend]][:STACK] */ case GF_AREA: /* vname-or-value[#color[:legend]][:STACK] */ + case GF_GRAD: /* vname-or-value[#color[:legend][#color[:gradientheight]]][:STACK] */ case GF_TICK: /* vname#color[:num[:legend]] */ if (rrd_parse_PVHLAST(argv[i], &eaten, gdp, im)) return; *************** *** 1122,1128 **** case GF_STACK: /* vname-or-value[#color[:legend]] */ if (rrd_parse_PVHLAST(argv[i], &eaten, gdp, im)) return; ! if (last_gf == GF_LINE || last_gf == GF_AREA) { gdp->gf = last_gf; gdp->linewidth = last_linewidth; } else { --- 1164,1170 ---- case GF_STACK: /* vname-or-value[#color[:legend]] */ if (rrd_parse_PVHLAST(argv[i], &eaten, gdp, im)) return; ! if (last_gf == GF_LINE || last_gf == GF_AREA || last_gf == GF_GRAD) { gdp->gf = last_gf; gdp->linewidth = last_linewidth; } else {

_______________________________________________
rrd-developers mailing list
rrd-developers@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers

samplegradientgraph.png (98K) Download Attachment

From forum: RRDTool - Dev

Re: rrdresize on munin-created rrd files

2009-11-05T09:28:04Z

You may want to have a look at
http://docs.cacti.net/manual:087:8_rrdtool#rrdtool in general and for the
resizing task at
http://docs.cacti.net/manual:087:8_rrdtool.04_resize#resize_rrd_files

As you may have deduced from the url, this was done for the cacti world but
should apply to other rrdtool based projects as well.
Reinhard

Am 05.11.2009 13:38, Jacob Alexandersson wrote:

> Hi,
>
> Thank you for your reply! I'll look at writing up a script that will
> convert all my munin-created files accordingly.
> :-)
>
> Cheers,
>
> Jacob.
>
>
>
> On Thu, Nov 5, 2009 at 1:30 PM, Tobias Oetiker<tobi@...> wrote:
>
>> Today Tobias Oetiker wrote:
>>
>>>
>>> I would structure the RRD as follows:
>>>
>>> RRA 90 Days at 1 step AVERAGE
>>> RRA 90 Days at 6 step AVERAGE
>>> RRA 90 Days at 6 step MAX
>>> RRA 90 Days at 6 step MIN
>>
>> the reason for keeping the lower resolution arround is that it will
>> accelerate graphing since rrd graph does not have to consolidate
>> every time you draw a low resolution graph ...
>>
>> obviously you may want additional RRAs at even lower resolutions
>> ...
>>
>> cheers
>> tobi
>>
>>>
>>> using MIN and MAX at 1 step makes little sense
>>>
>>> cheers
>>> tobi
>>>
>>>
>>>>
>>>> What I am looking for is to store "fully accurate" data for a
>>>> much longer time than the (munin) default of 48 hours.
>>>
>>>
>>>> //J
>>>>
>>>> ---------------
>>>>
>>>
>>>
>>
>> --
>> Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
>> http://it.oetiker.ch tobi@... ++41 62 775 9902 / sb: -9900
>>
>
>
>
>
>
> _______________________________________________
> rrd-users mailing list
> rrd-users@...
> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: rrdresize on munin-created rrd files

2009-11-05T04:38:56Z

Hi,

Thank you for your reply! I'll look at writing up a script that will convert all my munin-created files accordingly.
:-)

Cheers,

Jacob.

On Thu, Nov 5, 2009 at 1:30 PM, Tobias Oetiker <tobi@...> wrote:

Today Tobias Oetiker wrote:

>
> I would structure the RRD as follows:
>
> RRA 90 Days at 1 step AVERAGE
> RRA 90 Days at 6 step AVERAGE
> RRA 90 Days at 6 step MAX
> RRA 90 Days at 6 step MIN

the reason for keeping the lower resolution arround is that it will
accelerate graphing since rrd graph does not have to consolidate
every time you draw a low resolution graph ...

obviously you may want additional RRAs at even lower resolutions
...

cheers
tobi

>
> using MIN and MAX at 1 step makes little sense
>
> cheers
> tobi
>
>
> >
> > What I am looking for is to store "fully accurate" data for a
> > much longer time than the (munin) default of 48 hours.
>
>
> > //J
> >
> > ---------------
> >
>
>

--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi@... ++41 62 775 9902 / sb: -9900

--
________________________________________
Jacob Alexandersson, Aligerum AB
Strandbergsgatan 61
SE-112 51 Stockholm
Phone: +468-555 36 266
Mobile: +4676-146 33 10
aligerum.se | aligerum.com | aligerum.it

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: rrdresize on munin-created rrd files

2009-11-05T04:30:46Z

Today Tobias Oetiker wrote:

>
> I would structure the RRD as follows:
>
> RRA 90 Days at 1 step AVERAGE
> RRA 90 Days at 6 step AVERAGE
> RRA 90 Days at 6 step MAX
> RRA 90 Days at 6 step MIN

the reason for keeping the lower resolution arround is that it will
accelerate graphing since rrd graph does not have to consolidate
every time you draw a low resolution graph ...

obviously you may want additional RRAs at even lower resolutions
...

cheers
tobi

>
> using MIN and MAX at 1 step makes little sense
>
> cheers
> tobi
>
>
> >
> > What I am looking for is to store "fully accurate" data for a
> > much longer time than the (munin) default of 48 hours.
>
>
> > //J
> >
> > ---------------
> >
>
>

--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi@... ++41 62 775 9902 / sb: -9900

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: rrdresize on munin-created rrd files

2009-11-05T04:29:24Z

Hi Jacob,

Today Jacob Alexandersson wrote:

> Hello all,
>
> I posted the message below on the munin userlist a couple of days back but I
> haven't gotten any response. Hopefully someone can help out here?
>
> //Jacob.
>
> --------------
>
> Hello all,
>
> I've been digging around a bit on how munin creates its rrd
> files. I don't claim to understand much on the inner workings on
> rrd, but this is what I've managed to dig up:
>
> >From my understanding, "rrdtool info <filename>" tells me that the first
> three rra's save one pdp per row, meaning that they don't average
> out anything. We have 576 rows, where the "step" is 300 seconds
> which works out to be 48 hours.
>
> So we have 48 hours of fully accurate data stored (nothing averaged out).
>
> I want "fully accurate" data to be stored much longer. Say 90 days.
>
> 90 days = 7776000 seconds. /300 gives me 25920 rows. So I need to
> add 25344 rows to each rra. This can be achieved by:
>
> $ rrdtool resize filename.rrd 0 GROW 25344
>
> ...where "0" points out the first rra.
>
> I could do this for the first three rra's, but what about the
> other ones? There is a set of rra's that store data for 9 days
> over 30min averages if my calculations are correct. This clearly
> falls within the span of my 90 days above. Will these rra's ever
> be used? Or should I modify these accordingly to something
> appropriate after my change above?

when rrd fetch (via rrd graph) pulls data from an rrd file it will
pull the data that BEST matches the resolution required to draw the
graph. This means given a weekly graph it would probably pull the
data from that 9 day RRA ... OTOH if you drew a graph over two
weeks it might fall back to your new 90 days RRA since this
provides better coverage.
>
> I guess what I'm really asking is:
> Is this the right way of going about this?

I would structure the RRD as follows:

RRA 90 Days at 1 step AVERAGE
RRA 90 Days at 6 step AVERAGE
RRA 90 Days at 6 step MAX
RRA 90 Days at 6 step MIN

using MIN and MAX at 1 step makes little sense

cheers
tobi

>
> What I am looking for is to store "fully accurate" data for a
> much longer time than the (munin) default of 48 hours.

> //J
>
> ---------------
>

--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi@... ++41 62 775 9902 / sb: -9900

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

rrdresize on munin-created rrd files

2009-11-05T00:57:02Z

Hello all,

I posted the message below on the munin userlist a couple of days back but I haven't gotten any response. Hopefully someone can help out here?

//Jacob.

--------------

Hello all,

I've been digging around a bit on how munin creates its rrd files. I don't claim to
understand much on the inner workings on rrd, but this is what I've managed to dig up:

From my understanding, "rrdtool info <filename>" tells me that the first three rra's
save one pdp per row, meaning that they don't average out anything. We have 576 rows,
where the "step" is 300 seconds which works out to be 48 hours.

So we have 48 hours of fully accurate data stored (nothing averaged out).

I want "fully accurate" data to be stored much longer. Say 90 days.

90 days = 7776000 seconds. /300 gives me 25920 rows. So I need to add 25344 rows to each rra.
This can be achieved by:

$ rrdtool resize filename.rrd 0 GROW 25344

...where "0" points out the first rra.

I could do this for the first three rra's, but what about the other ones?
There is a set of rra's that store data for 9 days over 30min averages if my calculations are
correct. This clearly falls within the span of my 90 days above. Will these rra's ever be used?
Or should I modify these accordingly to something appropriate after my change above?

I guess what I'm really asking is:
Is this the right way of going about this?

What I am looking for is to store "fully accurate" data for a much longer time than the (munin)
default of 48 hours.

//J

---------------

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: rrdtool 1.4.x without graphing support?

2009-11-04T23:58:33Z

Hi,

On Thu, Nov 05, 2009 at 05:53:20AM +0100, Tobias Oetiker wrote:
> Yesterday Ulf Zimmermann wrote:
> > Anyone got an idea how much work would be involved to build/patch
> > rrdtool 1.4.x to remove graphing support? Library dependency for
> > EL4 is just hell at this point. And as I need librrd, I am not
> > sure how far I can work with a static build to work with collectd
> > together.
>
> you may want to try the appended patch.

> +if BUILD_RRDGRAPH
> +RRD_C_FILES += rrd_graph.c \
> + rrd_graph_helper.c \
> + rrd_xport.c \
> + rrd_gfx.c \
> + pngsize.c
> +endif
[…]

NB: RRD_C_FILES is later used to specify the source files for librrd.

In case this patch is supposed to be included in RRDtool, please note
that it provides an easy way to build RRDtool with a different API /
ABI. Hence, it requires a different SONAME version (or even better: a
different SONAME -- which would be easier to implement as well).

Anyway, rather than including this (imho) somewhat hackish way, I'd
rather go for splitting the library as discussed before (librrd /
librrdgraph). I'm willing to provide a patch for that targeted at
RRDtool 1.5 (it will probably require a SONAME version bump, thus, it
should imho not be included in 1.4 -- I'd also provide patches for
reverse dependencies known to be affected by that).

Cheers,
Sebastian

--
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

signature.asc (204 bytes) Download Attachment

From forum: RRDTool - User

Re: Invalid UTF-8 string#

2009-11-04T22:56:53Z

On Wed, Nov 04, 2009 at 05:21:08AM +0100, Tobias Oetiker wrote:

> Hi Stefan,
>
> Yesterday Stefan M. Brandl wrote:
>
> > Hello,
> > just upgrade from rrdtool 1.3.8 to 1.3.9
> > and I get
> >
> > (process:30282): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
> >
> > when I do a rrdtool graph ...
> > And have a ° (degree) sign in the GPRINT line.
>
>
> this is the kind of error you would get if you were running wit a
> locale setting suggesting utf8 encoding and then inputing data
> encoded with latin1 for example.
>

Ups, you are right.
Setting the "correct" locale did the job.

Thanks
Stefan

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: rrdtool 1.4.x without graphing support?

2009-11-04T20:53:20Z

Hi Ulf,

Yesterday Ulf Zimmermann wrote:

> Anyone got an idea how much work would be involved to build/patch
> rrdtool 1.4.x to remove graphing support? Library dependency for
> EL4 is just hell at this point. And as I need librrd, I am not
> sure how far I can work with a static build to work with collectd
> together.

you may want to try the appended patch.

cheers
tobi

>
> Ulf.
>
>

--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi@... ++41 62 775 9902 / sb: -9900
Index: src/rrd_tool.c
===================================================================
--- src/rrd_tool.c (revision 1966)
+++ src/rrd_tool.c (working copy)
@@ -693,6 +693,7 @@
free(data);
}
} else if (strcmp("xport", argv[1]) == 0) {
+#ifdef HAVE_RRD_GRAPH
int xxsize;
unsigned long int j = 0;
time_t start, end, ti;
@@ -766,7 +767,11 @@
printf("</%s>\n", ROOT_TAG);
}
free(vtag);
+#else
+ rrd_set_error("the instance of rrdtool has been compiled without graphcs");
+#endif
} else if (strcmp("graph", argv[1]) == 0) {
+#ifdef HAVE_RRD_GRAPH
char **calcpr;

#ifdef notused /*XXX*/
@@ -799,8 +804,11 @@
free(calcpr);
}
}
-
+#else
+ rrd_set_error("the instance of rrdtool has been compiled without graphcs");
+#endif
} else if (strcmp("graphv", argv[1]) == 0) {
+#ifdef HAVE_RRD_GRAPH
rrd_info_t *grinfo = NULL; /* 1 to distinguish it from the NULL that rrd_graph sends in */

grinfo = rrd_graph_v(argc - 1, &argv[1]);
@@ -808,7 +816,9 @@
rrd_info_print(grinfo);
rrd_info_free(grinfo);
}
-
+#else
+ rrd_set_error("the instance of rrdtool has been compiled without graphcs");
+#endif
} else if (strcmp("tune", argv[1]) == 0)
rrd_tune(argc - 1, &argv[1]);
else if (strcmp("flushcached", argv[1]) == 0)
Index: src/Makefile.am
===================================================================
--- src/Makefile.am (revision 1966)
+++ src/Makefile.am (working copy)
@@ -29,27 +29,30 @@
rrd_nan_inf.c \
rrd_rpncalc.c \
rrd_utils.c \
- rrd_update.c
+ rrd_update.c \
+ hash_32.c

RRD_C_FILES = \
- hash_32.c \
- pngsize.c \
rrd_create.c \
- rrd_graph.c \
- rrd_graph_helper.c \
rrd_version.c \
rrd_last.c \
rrd_lastupdate.c \
rrd_first.c \
rrd_restore.c \
- rrd_xport.c \
- rrd_gfx.c \
rrd_dump.c \
rrd_flushcached.c \
rrd_fetch.c \
rrd_resize.c \
rrd_tune.c

+if BUILD_RRDGRAPH
+RRD_C_FILES += rrd_graph.c \
+ rrd_graph_helper.c \
+ rrd_xport.c \
+ rrd_gfx.c \
+ pngsize.c
+endif
+
noinst_HEADERS = \
unused.h \
gettext.h \
Index: configure.ac
===================================================================
--- configure.ac (revision 1966)
+++ configure.ac (working copy)
@@ -102,6 +102,13 @@
AC_ARG_ENABLE(rrdcgi,AS_HELP_STRING([--disable-rrdcgi],[disable building of rrdcgi]),
[],[enable_rrdcgi=yes])

+AC_ARG_ENABLE(rrd_graph,AS_HELP_STRING([--disable-rrd_graph],[disable all rrd_graph functions]),
+[enable_rrdcgi=no],[enable_rrd_graph=yes])
+
+if test $enable_rrd_graph != no; then
+ AC_DEFINE([HAVE_RRD_GRAPH], [], [is rrd_graph supported by this install])
+fi
+
dnl Check if we run on a system that has fonts
AC_ARG_WITH(rrd-default-font,
[ --with-rrd-default-font=[OPTIONS] set the full path to your default font.],
@@ -510,19 +517,21 @@

AM_CONDITIONAL(BUILD_RRDCGI,[test $enable_rrdcgi != no])

+AM_CONDITIONAL(BUILD_RRDGRAPH,[test $enable_rrd_graph != no])

+
CORE_LIBS="$LIBS"

-dnl EX_CHECK_ALL(z, zlibVersion, zlib.h, zlib, 1.2.3, http://www.gzip.org/zlib/, "")
-dnl EX_CHECK_ALL(png, png_access_version_number, png.h, libpng, 1.2.10, http://prdownloads.sourceforge.net/libpng/, "")
-dnl EX_CHECK_ALL(freetype, FT_Init_FreeType, ft2build.h, freetype2, 2.1.10, http://prdownloads.sourceforge.net/freetype/, /usr/include/freetype2)
-dnl EX_CHECK_ALL(fontconfig, FcInit, fontconfig.h, fontconfig, 2.3.1, http://fontconfig.org/release/, /usr/include)
+if test $enable_rrd_graph != no; then
EX_CHECK_ALL(cairo, cairo_font_options_create, cairo.h, cairo-png, 1.4.6, http://cairographics.org/releases/, "")
EX_CHECK_ALL(cairo, cairo_svg_surface_create, cairo-svg.h, cairo-svg, 1.4.6, http://cairographics.org/releases/, "")
EX_CHECK_ALL(cairo, cairo_pdf_surface_create, cairo-pdf.h, cairo-pdf, 1.4.6, http://cairographics.org/releases/, "")
EX_CHECK_ALL(cairo, cairo_ps_surface_create, cairo-ps.h, cairo-ps, 1.4.6, http://cairographics.org/releases/, "")
+fi
EX_CHECK_ALL(glib-2.0, glib_check_version, glib.h, glib-2.0, 2.12.12, ftp://ftp.gtk.org/pub/glib/2.12/, "")
+if test $enable_rrd_graph != no; then
EX_CHECK_ALL(pango-1.0, pango_cairo_context_set_font_options, pango/pango.h, pangocairo, 1.17, http://ftp.gnome.org/pub/GNOME/sources/pango/1.17, "")
+fi
EX_CHECK_ALL(xml2, xmlParseFile, libxml/parser.h, libxml-2.0, 2.6.31, http://xmlsoft.org/downloads.html, /usr/include/libxml2)

if test "$EX_CHECK_ALL_ERR" = "YES"; then
@@ -932,6 +941,7 @@
echo
echo " With MMAP IO: $enable_mmap"
echo " Build rrd_getopt: $build_getopt"
+echo " Build rrd_graph: $enable_rrd_graph"
echo " Static programs: $staticprogs"
echo " Perl Modules: $COMP_PERL"
echo " Perl Binary: $PERL"

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: Trying to build rrdtool 1.4.1 on RedHat EL4

2009-11-04T17:50:39Z

Hi Ulf,

I'm going to trim some of the reply and top-post, for brevity ...

Are you able to get the rrdtool 1.4.1 fully working from source compile?

If so, is there any helpful info you could share RE the packages and/or
independent sources you had to install due to pre-existing EL4 versions?

Does it even work from a source compile on a stock EL4 + evolution28 box?

Thanks,

--
William R. Lorenz

On Wed, 4 Nov 2009, Ulf Zimmermann wrote:

> Using them I continued on trying to build rrdtool. Next stopper was
> rrd_restore.c wanting to use xmlTextReaderGetParserLineNumber when
> printing out errors about importing. This function was defined in
> libxml2 2.6.17, EL4 only has 2.6.16. Got around it by just doing

[...]

> Continuing on the next hurdle was dejavu-lgc-fonts, which is available
> on EL5, is noarch but requires fontconfig >= 2.3, I rebuild it for now
> setting fontconfig requirement to just >= 2.2.

> Now the rpm refuses still to install because of it is looking for
> libpangocairo-1.0.so.0, which is in /usr/evolution28/lib, but the
> evolution28 rpms don't add any ld.conf file to point there, so I am
> still trying to figure out how to teach rpmbuild/rpm to look there for
> the libs for installing and running. As compiled it does:

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: Trying to build rrdtool 1.4.1 on RedHat EL4

2009-11-04T17:39:23Z

> -----Original Message-----
> From: William R. Lorenz [mailto:wrl@...]
> Sent: Wednesday, November 04, 2009 4:50 PM
> To: Ulf Zimmermann
> Cc: 'Tobias Oetiker'; rrd-users@...
> Subject: Re: [rrd-users] Trying to build rrdtool 1.4.1 on RedHat EL4
>
> Hi Ulf,
>
> On Wed, 4 Nov 2009, Ulf Zimmermann wrote:
>
> >> Ok, I got a working configure now on EL4, I will see to modify the
> >> .spec file in a few minutes to see if I can build a rpm from it.
>
> > Now running into actual compile problems with libxml2. Rrdtool 1.4.1
> > code wants xmlTextReaderGetParserLineNumber, which was added to
> libxml2
> > 2.6.17 and EL4 only has 2.6.16, sigh.
>
> Welcome to my RPM building world. That's why I didn't make EL4 RPMs.
> ;-)
>
> > evolution28-cairo-1.2.4-6.el4.i386.rpm
> > evolution28-cairo-devel-1.2.4-6.el4.i386.rpm
> > evolution28-glib2-2.12.3-6.el4.i386.rpm
> > evolution28-glib2-devel-2.12.3-6.el4.i386.rpm
> > evolution28-pango-1.14.9-11.el4_7.i386.rpm
> > evolution28-pango-devel-1.14.9-11.el4_7.i386.rpm
>
> Where did you find these evolution28 packages? I may try to take a
> peek
> and see if I can't make something work with these and some other
> packages.
> Is there a particular site with the SRPMS for these so I can
> deconstruct?

They are part of RH EL4 Updates, also available via CentOS. They provided an Evolution 2.8 package, which needs these updated libraries.

Using them I continued on trying to build rrdtool. Next stopper was rrd_restore.c wanting to use xmlTextReaderGetParserLineNumber when printing out errors about importing. This function was defined in libxml2 2.6.17, EL4 only has 2.6.16. Got around it by just doing

#define xmlTextReaderGetParserLineNumber(xmlTextReaderPtr) 0

Which just means any error will show line 0, instead of the real line when there is an import.

Continuing on the next hurdle was dejavu-lgc-fonts, which is available on EL5, is noarch but requires fontconfig >= 2.3, I rebuild it for now setting fontconfig requirement to just >= 2.2.

Now the rpm refuses still to install because of it is looking for libpangocairo-1.0.so.0, which is in /usr/evolution28/lib, but the evolution28 rpms don't add any ld.conf file to point there, so I am still trying to figure out how to teach rpmbuild/rpm to look there for the libs for installing and running. As compiled it does:

el4build ulf rpmbuild/SPECS > ldd /usr/bin/rrdtool
librrd.so.4 => /usr/lib/librrd.so.4 (0x00c7a000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0x008f2000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x004b4000)
libm.so.6 => /lib/tls/libm.so.6 (0x00295000)
libpangocairo-1.0.so.0 => not found
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x0013e000)
libcairo.so.2 => /usr/lib/libcairo.so.2 (0x00821000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x0089d000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00886000)
libdl.so.2 => /lib/libdl.so.2 (0x00111000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00174000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00a3d000)
libz.so.1 => /usr/lib/libz.so.1 (0x0088b000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00d6e000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0x00676000)
libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x00adc000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x004c8000)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x005a9000)
libc.so.6 => /lib/tls/libc.so.6 (0x002b8000)
/lib/ld-linux.so.2 (0x00127000)
libpangocairo-1.0.so.0 => not found
libdirectfb-1.2.so.0 => /usr/lib/libdirectfb-1.2.so.0 (0x00f6d000)
libfusion-1.2.so.0 => /usr/lib/libfusion-1.2.so.0 (0x00498000)
libdirect-1.2.so.0 => /usr/lib/libdirect-1.2.so.0 (0x001ef000)
libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x006c3000)
libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x00202000)
libexpat.so.0 => /usr/lib/libexpat.so.0 (0x0021a000)

>
> Thanks,
>
> --
> William R. Lorenz

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: Trying to build rrdtool 1.4.1 on RedHat EL4

2009-11-04T16:50:29Z

Hi Ulf,

On Wed, 4 Nov 2009, Ulf Zimmermann wrote:

>> Ok, I got a working configure now on EL4, I will see to modify the
>> .spec file in a few minutes to see if I can build a rpm from it.

> Now running into actual compile problems with libxml2. Rrdtool 1.4.1
> code wants xmlTextReaderGetParserLineNumber, which was added to libxml2
> 2.6.17 and EL4 only has 2.6.16, sigh.

Welcome to my RPM building world. That's why I didn't make EL4 RPMs. ;-)

> evolution28-cairo-1.2.4-6.el4.i386.rpm
> evolution28-cairo-devel-1.2.4-6.el4.i386.rpm
> evolution28-glib2-2.12.3-6.el4.i386.rpm
> evolution28-glib2-devel-2.12.3-6.el4.i386.rpm
> evolution28-pango-1.14.9-11.el4_7.i386.rpm
> evolution28-pango-devel-1.14.9-11.el4_7.i386.rpm

Where did you find these evolution28 packages? I may try to take a peek
and see if I can't make something work with these and some other packages.
Is there a particular site with the SRPMS for these so I can deconstruct?

Thanks,

--
William R. Lorenz

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

rrdtool 1.4.x without graphing support?

2009-11-04T15:22:42Z

Anyone got an idea how much work would be involved to build/patch rrdtool 1.4.x to remove graphing support? Library dependency for EL4 is just hell at this point. And as I need librrd, I am not sure how far I can work with a static build to work with collectd together.

Ulf.

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: Trying to build rrdtool 1.4.1 on RedHat EL4

2009-11-04T14:19:13Z

> -----Original Message-----
> From: Ulf Zimmermann
> Sent: Tuesday, November 03, 2009 11:25 AM
> To: Ulf Zimmermann; 'Tobias Oetiker'
> Cc: rrd-users@...
> Subject: RE: [rrd-users] Trying to build rrdtool 1.4.1 on RedHat EL4
>
> Ok, I got a working configure now on EL4, I will see to modify the
> .spec file in a few minutes to see if I can build a rpm from it.
>
> Here is what I have done:
>
> Install from RHEL 4 Updates:
>
> evolution28-cairo-1.2.4-6.el4.i386.rpm
> evolution28-cairo-devel-1.2.4-6.el4.i386.rpm
> evolution28-glib2-2.12.3-6.el4.i386.rpm
> evolution28-glib2-devel-2.12.3-6.el4.i386.rpm
> evolution28-pango-1.14.9-11.el4_7.i386.rpm
> evolution28-pango-devel-1.14.9-11.el4_7.i386.rpm
>
> Set LDFLAGS:
>
> setenv LDFLAGS -L/usr/evolution28/lib
>
> Set PKG_CONFIG_PATH:
>
> setenv PKG_CONFIG_PATH
> /usr/evolution28/lib/pkgconfig:/usr/lib/pkgconfig
>
> Run configure:
>
> ./configure
>
> This results in an ok run as far I can tell.
>
> Ulf.

Now running into actual compile problems with libxml2. Rrdtool 1.4.1 code wants xmlTextReaderGetParserLineNumber, which was added to libxml2 2.6.17 and EL4 only has 2.6.16, sigh.

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: RRD Newbee needs help with RRD Perl script

2009-11-04T12:51:55Z

Here are some instructions I use for fixing the RRDs location problem (which I think is what you're experiencing). >From FlowViewer FAQ:

http://ensight.eos.nasa.gov/FlowViewer/faq.html#16

If the FlowTracker Group page appears but there is no sample graph at the top, or you
receive an "Internal Server Error" (most likely Perl compilation problem, it could be that
you haven't correctly installed RRDs.pm. A quick way to check for this is to issue a
'perl -c FlowTracker_Group.cgi' from a command line. If there is a RRDs.pm location problem
the script will not compile.

This problem can be tricky and I will try to make it easier in the next version. In the meantime
the easiest way to fix this is:

1. Do a 'perl -V' from a command line, and look at the @INC array

@INC:
/usr/lib/perl5/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/5.8.5
/usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
( ... more )

2. Identify the most likely directory into which to put a copy of RRDs.pm

probably: /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi

3. Copy RRDs.pm into that directory

from: /usr/local/rrdtool-1.2.26/lib/perl/5.8.5/i386-linux-thread-multi/RRDs.pm
to: /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/RRDs.pm

4. Copy the RRDs and RRDp 'auto' subdirectories and their contents into the Perl 'auto' subdirectory

from: /usr/local/rrdtool-1.2.26/lib/perl/5.8.5/i386-linux-thread-multi/auto/RRDp
to: /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/auto/RRDp

from: /usr/local/rrdtool-1.2.26/lib/perl/5.8.5/i386-linux-thread-multi/auto/RRDs
to: /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/auto/RRDs

Note: the above can be accomplished using links instead of copying.

Joe

From:	Mark Woodruff <n3hf@...>
To:	Koaps <koaps@...>, rrd-users@...
Date:	11/04/2009 01:52 PM
Subject:	Re: [rrd-users] RRD Newbee needs help with RRD Perl script

Chris, Thank you for the feedback. I tried rewriting something with RRDs but no success, something must be missing from the installation (I think!).

Can't locate loadable object for module RRDs in @INC (@INC contains: /usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.

.5 /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/ve

dor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl .) at ./temp-one.cgi line 27

Compilation failed in require at ./temp-one.cgi line 27.

Mark

From: Koaps <koaps@...>
To: Mark Woodruff <n3hf@...>
Sent: Tue, November 3, 2009 8:42:04 PM
Subject: Re: [rrd-users] RRD Newbee needs help with RRD Perl script

I have no idea about RRDp but I have used RRDs with no issues in perl scripts.

The graph subroutine I used looked like this:

# print "Creating graph\n";
RRDs::graph ("$png_path/$k.png",
"--title=$TITLE $k",
"--vertical-label=$VLABEL",
"--color=$BACK",
"--color=$SHADEA",
"--color=$SHADEB",
"--color=$FONT",
"--color=$CANVAS",
"--color=$GRID",
"--color=$MGRID",
"--color=$FRAME",
"--color=$ARROW",
"--base=$BASE",
"DEF:avg=$rrd_path/$k.rrd:$ds:AVERAGE",
"DEF:pred=$rrd_path/$k.rrd:$ds:HWPREDICT",
"DEF:dev=$rrd_path/$k.rrd:$ds:DEVPREDICT",
"DEF:fail=$rrd_path/$k.rrd:$ds:FAILURES",
"COMMENT: \\n",
"CDEF:mbs=avg,1048576,/",
"LINE2:$AVG_LINE:Average MB/s",
"GPRINT:mbs:AVERAGE:\\: %5.2lf",
"GPRINT:mbs:LAST: Last\\: %5.2lf\\n",
"TICK:$TICK:1.0:Failures",
"CDEF:upper=pred,dev,2,*,+",
"CDEF:lower=pred,dev,2,*,-",
"LINE1:$UPPER_LINE:Upper Bound",
"LINE1:$LOWER_LINE:Lower Bound",
"\\n",
"COMMENT:$date",
);
$err=RRDs::error;
if ($err) {print "problem generating the graph: $err\n";}

with variables defined like this:
NOTE: $k for me was pulled from a reference I generated, you should be able to set it to your RRD without any issues.

#--------------#
# RRDTool vars #
#--------------#
my $png_path = "/var/www/html/";
my $TITLE = "IO Test:";
my $VLABEL = "Bytes per second (B/s)";
my $BACK = "BACK#000000";
my $SHADEA = "SHADEA#FFFFFF";
my $SHADEB = "SHADEB#FFFFFF";
my $FONT = "FONT#DDDDDD";
my $CANVAS = "CANVAS#202020";
my $GRID = "GRID#666666";
my $MGRID = "MGRID#AAAAAA";
my $FRAME = "FRAME#202020";
my $ARROW = "ARROW#FFFFFF";
my $BASE = 1024;
my $AVG_LINE = "AVG#0000FF";
my $TICK = "FAIL#FFFFA0";
my $UPPER_LINE = "UPPER#ff0000";
my $LOWER_LINE = "LOWER#ff0000";

-Chris

--- On Tue, 11/3/09, Mark Woodruff <n3hf@...> wrote:

> From: Mark Woodruff <n3hf@...>
> Subject: [rrd-users] RRD Newbee needs help with RRD Perl script
> To: rrd-users@...
> Date: Tuesday, November 3, 2009, 5:03 PM
> Recently installed Version 1.3.8
> and have been trying to make a Perl script wrritten by Brian
> Lane (Digitemp) from what I have been able to determine the
> scripts hangs up on the line containing:
>
> $answer=RRDp::read;
>
> # Output a HTML header for the PNG
> image to follow
>
> print $cgi->header('image/png');
> # Generate the graph
> RRDp::cmd "graphv - --imgformat PNG",
> "--start '$starttime' --end
> '$endtime'",
> "--width $width --height $height",
> "DEF:temp_c=$rrd:$var:AVERAGE",
> "CDEF:temp_f=temp_c,9,*,5,/,32,+",
> "LINE1:temp_f$color:'$label'";
> $answer=RRDp::read;
> print $$answer;
> RRDp::end;
>
> After reading rrd tutiorial I wrote a
> shorten bash script which works fine which tells me my
> RRD datafile is fine. Is there a bug and/or do I have
> installation issue??
>
> Mark
>
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> rrd-users mailing list
> rrd-users@...
> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
>

_______________________________________________ rrd-users mailing list rrd-users@...https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: RRD Newbee needs help with RRD Perl script

2009-11-04T12:13:39Z

Hi Mark,

You're missing the module, did you build rrdtool from source or use a RPM/YUM?

To check you can do:

updatedb
locate RRDs

If the perl module is installed you should get something like:

/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/RRDs.pm

If you find the module but it's not in a perl ISA path you will need to add a line like this to tell perl where the module is:

use lib qw( /path/to/RRDs );

I tend to build rrdtool from source per the rrdbuild:

http://oss.oetiker.ch/rrdtool/doc/rrdbuild.en.html

If you are on centos, you can yum install perl-rrdtool and that should get you want you need.

-Chris

--- On Wed, 11/4/09, Mark Woodruff <n3hf@...> wrote:

> From: Mark Woodruff <n3hf@...>
> Subject: Re: [rrd-users] RRD Newbee needs help with RRD Perl script
> To: "Koaps" <koaps@...>, rrd-users@...
> Date: Wednesday, November 4, 2009, 10:52 AM
>
> Chris, Thank you for the feedback. I tried rewriting
> something with RRDs but no success, something must be
> missing from the installation (I think!).
>
> Can't locate loadable object for module RRDs in @INC
> (@INC contains: /usr/lib/perl5/5.8.5/i386-linux-thread-multi
> /usr/lib/perl5/5.
> .5
> /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
> /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
> /usr/lib/perl5/ve
> dor_perl/5.8.5/i386-linux-thread-multi
> /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl
> .) at ./temp-one.cgi line 27
> Compilation failed in require at ./temp-one.cgi line
> 27.
>
> Mark
>
>
>
>
>
> From: Koaps
> <koaps@...>
> To: Mark
> Woodruff <n3hf@...>
> Sent: Tue,
> November 3, 2009 8:42:04 PM
> Subject: Re:
> [rrd-users] RRD Newbee needs help with RRD Perl script
>
> I have no idea about RRDp but I have used RRDs with no
> issues in perl scripts.
>
> The graph subroutine I used looked like this:
>
> #    print "Creating
> graph\n";
>     RRDs::graph
> ("$png_path/$k.png",
>
>     "--title=$TITLE $k",
>
>     "--vertical-label=$VLABEL",
>
> "--color=$BACK",
>
> "--color=$SHADEA",
>
> "--color=$SHADEB",
>
> "--color=$FONT",
>
> "--color=$CANVAS",
>
> "--color=$GRID",
>
> "--color=$MGRID",
>
> "--color=$FRAME",
>
> "--color=$ARROW",
>
>     "--base=$BASE",
>
>
> "DEF:avg=$rrd_path/$k.rrd:$ds:AVERAGE",
>
>
> "DEF:pred=$rrd_path/$k.rrd:$ds:HWPREDICT",
>
>
> "DEF:dev=$rrd_path/$k.rrd:$ds:DEVPREDICT",
>
>
> "DEF:fail=$rrd_path/$k.rrd:$ds:FAILURES",
>         "COMMENT:
> \\n",
>
>      "CDEF:mbs=avg,1048576,/",
>
> "LINE2:$AVG_LINE:Average MB/s",
>
> "GPRINT:mbs:AVERAGE:\\: %5.2lf",
>
> "GPRINT:mbs:LAST: Last\\:
> %5.2lf\\n",
>
> "TICK:$TICK:1.0:Failures",
>
> "CDEF:upper=pred,dev,2,*,+",
>
> "CDEF:lower=pred,dev,2,*,-",
>
> "LINE1:$UPPER_LINE:Upper Bound",
>
> "LINE1:$LOWER_LINE:Lower Bound",
>
> "\\n",
>
> "COMMENT:$date",
>         );
>     $err=RRDs::error;
>     if ($err) {print
> "problem generating the graph: $err\n";}
>
>
> with
> variables defined like this:
> NOTE: $k for me was pulled from a reference I generated,
> you should be able to set it to your RRD without any
> issues.
>
>
> #--------------#
> # RRDTool vars #
> #--------------#
> my $png_path = "/var/www/html/";
> my $TITLE = "IO Test:";
> my $VLABEL = "Bytes per second (B/s)";
> my $BACK = "BACK#000000";
> my $SHADEA = "SHADEA#FFFFFF";
> my $SHADEB = "SHADEB#FFFFFF";
> my $FONT = "FONT#DDDDDD";
> my $CANVAS = "CANVAS#202020";
> my $GRID = "GRID#666666";
> my $MGRID = "MGRID#AAAAAA";
> my $FRAME = "FRAME#202020";
> my $ARROW = "ARROW#FFFFFF";
> my $BASE = 1024;
> my $AVG_LINE = "AVG#0000FF";
> my $TICK = "FAIL#FFFFA0";
> my $UPPER_LINE = "UPPER#ff0000";
> my $LOWER_LINE = "LOWER#ff0000";
>
>
> -Chris
>
> --- On Tue, 11/3/09, Mark Woodruff <n3hf@...>
> wrote:
>
> > From: Mark Woodruff <n3hf@...>
> > Subject: [rrd-users] RRD Newbee needs help with RRD
> Perl script
> > To: rrd-users@...
> > Date: Tuesday, November 3, 2009, 5:03 PM
> > Recently installed Version 1.3.8
> > and have been trying to make a Perl script wrritten by
> Brian
> > Lane (Digitemp) from what I have been able to
> determine the
> > scripts hangs up on the line containing:
> >
> > $answer=RRDp::read;
> >
> > # Output a HTML header for the PNG
> > image to follow
> >
> > print $cgi->header('image/png');
> > # Generate the graph
> > RRDp::cmd "graphv - --imgformat PNG",
> > "--start '$starttime' --end
> > '$endtime'",
> > "--width $width --height $height",
> >
> "DEF:temp_c=$rrd:$var:AVERAGE",
> > "CDEF:temp_f=temp_c,9,*,5,/,32,+",
> > "LINE1:temp_f$color:'$label'";
> > $answer=RRDp::read;
> > print $$answer;
> > RRDp::end;
> >
> > After reading rrd tutiorial I wrote a
> > shorten bash script which works fine which tells
> me my
> > RRD datafile is fine. Is there a bug and/or do I have
> > installation issue??
> >
> > Mark
> >
> >
> >
> > -----Inline Attachment Follows-----
> >
> > _______________________________________________
> > rrd-users mailing list
> > rrd-users@...
> > https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
> >
>
>
>
>
>
>
>

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: RRD Newbee needs help with RRD Perl script

2009-11-04T10:52:37Z

Chris, Thank you for the feedback. I tried rewriting something with RRDs but no success, something must be missing from the installation (I think!).

Can't locate loadable object for module RRDs in @INC (@INC contains: /usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.

.5 /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/ve

dor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl .) at ./temp-one.cgi line 27

Compilation failed in require at ./temp-one.cgi line 27.

Mark

From: Koaps <koaps@...>
To: Mark Woodruff <n3hf@...>
Sent: Tue, November 3, 2009 8:42:04 PM
Subject: Re: [rrd-users] RRD Newbee needs help with RRD Perl script

I have no idea about RRDp but I have used RRDs with no issues in perl scripts.

The graph subroutine I used looked like this:

#    print "Creating graph\n";
    RRDs::graph ("$png_path/$k.png",
    "--title=$TITLE $k",
    "--vertical-label=$VLABEL",
        "--color=$BACK",
        "--color=$SHADEA",
        "--color=$SHADEB",
        "--color=$FONT",
        "--color=$CANVAS",
        "--color=$GRID",
        "--color=$MGRID",
        "--color=$FRAME",
        "--color=$ARROW",
    "--base=$BASE",
    "DEF:avg=$rrd_path/$k.rrd:$ds:AVERAGE",
    "DEF:pred=$rrd_path/$k.rrd:$ds:HWPREDICT",
    "DEF:dev=$rrd_path/$k.rrd:$ds:DEVPREDICT",
    "DEF:fail=$rrd_path/$k.rrd:$ds:FAILURES",
        "COMMENT: \\n",
        "CDEF:mbs=avg,1048576,/",
        "LINE2:$AVG_LINE:Average MB/s",
        "GPRINT:mbs:AVERAGE:\\: %5.2lf",
        "GPRINT:mbs:LAST: Last\\: %5.2lf\\n",
        "TICK:$TICK:1.0:Failures",
        "CDEF:upper=pred,dev,2,*,+",
        "CDEF:lower=pred,dev,2,*,-",
        "LINE1:$UPPER_LINE:Upper Bound",
        "LINE1:$LOWER_LINE:Lower Bound",
        "\\n",
        "COMMENT:$date",
        );
    $err=RRDs::error;
    if ($err) {print "problem generating the graph: $err\n";}

with variables defined like this:
NOTE: $k for me was pulled from a reference I generated, you should be able to set it to your RRD without any issues.

#--------------#
# RRDTool vars #
#--------------#
my $png_path = "/var/www/html/";
my $TITLE = "IO Test:";
my $VLABEL = "Bytes per second (B/s)";
my $BACK = "BACK#000000";
my $SHADEA = "SHADEA#FFFFFF";
my $SHADEB = "SHADEB#FFFFFF";
my $FONT = "FONT#DDDDDD";
my $CANVAS = "CANVAS#202020";
my $GRID = "GRID#666666";
my $MGRID = "MGRID#AAAAAA";
my $FRAME = "FRAME#202020";
my $ARROW = "ARROW#FFFFFF";
my $BASE = 1024;
my $AVG_LINE = "AVG#0000FF";
my $TICK = "FAIL#FFFFA0";
my $UPPER_LINE = "UPPER#ff0000";
my $LOWER_LINE = "LOWER#ff0000";

-Chris

--- On Tue, 11/3/09, Mark Woodruff <n3hf@...> wrote:

> From: Mark Woodruff <n3hf@...>
> Subject: [rrd-users] RRD Newbee needs help with RRD Perl script
> To: rrd-users@...
> Date: Tuesday, November 3, 2009, 5:03 PM
> Recently installed Version 1.3.8
> and have been trying to make a Perl script wrritten by Brian
> Lane (Digitemp) from what I have been able to determine the
> scripts hangs up on the line containing:
>
> $answer=RRDp::read;
>
> # Output a HTML header for the PNG
> image to follow
>
> print $cgi->header('image/png');
> # Generate the graph
> RRDp::cmd "graphv - --imgformat PNG",
> "--start '$starttime' --end
> '$endtime'",
> "--width $width --height $height",
> "DEF:temp_c=$rrd:$var:AVERAGE",
> "CDEF:temp_f=temp_c,9,*,5,/,32,+",
> "LINE1:temp_f$color:'$label'";
> $answer=RRDp::read;
> print $$answer;
> RRDp::end;
>
> After reading rrd tutiorial I wrote a
> shorten bash script which works fine which tells me my
> RRD datafile is fine. Is there a bug and/or do I have
> installation issue??
>
> Mark
>
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> rrd-users mailing list
> rrd-users@...
> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
>

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: Invalid UTF-8 string

2009-11-03T20:21:08Z

Hi Stefan,

Yesterday Stefan M. Brandl wrote:

> Hello,
> just upgrade from rrdtool 1.3.8 to 1.3.9
> and I get
>
> (process:30282): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
>
> when I do a rrdtool graph ...
> And have a ° (degree) sign in the GPRINT line.

this is the kind of error you would get if you were running wit a
locale setting suggesting utf8 encoding and then inputing data
encoded with latin1 for example.

if you are using rrdtool from language bindings, make sure you call
setlocale and are not just setting the environment variable inside
you code.

cheers
tobi

> Stefan
>
> _______________________________________________
> rrd-users mailing list
> rrd-users@...
> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
>
>

--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi@... ++41 62 775 9902 / sb: -9900
_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

RRD Newbee needs help with RRD Perl script

2009-11-03T17:03:23Z

Recently installed Version 1.3.8 and have been trying to make a Perl script wrritten by Brian Lane (Digitemp) from what I have been able to determine the scripts hangs up on the line containing:

$answer=RRDp::read;

# Output a HTML header for the PNG image to follow

print $cgi->header('image/png');

# Generate the graph

RRDp::cmd "graphv - --imgformat PNG",

"--start '$starttime' --end '$endtime'",

"--width $width --height $height",

"DEF:temp_c=$rrd:$var:AVERAGE",

"CDEF:temp_f=temp_c,9,*,5,/,32,+",

"LINE1:temp_f$color:'$label'";

$answer=RRDp::read;

print $$answer;

RRDp::end;

After reading rrd tutiorial I wrote a shorten bash script which works fine which tells me my RRD datafile is fine. Is there a bug and/or do I have installation issue??

Mark

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: Trying to build rrdtool 1.4.1 on RedHat EL4

2009-11-03T11:24:47Z

Ok, I got a working configure now on EL4, I will see to modify the .spec file in a few minutes to see if I can build a rpm from it.

Here is what I have done:

Install from RHEL 4 Updates:

evolution28-cairo-1.2.4-6.el4.i386.rpm
evolution28-cairo-devel-1.2.4-6.el4.i386.rpm
evolution28-glib2-2.12.3-6.el4.i386.rpm
evolution28-glib2-devel-2.12.3-6.el4.i386.rpm
evolution28-pango-1.14.9-11.el4_7.i386.rpm
evolution28-pango-devel-1.14.9-11.el4_7.i386.rpm

Set LDFLAGS:

setenv LDFLAGS -L/usr/evolution28/lib

Set PKG_CONFIG_PATH:

setenv PKG_CONFIG_PATH /usr/evolution28/lib/pkgconfig:/usr/lib/pkgconfig

Run configure:

./configure

This results in an ok run as far I can tell.

Ulf.

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Invalid UTF-8 string

2009-11-03T04:07:35Z

Hello,
just upgrade from rrdtool 1.3.8 to 1.3.9
and I get

(process:30282): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

when I do a rrdtool graph ...
And have a ° (degree) sign in the GPRINT line.

Stefan

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: Trying to build rrdtool 1.4.1 on RedHat EL4

2009-11-02T18:50:30Z

> -----Original Message-----
> From: Tobias Oetiker [mailto:tobi@...]
> Sent: Monday, November 02, 2009 6:47 PM
> To: Ulf Zimmermann
> Cc: William R. Lorenz; rrd-users@...
> Subject: Re: [rrd-users] Trying to build rrdtool 1.4.1 on RedHat EL4
>
> Just wondering,
>
> Yesterday Ulf Zimmermann wrote:
> >
> > I wished it were so easy ... I got about 250 or so EL4 machines
> > and upgrading them aint gonna happen any time soon.
> >
> > I was mainly looking at rrdtool 1.4.1 because of rrdcached to be
> > used in conjunction with collectd. Currently we have a large
> > number of virtual machines and running collectd inside of those,
> > each has about 75KB/sec writing due to writing to rrd files.
>
> have you tried compiling everything according to the build
> instructions ? of you creaded a tar file for a setup that installs
> into /opt, that should not be all that bad.
>
> cheers
> tobi

Trying to build a rpm, because of rolling it out to a number of machines. I need to look at
collectd what it actually needs for rrdcached. Already running into another problem at manual
running configure, which checks glib2 by looking for glib_check_version, which wasn't introduced
until glib 2.6 and EL4 has only 2.4.x.

Would love to upgrade all to EL5, but as said before, it will take a long time and I am trying to
remove the need to write to local files.

>
>
> > >
> > > Hope this helps,
> > >
> > > --
> > > William R. Lorenz
> >
> > _______________________________________________
> > rrd-users mailing list
> > rrd-users@...
> > https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
> >
> >
>
> --
> Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
> http://it.oetiker.ch tobi@... ++41 62 775 9902 / sb: -9900

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User

Re: Trying to build rrdtool 1.4.1 on RedHat EL4

2009-11-02T18:47:18Z

> -----Original Message-----
> From: Tobias Oetiker [mailto:tobi@...]
> Sent: Monday, November 02, 2009 6:45 PM
> To: Ulf Zimmermann
> Cc: rrd-users@...
> Subject: Re: [rrd-users] Trying to build rrdtool 1.4.1 on RedHat EL4
>
> Hi Ulf,
>
> the spec file has not been updated recently ...
>
> you should not need intltool at all and for pango a lower version
> might do as well ... the problem with pango is that the library is
> under heavy development and apart form new featueres there are also
> important bugfixes going in ... if I remember corectly there were
> several memory management issues which were resolved over time (not
> sure which version). In essence the newer the better, but you
> should be able use older versions to, I am not using any
> particularly fancy features of pango ...

I will set the spec file to the lower versions I got and test around with it. I don't actually need the graphing functions for the EL4 systems, just librrd to write to files or rrdcached to send data to a central collecting server. That server is running FreeBSD and had no problems compiling 1.4.1. Any test I have done there so far look good.

>
> cheers
> tobi
>
>
> Yesterday Ulf Zimmermann wrote:
>
> > I am looking at building RRDtool 1.4.1 for our EL4 environment.
> Looking the spec file which was included in the source tar of 1.4.1, it
> has certain requirements:
> >
> > Pango >= 1.14
> > Intltool >= 0.35.0
> >
> > Both these are not provided by RedHat in a recent enough version, nor
> are they available in for example rpmforge. Can anyone point me to the
> exact reasons for requiring the above versions? Would it be possible to
> change the .spec to the lower version, which could cause consequences.
> >
> > Ulf.
> >
> >
>
> --
> Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
> http://it.oetiker.ch tobi@... ++41 62 775 9902 / sb: -9900

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

From forum: RRDTool - User