Bug 1119273
| Summary: | [Nagios] - When CTDB is configured and functioning, stopping ctdb service on a node displays the status of ctdb service as 'UNKNOWN' and status Information as 'CTDB not Configured | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | RamaKasturi <knarra> |
| Component: | nagios-server-addons | Assignee: | Timothy Asir <tjeyasin> |
| Status: | CLOSED ERRATA | QA Contact: | RamaKasturi <knarra> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | rhgs-3.0 | CC: | asrivast, divya, dpati, lmohanty, rhsc-qe-bugs, rtalur, sabose, sbhaloth, ssampat, tjeyasin, vagarwal |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | nagios-server-addons-0.2.0-1.el6rhs.noarch | Doc Type: | Bug Fix |
| Doc Text: |
Previously, when CTDB was configured and functioning, stopping ctdb service on a node displayed the status of ctdb service as 'UNKNOWN' and the status information was displayed as 'CTDB not Configured' instead of showing a proper critical error message. Due to this wrong error message, user might think that the CTDB is not configured. With this fix, this issue is resolved and correct error messages are displayed.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-07-29 05:26:35 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 | ||
|
Description
RamaKasturi
2014-07-14 12:01:15 UTC
The plugin returns UNKNOWN as it does not find a ctdb service running. There should be reliable way to know if ctdb is required to be running on the node and not running - in which case it can be marked as CRITICAL. Is there some way to know if ctdb is required on the node? One way of determining if ctdb is supposed to be running is by checking chkconfig ctdb If the output shows that ctdb chkconfig is on, it is fairly sure that ctdb is supposed to be running, but currently it is not. I remember having conversation with Timothy about this. There were other associated cases too and he must have more info on it. CTDB will be considered as configured only if the chkconfig status is on. This may be a limitation now, but currently there is no specific tool or something available to check the configuration. Currently the plugin will not proceed validation and will immediately returns "CTDB not configured" with Unknown status when there is no ctdbd process is running. But, it should also consider the ctdb chkconfig status to reach out the possible state. I hope the following validations can be added to improve the plugin's CTDB status find. if any process.CTDB is not running and ctdb chkconfig status is on: then return "CTDB stopped", appropriate status code (OK). if any process.CTDB is not running and ctdb chkconfig status is off: then return "CTDB not configured", Unknown Patch sent to upstream: http://review.gluster.org/#/c/9124/ please put the FIV for the bug. Verified and works fine with build nagios-server-addons-0.2.0-1.el6rhs.noarch. When CTDB is not configured, CTDB service will be created and it will be shown with status as UNKNOWN with status information as "CTDB not configured" When CTDB is stopped and chkconfig CTDB is on , CTDB status is shown as "CRITICAL" with status information as "CTDB process is not running". When CTDB is on and chkconfig CTDB is on, CTDB status is shown as "RUNNING" with status information "CTDB process is running". Tim, Please review and sign-off the edited doc text. 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 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |