Description of problem:
When ctdb is configured and functioning proplery, stopping ctdb on one node in the cluster displays ctdb status as 'UNKNOWN' and status information as 'CTDB not Configured'
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install nagios on RHS node.
2. Now setup ctdb.
3. Nagios displays ctdb status as 'OK' and status information as 'Node Status:OK'
4. Now stop ctdb on one node by running 'service ctdb stop'
CTDB service on that node displays status as 'UNKNOWN' and status information as 'CTDB not configured'
CTDB should display the status as 'CRITCAL' with status information as 'ctdb process is not running'
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
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".
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.