Description of problem: ------------------------- Currently the disk utilization service monitors all mounted partitions on the RHS node being monitored by nagios. The disks that are used as bricks are monitored also by the brick utilization service. So it would be a good idea not to monitor these disks using the disk utilization service in addition to the brick utilization service. Version-Release number of selected component (if applicable): -------------------------------------------------------------- gluster-nagios-addons-0.1.10-2.el6rhs.x86_64 nagios-server-addons-0.1.6-1.el6rhs.noarch How reproducible: Always Steps to Reproduce: 1. Monitor an RHS node using nagios. 2. Observe the brick utilization service and the disk utilization service. Actual results: Disks that are being used as bricks are monitored both using the brick utilization service as well as the disk utilization service. Expected results: Nagios need not monitor disks that are used as bricks using the disk utilization service as they are already monitored using the brick utilization service. Additional info:
This issue causes disk utilization to show older bricks even after a snapshot is restored. Consider a case where there is a volume called "vol1". 1) User takes a snapshot of the volume. 2) Once the snap is taken, the volume has been filled with data so that utilization is reached to 100 percent. 3) Now user restores the volume and the restored volume does not have data in it. 4) Volume utilization, brick utilization goes to zero percent once the restore is performed. 5) Disk utilization still shows as critical.
monitor only the 4 mount points, which are needed for the system operation
Disk utilization service is modified to monitor only the following mount points: / , /boot , /home , /var , /usr.
patch: http://review.gluster.org/#/c/9673/
Verified as fixed in gluster-nagios-addons-0.1.16-1.el6rhs.x86_64 Disk utilization service now monitors the following mount points - /, /boot, /home, /var and /usr Tested for space and inode utilization monitoring for the above partitions.
Please review and sign-off edited doc text.
looks good.
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/RHBA-2015-0681.html