Bug 1099334
| Summary: | [Nagios] - When smb is killed /stopped, nagios UI does not reflect the staus as critical. | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | RamaKasturi <knarra> |
| Component: | nagios-server-addons | Assignee: | Ramesh N <rnachimu> |
| Status: | CLOSED ERRATA | QA Contact: | RamaKasturi <knarra> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rhgs-3.0 | CC: | dpati, kmayilsa, rhsc-qe-bugs, rnachimu, tjeyasin |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.0.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | nagios-server-addons-0.1.1-2.el6rhs, gluster-nagios-addons-0.1.1-1.el6rhs | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-09-22 19:09:57 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: | 1104574, 1105123 | ||
| Bug Blocks: | |||
|
Description
RamaKasturi
2014-05-20 05:36:48 UTC
is there any volume using smb in that node? If there is no volume or no volume using SMB, it will simply says OK. Fixed in patch http://review.gluster.org/7847 By default, SMB is enabled for all volumes. So even if there is no "user.cifs" or "user.smb" volume option is specified in the volume, we have consider this as SMB enabled. Also if either of the("user.cifs" , "user.smb") values is disabled, it means SMB is disabled.
With this fix and above assumption, whenever SMB is enabled for any volume in the cluster and SMB service is not running, corresponding service in Nagios UI will go to CRITICAL. Whenever SMB process is not running and SMB is not enabled for any of the volume, corresponding service in Nagios UI will be in OK state with message as "OK: No gluster volume uses smb".
Moving this bug back to assigned bcoz when user.smb is set to disabled, smb process start even if it is not started before. Filed a bug for the same. Here is the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1104574 This is bug is about service is not going to CRITICAL when smb is killed/stopped. RHS bug 1104574 is about smb is getting start when user.smb is set to disable. So this bug can still be verified. Verified and works fine with the build "nagios-server-addons-0.1.1-2.el6rhs.x86_64" , gluster-nagios-addons-0.1.1-1.el6rhs.x86_64. As per comment 3, considering smb is enabled for all volumes by default, 1)smb status to "CRITICAL" with status information as "CRITICAL:Process smb is not running", when smb process is not running. 2)smb status shows "OK" with status information as process smb is running", when smb process is up and running. 3)smb status shows "OK" with status information as "OK:No gluster volume uses smb" when smb is disabled and no smb process is not running. 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. http://rhn.redhat.com/errata/RHEA-2014-1277.html |