Red Hat Bugzilla – Bug 1451997
[RHEL-6] Move custom nrpe commands to conf.d folder
Last modified: 2017-09-21 00:52:44 EDT
+++ This bug was initially created as a clone of Bug #1425724 +++ Description of problem: With the rise of configuration management tools, the default nrpe.conf file often times gets overwritten. A simple solution for this is to move our custom nrpe commands in a special configuration file in /etc/nrpe.d/ Version-Release number of selected component (if applicable): RHGS 3.1.3 (version independent) gluster-nagios-addons-0.2.7-1.el7 gluster-nagios-common-0.2.4-1.el7 How reproducible: always Steps to Reproduce: 1. Have a configuration management tool that templates the nrpe.conf file 2. See the custom gluster commands disappear Actual results: Customer Gluster commands are inaccessible breaking monitoring Expected results: Gluster commands are still reachable Additional info: Please :) --- Additional comment from Sahina Bose on 2017-05-17 04:09:46 EDT --- Patch https://review.gluster.org/#/c/17306 posted to address this. Moved the gluster nrpe commands to /etc/nrpe.d/glusternrpe.cfg
Verified this bz with gluster-nagios-addons-0.2.9-1.el6rhs.x86_64 and glusterfs-3.8.4-26.el6rhs.x86_64. The section related to gluster in /etc/nagios/nrpe.cfg is moved to /etc/nrpe.d/glusternrpe.cfg. There is no impact on the configured nagios functionality, when tried with fresh install or upgrade. Moving the BZ to verified in 3.3. Related logs are pasted below: [root@dhcp37-44 nagios]# [root@dhcp37-44 nagios]# gluster pool list UUID Hostname State d1c1fb6c-a7e4-4498-aea4-aa5ec4130cac dhcp37-127.lab.eng.blr.redhat.com Connected 4f3cea73-379d-4036-bd57-541ad087ccf8 dhcp37-91.lab.eng.blr.redhat.com Connected 01dde995-e611-4dcc-b88f-ee8ca297ecc5 dhcp37-118.lab.eng.blr.redhat.com Connected 2cce6af6-617e-49b4-8194-2493692cd866 dhcp37-124.lab.eng.blr.redhat.com Connected 35325849-ce70-48d8-853b-a2d0bfefe50c dhcp37-89.lab.eng.blr.redhat.com Connected c11413e0-7dec-4300-b17f-0a325327038e localhost Connected [root@dhcp37-44 nagios]# rpm -qa | grep gluster gluster-nagios-common-0.2.4-1.el6rhs.noarch glusterfs-3.8.4-26.el6rhs.x86_64 glusterfs-fuse-3.8.4-26.el6rhs.x86_64 glusterfs-geo-replication-3.8.4-26.el6rhs.x86_64 vdsm-gluster-4.16.30-1.5.el6rhs.noarch glusterfs-libs-3.8.4-26.el6rhs.x86_64 glusterfs-api-3.8.4-26.el6rhs.x86_64 gluster-nagios-addons-0.2.9-1.el6rhs.x86_64 glusterfs-server-3.8.4-26.el6rhs.x86_64 python-gluster-3.8.4-26.el6rhs.noarch glusterfs-client-xlators-3.8.4-26.el6rhs.x86_64 glusterfs-cli-3.8.4-26.el6rhs.x86_64 glusterfs-rdma-3.8.4-26.el6rhs.x86_64 [root@dhcp37-44 nagios]# [root@dhcp37-44 nagios]# rpm -qa | grep nagios gluster-nagios-common-0.2.4-1.el6rhs.noarch nagios-plugins-dummy-1.4.16-12.el6rhs.x86_64 nagios-plugins-ide_smart-1.4.16-12.el6rhs.x86_64 nagios-plugins-1.4.16-12.el6rhs.x86_64 nagios-plugins-procs-1.4.16-12.el6rhs.x86_64 nagios-3.5.1-9.el6.x86_64 nagios-plugins-nrpe-2.15-4.2.el6rhs.x86_64 nagios-plugins-ping-1.4.16-12.el6rhs.x86_64 pnp4nagios-0.6.22-2.1.el6rhs.x86_64 gluster-nagios-addons-0.2.9-1.el6rhs.x86_64 nagios-common-3.5.1-9.el6.x86_64 nagios-server-addons-0.2.6-1.el6rhs.noarch [root@dhcp37-44 nagios]# [root@dhcp37-44 nagios]# [root@dhcp37-44 nagios]# nagios -v /etc/nagios/nagios.cfg Nagios Core 3.5.1 Copyright (c) 2009-2011 Nagios Core Development Team and Community Contributors Copyright (c) 1999-2009 Ethan Galstad Last Modified: 08-30-2013 License: GPL Website: http://www.nagios.org Reading configuration data... Read main config file okay... Processing object config file '/etc/nagios/objects/commands.cfg'... Processing object config file '/etc/nagios/objects/contacts.cfg'... Processing object config file '/etc/nagios/objects/timeperiods.cfg'... Processing object config file '/etc/nagios/objects/templates.cfg'... .. .. .. Checking misc settings... Total Warnings: 37 Total Errors: 0 Things look okay - No serious problems were detected during the pre-flight check [root@dhcp37-44 nagios]# [root@dhcp37-44 nagios]# grep "gluster" /etc/nagios/nrpe.cfg [root@dhcp37-44 nagios]# [root@dhcp37-44 nagios]# ll /etc/nrpe.d/glusternrpe.cfg -rw-r--r--. 1 root root 1657 May 18 20:29 /etc/nrpe.d/glusternrpe.cfg [root@dhcp37-44 nagios]# [root@dhcp37-44 nagios]# cat /etc/nrpe.d/glusternrpe.cfg command[check_disk_and_inode]=sudo /usr/lib64/nagios/plugins/gluster/check_mounts.py -w 80 -c 90 -i / -i /boot -i /home -i /var -i /usr command[check_memory]=/usr/lib64/nagios/plugins/gluster/memory.py -w 80 -c 90 -t 2 command[check_swap_usage]=/usr/lib64/nagios/plugins/gluster/swap.py -w 80 -c 90 -t 2 command[check_cpu_multicore]=/usr/lib64/nagios/plugins/gluster/cpu.py -w 80 -c 90 -t 2 command[check_interfaces]=/usr/lib64/nagios/plugins/gluster/network.py -e lo -e ';vdsmdummy;' -t 2 command[check_brick_usage]=sudo /usr/lib64/nagios/plugins/gluster/check_mounts.py -w 80 -c 90 -i \$ARG1\$ command[check_vol_utilization]=sudo /usr/lib64/nagios/plugins/gluster/check_vol_utilization.py \$ARG1\$ -w \$ARG2\$ -c \$ARG3\$ command[check_vol_status]=sudo /usr/lib64/nagios/plugins/gluster/check_volume_status.py -v \$ARG1\$ -t \$ARG2\$ command[check_proc_status]=sudo /usr/lib64/nagios/plugins/gluster/check_gluster_proc_status.py -t \$ARG1\$ command[check_brick_status]=sudo /usr/lib64/nagios/plugins/gluster/check_gluster_proc_status.py -t BRICK -v \$ARG1\$ -b \$ARG2\$ command[discoverpeers]=sudo /usr/lib64/nagios/plugins/gluster/discoverpeers.py command[discover_volume_list]=sudo /usr/lib64/nagios/plugins/gluster/discover_volumes.py -l command[discover_volume_info]=sudo /usr/lib64/nagios/plugins/gluster/discover_volumes.py -v \$ARG1\$ command[discoverhostparams]=sudo /usr/lib64/nagios/plugins/gluster/discoverhostparams.py command[configure_gluster_node]=sudo /usr/lib64/nagios/plugins/gluster/configure_gluster_node.py -c \$ARG1\$ -n \$ARG2\$ -H \$ARG3\$ command[check_quorum_status]=sudo /usr/lib64/nagios/plugins/gluster/check_quorum_status.py [root@dhcp37-44 nagios]#
Minor changes in Doc Text based on Peer Review.
Doc text changed: NERP -> NRPE
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://access.redhat.com/errata/RHBA-2017:2782