Bug 1177129
| Summary: | [New] - glusterd service in nagios is not marked critical when glusterd is hung on the node | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | RamaKasturi <knarra> | ||||||
| Component: | nagios-server-addons | Assignee: | Sahina Bose <sabose> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | RamaKasturi <knarra> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | rhgs-3.1 | CC: | divya, dpati, sabose, tjeyasin | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | RHGS 3.1.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | nagios-server-addons-0.2.1-3.el7rhgs, nagios-server-addons-0.2.1-2.el6rhs | Doc Type: | Bug Fix | ||||||
| Doc Text: |
Previously, the Nagios plugin monitored if glusterd process is present. As a consequence, the Plugin returned OK status even if the glusterd process is dead but the pid file existed. With this fix, the plugin is updated to monitor glusterd service state and the glusterd service status is now reflected correctly.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-07-29 05:27:18 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 | ||||||||
| Attachments: |
|
||||||||
|
Description
RamaKasturi
2014-12-24 10:22:34 UTC
Attaching the sos reports link http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1177129/ Patch sent to master: http://review.gluster.org/10246 Can you please put FIV for this bug? Moving this bug back because when glusterd is stopped on the node or when glusterd is dead put pid file exists, then the status of glusterd is moving to UNKNOWN, but glusterd should be marked critical. Created attachment 1033250 [details]
Screenshot when glusterd is stopped
Created attachment 1033251 [details]
Screenshot when glusterd dead but pid file exists
Ignore comment 7. Moving this bug back because when glusterd is stopped on the node service status moves to UNKNOWN with status information "glusterd is stopped". When glusterd is killed on the node using kill -9 <glusterpid> service status is shown as WARNING with status information as "gluster dead but pid file exists". In both the above cases glusterd should be marked critical. Posted patch http://review.gluster.org/11161 to correct this Verified and works fine with build nagios-server-addons-0.2.1-2.el6rhs.noarch. When glusterd is stopped on the node, status of gluster Management is marked as critical with status information "Process glusterd is not running". When glusterd is killed on the node using kill -9 <glusterpid> service status is shown as WARNING with status information as "gluster dead but pid file exists". Ignore comment 12. Verified and works fine with build nagios-server-addons-0.2.1-2.el6rhs.noarch. When glusterd is stopped on the node, status of gluster Management is marked as CRITICAL with status information "Process glusterd is not running". When glusterd is killed on the node using kill -9 <glusterpid> service status is shown as CRITICAL with status information as "gluster dead but pid file exists". Sahina, Please review and sign-off the edited doc text. acked 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 |