Bug 1204314
Summary: | NRPE memory check doesn't factor cached memory | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Kevin Clevenger <kcleveng> |
Component: | gluster-nagios-addons | Assignee: | Darshan <dnarayan> |
Status: | CLOSED ERRATA | QA Contact: | RamaKasturi <knarra> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | rhgs-3.0 | CC: | annair, asrivast, divya, dnarayan, dpati, kcleveng, knarra, ltrilety, nsathyan, sgraf |
Target Milestone: | --- | ||
Target Release: | RHGS 3.1.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | gluster-nagios-addons-0.2.1-1.el6rhs.x86_64.rpm | Doc Type: | Bug Fix |
Doc Text: |
Previously, the Memory utilization plugin was not deducting cached memory from used memory. This caused Nagios to alert for a low memory condition when none actually exists. With this fix, the used value is obtained by deducting cached value from it. Now, the Memory utilization plugin will return the correct value for used memory and hence there will be no false low memory alerts.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-07-29 05:27:37 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 |
Comment 1
Darshan
2015-03-23 09:24:54 UTC
Fix Patch: http://review.gluster.org/#/c/9977/ Targeted for 3.1.0 release. Verified and works fine with build gluster-nagios-addons-0.2.1-1.el6rhs.x86_64.rpm. with this fix cached memory is also being deducted from the Used space to get the actual used space. Darshan, Could you review the edited doc text and sign-off. (In reply to Divya from comment #10) > Darshan, > > Could you review the edited doc text and sign-off. 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/RHEA-2015-1494.html |