Red Hat Bugzilla – Bug 1231422
[New] - CPU Utilization [pnp4nagios] fails to load the graph for physical machine
Last modified: 2016-03-09 10:19:21 EST
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:
Created attachment 1038237 [details] Attaching the screenshot for cpu utilization on physicalmachine.
Did u try immediately after running configure-gluster-nagios?. What is the OS version, selinux status, pnp4nagios version?.
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
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.
Fixed size issue with nrpe and that resolves this issue.
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.
Created attachment 1040497 [details] Attaching the cpu utilization after the fix
Shubhendu, Could you review and sign-off the edited doc text.
doc-text looks fine
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