Maximum value incorrect on additive graphs

Post general support questions here that do not specifically fall into the Linux or Windows categories.

Moderators: Developers, Moderators

ashke
Posts: 32
Joined: Wed Feb 06, 2008 10:52 am

Maximum value incorrect on additive graphs

Post by ashke »

I just upgraded from 0.8.6j to 0.8.7b and a few of my graphs no longer function the same.

Whenever I add a data source to a graph to get a total, the Maximum on the Legend only displays the value for the data source the Legend was created under. The Current and Average value seem to be correct.

http://ashkie.shackspace.com/cactiold.JPG
http://ashkie.shackspace.com/cactinew.JPG

The dip in the new graph is when I moved the RRDs over but similar graphs with no dips are behaving exactly the same. I've tried re-creating a graph a similar way and it no longer functions the same. Basically I just want to take mutiple data sources and represent them as 1 single data source on a graph. I know about the aggregate plugin but I'm not sure why this is no longer working.


Cacti Version - 0.8.7b
Plugin Architecture - 2.0
Poller Type - CMD.php
Server Info - Linux 2.6.18-53.el5
Web Server - Apache/2.2.3 (Red Hat)
PHP - 5.1.6
PHP Extensions - libxml, xml, wddx, tokenizer, sysvshm, sysvsem, sysvmsg, standard, SimpleXML, sockets, SPL, shmop, session, Reflection, pspell, posix, mime_magic, iconv, hash, gmp, gettext, ftp, exif, date, curl, ctype, calendar, bz2, zlib, pcre, openssl, apache2handler, gd, mysql, mysqli, PDO, pdo_mysql, pdo_sqlite
MySQL - 5.0.22
RRDTool - 1.2.26
SNMP - 5.3.1
Plugins
  • Global Plugin Settings (settings - v0.3)
    Create Aggregate Graphs (aggregate - v0.62)
    Device Monitoring (monitor - v0.8.2)
    PHP Network Weathermap (weathermap - v0.941)
    Host Info (hostinfo - v0.2)
    SuperLinks (superlinks - v0.72)
    Thresholds (thold - v0.3.9)
User avatar
BSOD2600
Cacti Moderator
Posts: 12171
Joined: Sat May 08, 2004 12:44 pm
Location: USA

Post by BSOD2600 »

If possible, please post the graph debug output (graph management -> enable graph debugging) for the old and new graphs.
ashke
Posts: 32
Joined: Wed Feb 06, 2008 10:52 am

Post by ashke »

NEW: http://ashkie.shackspace.com/debugnew.txt

OLD: http://ashkie.shackspace.com/debugold.txt

It appears the NEW version of the command has 3 new variable with MAX in them. I'm seeing similar behavior in other graphs that are broken in this fashion.
Last edited by ashke on Thu Apr 17, 2008 12:45 pm, edited 1 time in total.
ashke
Posts: 32
Joined: Wed Feb 06, 2008 10:52 am

Post by ashke »

Also the new version has the following which are not in the old version:

Code: Select all

CDEF:cdefd=TIME,1204152344,GT,b,b,UN,0,b,IF,IF,TIME,1204152344,GT,c,c,UN,0,c,IF,IF,+,8,* \ 
CDEF:cdefbg=TIME,1204152344,GT,bd,bd,UN,0,bd,IF,IF,8,* \ 
ashke
Posts: 32
Joined: Wed Feb 06, 2008 10:52 am

Post by ashke »

Is there any other information needed to figure out what borked here?
User avatar
BSOD2600
Cacti Moderator
Posts: 12171
Joined: Sat May 08, 2004 12:44 pm
Location: USA

Post by BSOD2600 »

Just a guess, try switching rrdtool to 1.2.26 or the 1.3 beta. I recently solved a problem with large graphs breaking after 0.8.7b. Turns out the older rrdtool 1.2.15 I was using had issues and upgrading to 1.2.26.

