Unable to start monitoring engine in Nagios XI
Posted: Tue Apr 28, 2020 10:09 am
Hi Team,
In our Nagios serer, apply configuration was not working. We stopped Nagios service and tried restarting.
We are unable to start Nagios Monitoring engine.
Please help us on priority.
[root@eu2napu003 var]# service nagios status
Redirecting to /bin/systemctl status nagios.service
● nagios.service - Nagios Core 4.4.5
Loaded: loaded (/usr/lib/systemd/system/nagios.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2020-04-28 15:54:17 BST; 3min 59s ago
Docs: https://www.nagios.org/documentation
Process: 12621 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=1/FAILURE)
Apr 28 15:54:17 eu2napu003 nagios[12621]: Check your configuration file(s) to ensure that they contain valid
Apr 28 15:54:17 eu2napu003 nagios[12621]: directives and data definitions. If you are upgrading from a previous
Apr 28 15:54:17 eu2napu003 nagios[12621]: version of Nagios, you should be aware that some variables/definitions
Apr 28 15:54:17 eu2napu003 nagios[12621]: may have been removed or modified in this version. Make sure to read
Apr 28 15:54:17 eu2napu003 nagios[12621]: the HTML documentation regarding the config files, as well as the
Apr 28 15:54:17 eu2napu003 nagios[12621]: 'Whats New' section to find out what has changed.
Apr 28 15:54:17 eu2napu003 systemd[1]: nagios.service: control process exited, code=exited status=1
Apr 28 15:54:17 eu2napu003 systemd[1]: Failed to start Nagios Core 4.4.5.
Apr 28 15:54:17 eu2napu003 systemd[1]: Unit nagios.service entered failed state.
Apr 28 15:54:17 eu2napu003 systemd[1]: nagios.service failed.
[root@eu2napu003 var]#
Tried to start the service in other way as well.Getting below error:
[root@eu2napu003 var]# systemctl start nagios.service
Job for nagios.service failed because the control process exited with error code. See "systemctl status nagios.service" and "journalctl -xe" for details.
In our Nagios serer, apply configuration was not working. We stopped Nagios service and tried restarting.
We are unable to start Nagios Monitoring engine.
Please help us on priority.
[root@eu2napu003 var]# service nagios status
Redirecting to /bin/systemctl status nagios.service
● nagios.service - Nagios Core 4.4.5
Loaded: loaded (/usr/lib/systemd/system/nagios.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2020-04-28 15:54:17 BST; 3min 59s ago
Docs: https://www.nagios.org/documentation
Process: 12621 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=1/FAILURE)
Apr 28 15:54:17 eu2napu003 nagios[12621]: Check your configuration file(s) to ensure that they contain valid
Apr 28 15:54:17 eu2napu003 nagios[12621]: directives and data definitions. If you are upgrading from a previous
Apr 28 15:54:17 eu2napu003 nagios[12621]: version of Nagios, you should be aware that some variables/definitions
Apr 28 15:54:17 eu2napu003 nagios[12621]: may have been removed or modified in this version. Make sure to read
Apr 28 15:54:17 eu2napu003 nagios[12621]: the HTML documentation regarding the config files, as well as the
Apr 28 15:54:17 eu2napu003 nagios[12621]: 'Whats New' section to find out what has changed.
Apr 28 15:54:17 eu2napu003 systemd[1]: nagios.service: control process exited, code=exited status=1
Apr 28 15:54:17 eu2napu003 systemd[1]: Failed to start Nagios Core 4.4.5.
Apr 28 15:54:17 eu2napu003 systemd[1]: Unit nagios.service entered failed state.
Apr 28 15:54:17 eu2napu003 systemd[1]: nagios.service failed.
[root@eu2napu003 var]#
Tried to start the service in other way as well.Getting below error:
[root@eu2napu003 var]# systemctl start nagios.service
Job for nagios.service failed because the control process exited with error code. See "systemctl status nagios.service" and "journalctl -xe" for details.