Nagios failed to start
Posted: Mon Apr 20, 2015 3:52 pm
Hey guys just done a new install of nagios core and its failing to start any help would be great
[root@ip-172-31-19-118 nagios-plugins-2.0]# service nagios start
Starting nagios (via systemctl): Job for nagios.service failed. See 'systemctl status nagios.service' and 'journalctl -xn' for details.
[FAILED]
[root@ip-172-31-19-118 nagios-plugins-2.0]# ^C
[root@ip-172-31-19-118 nagios-plugins-2.0]# systemctl status nagios.service
nagios.service - LSB: Starts and stops the Nagios monitoring server
Loaded: loaded (/etc/rc.d/init.d/nagios)
Active: failed (Result: exit-code) since Mon 2015-04-20 16:45:01 EDT; 10s ago
Process: 24195 ExecStart=/etc/rc.d/init.d/nagios start (code=exited, status=8)
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: ***> One or more problems was encountered while running the pre-flight check...
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: Check your configuration file(s) to ensure that they contain valid
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: directives and data defintions. If you are upgrading from a previous
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: version of Nagios, you should be aware that some variables/definitions
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: may have been removed or modified in this version. Make sure to read
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: the HTML documentation regarding the config files, as well as the
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: 'Whats New' section to find out what has changed.
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal systemd[1]: nagios.service: control process exited, code=exited status=8
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal systemd[1]: Failed to start LSB: Starts and stops the Nagios monitoring server.
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal systemd[1]: Unit nagios.service entered failed state.
[root@ip-172-31-19-118 nagios-plugins-2.0]# service nagios start
Starting nagios (via systemctl): Job for nagios.service failed. See 'systemctl status nagios.service' and 'journalctl -xn' for details.
[FAILED]
[root@ip-172-31-19-118 nagios-plugins-2.0]# ^C
[root@ip-172-31-19-118 nagios-plugins-2.0]# systemctl status nagios.service
nagios.service - LSB: Starts and stops the Nagios monitoring server
Loaded: loaded (/etc/rc.d/init.d/nagios)
Active: failed (Result: exit-code) since Mon 2015-04-20 16:45:01 EDT; 10s ago
Process: 24195 ExecStart=/etc/rc.d/init.d/nagios start (code=exited, status=8)
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: ***> One or more problems was encountered while running the pre-flight check...
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: Check your configuration file(s) to ensure that they contain valid
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: directives and data defintions. If you are upgrading from a previous
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: version of Nagios, you should be aware that some variables/definitions
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: may have been removed or modified in this version. Make sure to read
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: the HTML documentation regarding the config files, as well as the
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal nagios[24195]: 'Whats New' section to find out what has changed.
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal systemd[1]: nagios.service: control process exited, code=exited status=8
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal systemd[1]: Failed to start LSB: Starts and stops the Nagios monitoring server.
Apr 20 16:45:01 ip-172-31-19-118.us-west-2.compute.internal systemd[1]: Unit nagios.service entered failed state.