Otherwise, going to need a dev to figure out why the new graph format doesn't work. Could post your question (with old/new graph outputs) on the rrdtool mailing list too.
ashke
Posts: 32
Joined: Wed Feb 06, 2008 10:52 am

Post by ashke »

BSOD2600 wrote:Just a guess, try switching rrdtool to 1.2.26 or the 1.3 beta. I recently solved a problem with large graphs breaking after 0.8.7b. Turns out the older rrdtool 1.2.15 I was using had issues and upgrading to 1.2.26.

Otherwise, going to need a dev to figure out why the new graph format doesn't work. Could post your question (with old/new graph outputs) on the rrdtool mailing list too.
Hmm, it seems the old box was running RRDtool 1.2.23 and the new box RRDtool 1.2.26. Perhaps something screwed up between those 2 releases.
ashke
Posts: 32
Joined: Wed Feb 06, 2008 10:52 am

Post by ashke »

I have tried to seek help from the RRD community as well as downgraded my RRDTool back to what was working on the original install (1.2.23) and the behavior still occurs.

Right now, I'm leaning towards it being a bug in this version of Cacti.
ashke
Posts: 32
Joined: Wed Feb 06, 2008 10:52 am

Post by ashke »

Another user had the same issue that he corrected with downgrading from 0.8.7b. Is there anyway to fix this without a downgrade?

http://forums.cacti.net/viewtopic.php?p=129432
ashke
Posts: 32
Joined: Wed Feb 06, 2008 10:52 am

Post by ashke »

I'm still looking for a resolution to this post. I have no clue why the MAX values on my additive AREA graphs are incorrect. Please advise on how I'm supposed to fix this issue.
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Post by gandalf »

The graph DEBUG shows, that you have DEFs for data source with cf=AVERAGE and those with cf=MAX. When using "SIMILAR_DATA_SOURCES_NODUPS" or the like, AVERAGE and MAX will be considered not to be SIMILAR.
Reinhard
ashke
Posts: 32
Joined: Wed Feb 06, 2008 10:52 am

Post by ashke »

gandalf wrote:The graph DEBUG shows, that you have DEFs for data source with cf=AVERAGE and those with cf=MAX. When using "SIMILAR_DATA_SOURCES_NODUPS" or the like, AVERAGE and MAX will be considered not to be SIMILAR.
Reinhard
Thats just the thing, nothing changed in the config from 0.86j to 0.87b. I'm aware that the debug now shows MAX where my old install did not. The question is, how do I get rid of them? The graphs are built exactly the same as they were in 0.86j and they worked fine. You can see from the screenshot that they are all CF=AVERAGE except for the initial LEGEND.
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Post by gandalf »

It would be easier if the linked data was posted inline.
Let's take e.g.
LINE3:cdefbd#00FF00FF:"Outbound" \
It refers to cf=MAX, outbound. Since there is only a single MAX outbound DEF, the sum over all MAX outbound's equals this single one. If you'd like to see the sum of AVERAGE outbound's, simply visit that graph item and change cf from MAX to AVERAGE
Reinhard
ashke
Posts: 32
Joined: Wed Feb 06, 2008 10:52 am

Post by ashke »

gandalf wrote:It would be easier if the linked data was posted inline.
Let's take e.g.
LINE3:cdefbd#00FF00FF:"Outbound" \
It refers to cf=MAX, outbound. Since there is only a single MAX outbound DEF, the sum over all MAX outbound's equals this single one. If you'd like to see the sum of AVERAGE outbound's, simply visit that graph item and change cf from MAX to AVERAGE
Reinhard
Well I changed the MAX to AVG but it had no effect. The Maxiumum is still incorrect in the graphs and the debug looks the same. There is a hidden MAX somewhere in here that gets created using 0.8.7b using this graph type.


http://ashkie.shackspace.com/graphnew2.JPG
http://ashkie.shackspace.com/debugnew2.txt
ashke
Posts: 32
Joined: Wed Feb 06, 2008 10:52 am

Post by ashke »

Bump.
Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests