Red Hat Bugzilla – Bug 1138943
[Nagios] - Discovery.py does not check for the correctness of nagios configuration before restarting nagios service
Last modified: 2015-05-13 13:43:16 EDT
Description of problem: Discovery.py does not check for the correctness of email and snmp config files and says "nagios restarted sucessfully" where as nagios would not have restarted sucessfully. Version-Release number of selected component (if applicable): How reproducible: nagios-server-addons-0.1.5-1.el6rhs.noarch Steps to Reproduce: 1. Install nagios on a rhel machine. 2. Configure nagios on RHS nodes. 3. Now add some contact in gluster-templates.cfg which does not exist. Actual results: When discovery.py is run, script says nagios sucessfully restarted, where as nagios is stopped. Expected results: When discovery.py is run, script should check the correctness of all config the files which is used by nagios. Additional info:
We can run 'nagios -v /etc/nagios/nagios.cfg' to check the correctness of the nagios configuration before restarting the Nagios. Upstream patch http://review.gluster.org/#/c/8131/ will address this use case.
Fixed in upstream patch http://review.gluster.org/#/c/8131/.
Please review and sign-off edited doc text.
The discovery.py script does not check the correctness of the nagios configuration (syntax check).So nagios restart may fail if there is some config error in the nagios configuration. Its not specific to email configuration, but for the any nagois configuration. Note: I don't think accuracy is the right word here. We cann't verify the accuracy like verifying the correctness of email address by sending mail.
From kanagaraj, i understand that these bugs have been moved to on_qa by errata. Since QE has not yet received the build i am moving this bug back to assigned state. Please move it on to on_qa once builds are attached to errata.
Verified and works fine with build nagios-server-addons-0.1.8-1.el6rhs.noarch When discovery.py is run and when email and snmp configs are not proper it says "CONFIG ERROR ! Check your Nagios configuration".
Hi Ramesh, Can you please review the edited doc text for technical accuracy and sign off?
Doc text looks good to me
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/RHBA-2015-0039.html