Bug 1231422 - [New] - CPU Utilization [pnp4nagios] fails to load the graph for physical machine
Summary: [New] - CPU Utilization [pnp4nagios] fails to load the graph for physical mac...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-nagios-addons
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHGS 3.1.0
Assignee: Shubhendu Tripathi
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On: 1230194 1314419 1314422 1316177 1316180
Blocks: 1202842
TreeView+ depends on / blocked
 
Reported: 2015-06-13 07:04 UTC by RamaKasturi
Modified: 2016-03-09 15:19 UTC (History)
3 users (show)

Fixed In Version: nrpe-2.15-4.1.el6rhs
Doc Type: Bug Fix
Doc Text:
Previously, due to an issue in the package nrpe, the data got truncated while transferring and there was an invalid data available in the rrd database. This caused failures in pnp4nagios charts display. With this fix, the pnp4nagios charts work properly as the entire data gets transferred from nrpe server.
Clone Of:
Environment:
Last Closed: 2015-07-29 05:33:26 UTC
Embargoed:


Attachments (Terms of Use)
Attaching the screenshot for cpu utilization on physicalmachine. (87.72 KB, image/png)
2015-06-13 07:08 UTC, RamaKasturi
no flags Details
Attaching the cpu utilization after the fix (270.81 KB, image/png)
2015-06-18 13:47 UTC, RamaKasturi
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:1494 0 normal SHIPPED_LIVE Red Hat Gluster Storage Console 3.1 Enhancement and bug fixes 2015-07-29 09:24:02 UTC

Description RamaKasturi 2015-06-13 07:04:41 UTC
Description of problem:
When a physical machine is added to nagios for monitoring pnp4 nagios fails to load the graph

Version-Release number of selected component (if applicable):
gluster-nagios-addons-0.2.2-1.el7rhgs.x86_64

How reproducible:
Alway.

Steps to Reproduce:
1. Add a physical machine to console.
2. Now run configure-gluster-nagios command to monitor the nodes.
3. Click on cpu utilization graph

Actual results:
PNP4 nagios fails to load the graph for physical machine.

Expected results:
PNP4 nagios should not fail to load the graph for physical machine.

Additional info:

Comment 2 RamaKasturi 2015-06-13 07:08:28 UTC
Created attachment 1038237 [details]
Attaching the screenshot for cpu utilization on physicalmachine.

Comment 4 Ramesh N 2015-06-13 07:17:02 UTC
Did u try immediately after running configure-gluster-nagios?. What is the OS version, selinux status, pnp4nagios version?.

Comment 5 RamaKasturi 2015-06-13 07:35:27 UTC
No,  I am able to see all other graphs and cpu utilization graph for virtual machines works fine. Only for physical machine i have the issue.

selinux status - Enforcing
Os version - RHEL7 and RHEL6.7
pnp4nagios - pnp4nagios-0.6.22-2.1.el6rhs.x86_64

Comment 6 Ramesh N 2015-06-13 08:55:50 UTC
I got the root cause. This issue is happening because of the NRPE issue reported in bz#1230194. NRPE output is getting truncated after 1023 characters. As a result , CPU utilization details are not returned completely and it corrupts the rrd file. It will be automatically fixed as part of the dependent bug bz#1230194.

Comment 8 Shubhendu Tripathi 2015-06-15 12:55:47 UTC
Fixed size issue with nrpe and that resolves this issue.

Comment 9 RamaKasturi 2015-06-18 13:24:47 UTC
Verified and works fine with nrpe-2.15-4.1.el6rhs.x86_64.

CPU Utilization graph loads successfully when physical machine is added to monitor node through nagios.

Comment 10 RamaKasturi 2015-06-18 13:47:31 UTC
Created attachment 1040497 [details]
Attaching the cpu utilization after the fix

Comment 11 Divya 2015-07-26 11:57:20 UTC
Shubhendu,

Could you review and sign-off the edited doc text.

Comment 12 Shubhendu Tripathi 2015-07-27 04:41:07 UTC
doc-text looks fine

Comment 13 errata-xmlrpc 2015-07-29 05:33:26 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.

https://rhn.redhat.com/errata/RHEA-2015-1494.html


Note You need to log in before you can comment on or make changes to this bug.