Nagios does not start anymore after UCS Update

Since UCS Update in February Nagios does not start anymore.
Before it was running fine.
If I try to start the service manually I see this:

root@s1:~# service nagios3 start
Job for nagios3.service failed. See 'systemctl status nagios3.service' and 'journalctl -xn' for details.
root@s1:~# systemctl status nagios3.service
● nagios3.service - LSB: nagios host/service/network monitoring and management system
   Loaded: loaded (/etc/init.d/nagios3)
   Active: failed (Result: exit-code) since Mo 2018-03-12 08:58:19 CET; 11s ago
  Process: 9395 ExecStart=/etc/init.d/nagios3 start (code=exited, status=1/FAILURE)

Mär 12 08:58:19 s1 nagios3[9395]: Total Errors:   1
Mär 12 08:58:19 s1 nagios3[9395]: ***> One or more problems was encountered while running the pre...ck...
Mär 12 08:58:19 s1 nagios3[9395]: Check your configuration file(s) to ensure that they contain valid
Mär 12 08:58:19 s1 nagios3[9395]: directives and data defintions.  If you are upgrading from a previous
Mär 12 08:58:19 s1 nagios3[9395]: version of Nagios, you should be aware that some variables/definitions
Mär 12 08:58:19 s1 nagios3[9395]: may have been removed or modified in this version.  Make sure to read
Mär 12 08:58:19 s1 nagios3[9395]: the HTML documentation regarding the config files, as well as the
Mär 12 08:58:19 s1 nagios3[9395]: 'Whats New' section to find out what has changed.
Mär 12 08:58:19 s1 nagios3[9395]: errors in config! ... failed!
Mär 12 08:58:19 s1 nagios3[9395]: failed!
Hint: Some lines were ellipsized, use -l to show in full.
root@s1:~#

Any hints how i can figure out the error to get the service up again?
Would be nice if anyone can help me.

Thanks
Stefan

Hey,

unfortunately systemctl status only shows the last couple of lines a service unit has created, and in this case the interesting bits are in the messages that aren’t shown. Please try to start the service, run journalctl -u nagios3.service --since '5min ago' and post all of what it outputs. Thanks.

Kind regards,
mosu

Thanks a lot. That was the solution. It was an typing error in an nagios service “checkfping” should be “check_fping”.
It was my mistake :wink: