Bug 1230194

Summary: NRPE output is getting truncated after 1024 chars
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Kanagaraj <kmayilsa>
Component: nagios-server-addonsAssignee: Shubhendu Tripathi <shtripat>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: asrivast, dpati, knarra, sabose, sankarshan
Target Milestone: ---   
Target Release: RHGS 3.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nrpe-2.15-4.1.el6rhs Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1314419 1314422 1316177 (view as bug list) Environment:
Last Closed: 2015-07-29 05:32:45 UTC Type: Bug
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: 1202842, 1231420, 1231422, 1314419, 1314422, 1316177, 1316180    

Description Kanagaraj 2015-06-10 12:22:15 UTC
Description of problem:
discovery.py is failing with error  'Invalid control character at: line 1 column 1023 (char 1023)'

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create 2 volumes with each 6 bricks
2. Run discovery.py with necessary options


Actual results:
Fails with 'Invalid control character at: line 1 column 1023 (char 1023)'

Expected results:
discovery.py should configure the nagios server to monitor RHGS nodes.

Additional info:
This is happening due to the 1024 char limit in nrpe.

Comment 3 Shubhendu Tripathi 2015-06-12 11:55:36 UTC
Done the scratch build and verified the changes. Works fine.
Will build non-scratch.

Comment 4 Shubhendu Tripathi 2015-06-14 10:01:54 UTC
No scratch build available now with fix

Comment 5 RamaKasturi 2015-06-18 07:49:04 UTC
Verified and works fine with nagios-server-addons-0.2.1-2.el6rhs.noarch.

Created two volumes distribtue and distirbute replicate each with 6 bricks and ran configure-gluster-nagios command. Auto discovery script does not fail with this scenario.

Changes :
Hostgroup cluster1 - UPDATE
Host cluster1 - UPDATE
	 Service - Volume Utilization - vol3 -ADD 
	 Service - Volume Split-brain status - vol3 -ADD 
	 Service - Volume Status - vol3 -ADD 
	 Service - Volume Utilization - vol2 -ADD 
	 Service - Volume Status - vol2 -ADD 
Host rhs-client24.lab.eng.blr.redhat.com - UPDATE
	 Service - Brick Utilization - /rhgs/brick5/brick5 -ADD 
	 Service - Brick - /rhgs/brick5/brick5 -ADD 
	 Service - Brick Utilization - /rhgs/brick6/brick6 -ADD 
	 Service - Brick - /rhgs/brick6/brick6 -ADD 
	 Service - Brick Utilization - /rhgs/brick7/brick7 -ADD 
	 Service - Brick - /rhgs/brick7/brick7 -ADD 
	 Service - Brick Utilization - /rhgs/brick2/brick2 -ADD 
	 Service - Brick - /rhgs/brick2/brick2 -ADD 
	 Service - Brick Utilization - /rhgs/brick3/brick3 -ADD 
	 Service - Brick - /rhgs/brick3/brick3 -ADD 
	 Service - Brick Utilization - /rhgs/brick4/brick4 -ADD 
	 Service - Brick - /rhgs/brick4/brick4 -ADD 
Host rhs-client33.lab.eng.blr.redhat.com - UPDATE
	 Service - Brick Utilization - /rhgs/brick5/brick5 -ADD 
	 Service - Brick - /rhgs/brick5/brick5 -ADD 
	 Service - Brick Utilization - /rhgs/brick6/brick6 -ADD 
	 Service - Brick - /rhgs/brick6/brick6 -ADD 
	 Service - Brick Utilization - /rhgs/brick7/brick7 -ADD 
	 Service - Brick - /rhgs/brick7/brick7 -ADD 
	 Service - Brick Utilization - /rhgs/brick2/brick2 -ADD 
	 Service - Brick - /rhgs/brick2/brick2 -ADD 
	 Service - Brick Utilization - /rhgs/brick3/brick3 -ADD 
	 Service - Brick - /rhgs/brick3/brick3 -ADD 
	 Service - Brick Utilization - /rhgs/brick4/brick4 -ADD 
	 Service - Brick - /rhgs/brick4/brick4 -ADD 
Are you sure, you want to commit the changes? (Yes, No) [Yes]: Yes
Cluster configurations synced successfully from host rhs-client24.lab.eng.blr.redhat.com
Do you want to restart Nagios to start monitoring newly discovered entities? (Yes, No) [Yes]: 
Nagios re-started successfully

Comment 6 errata-xmlrpc 2015-07-29 05:32:45 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