Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 436662

Summary: Override of kMG option causes graph overlap.
Product: Red Hat Enterprise Linux 5 Reporter: Ray Van Dolson <rayvd>
Component: mrtgAssignee: Vitezslav Crhonek <vcrhonek>
Status: CLOSED ERRATA QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: high Docs Contact:
Priority: high    
Version: 5.1CC: cward, dkutalek, psplicha, rvandolson, rvokal
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: mrtg-2.14.5-4.el5 Doc Type: Bug Fix
Doc Text:
Previously, changing the "kMG" keyword in the MRTG configuration could cause the labels on the y-axis to overlap the main area of the generated chart. With this update, an upstream patch has been applied to address this issue, and changing the "kMG" keyword in the configuration no longer leads to the incorrect rendering of the resulting charts.
Story Points: ---
Clone Of:
: 707188 (view as bug list) Environment:
Last Closed: 2011-11-29 10:18:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 499522, 707188    
Attachments:
Description Flags
Demonstrates issue.
none
Patch to fix kMG overlap issue. none

Description Ray Van Dolson 2008-03-08 21:31:15 UTC
mrtg-2.14.5-2

Using the following in a graph configuration:

kMG[aggregate]: ,k,M,G,T,P

Results in the kMG values being displayed in the Y-legend incorrectly
overlapping with the graph area. Per this post:

https://lists.oetiker.ch/pipermail/mrtg/2007-April/032543.html

This appears to have been fixed in 2.15.  Would it be possible to either upgrade
to a later version or backport this fix?

Will attach image demonstrating issue.

Comment 1 Ray Van Dolson 2008-03-08 21:31:15 UTC
Created attachment 297328 [details]
Demonstrates issue.

Comment 2 Ray Van Dolson 2008-03-08 22:02:16 UTC
The following appears to fix the issue:

http://oss.oetiker.ch/mrtg-trac/changeset/112?format=diff&new=112

Comment 3 Ray Van Dolson 2008-03-08 22:03:30 UTC
Created attachment 297334 [details]
Patch to fix kMG overlap issue.

Comment 4 Ray Van Dolson 2008-03-08 22:08:55 UTC
SRPM and .spec file are here for anyone looking for a quick and obviously
unofficial fix:

http://www.bludgeon.org/~rayvd/rpms/mrtg/

Comment 5 Ray Van Dolson 2008-08-09 05:11:20 UTC
Opened SR #1849120 for this issue.

Comment 6 RHEL Program Management 2009-03-26 17:01:09 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 13 Jaromir Hradilek 2011-04-04 15:13:13 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, changing the "kMG" keyword in the MRTG configuration could cause the labels on the y-axis to overlap the main area of the generated chart. With this update, an upstream patch has been applied to address this issue, and changing the "kMG" keyword in the configuration no longer leads to the incorrect rendering of the resulting charts.

Comment 23 errata-xmlrpc 2011-11-29 10:18:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1493.html