Hello There, Guest! Login Register
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Failed to start LSB: Starts and stops the Nagios monitoring server.

#1
I recently made some changes to check services on a host and successfully generated the Nagio Config.  When I deployed I received the following error:

PHP copy:
OK
recursive copy(/tmp/global/, /etc/nems/conf/global/)
system call
FAILED
sudo /bin/systemctl restart nagios


Job for nagios.service failed because the control process exited with error code. 
See "systemctl status nagios.service" and "journalctl -xe" for details.


I entered the following command on the NEMS server:

"sudo systemctl status nagios.service" gave the following result


● nagios.service - LSB: Starts and stops the Nagios monitoring server
   Loaded: loaded (/etc/init.d/nagios; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2018-09-30 20:28:50 PDT; 17s ago
     Docs: manConfusedystemd-sysv-generator(8)
  Process: 17487 ExecStart=/etc/init.d/nagios start (code=exited, status=8)

Sep 30 20:28:50 nems nagios[17487]:      Check your configuration file(s) to ensure that they contain valid
Sep 30 20:28:50 nems nagios[17487]:      directives and data definitions.  If you are upgrading from a previous
Sep 30 20:28:50 nems nagios[17487]:      version of Nagios, you should be aware that some variables/definitions
Sep 30 20:28:50 nems nagios[17487]:      may have been removed or modified in this version.  Make sure to read
Sep 30 20:28:50 nems nagios[17487]:      the HTML documentation regarding the config files, as well as the
Sep 30 20:28:50 nems nagios[17487]:      'Whats New' section to find out what has changed.
Sep 30 20:28:50 nems systemd[1]: nagios.service: Control process exited, code=exited status=8
Sep 30 20:28:50 nems systemd[1]: Failed to start LSB: Starts and stops the Nagios monitoring server.
Sep 30 20:28:50 nems systemd[1]: nagios.service: Unit entered failed state.
Sep 30 20:28:50 nems systemd[1]: nagios.service: Failed with result 'exit-code'.

and I then entered the command "sudo journalctl -xe"

Sep 30 20:16:17 nems nagios[12213]:      version of Nagios, you should be aware that some variables/definitions

Sep 30 20:16:17 nems nagios[12213]:      may have been removed or modified in this version.  Make sure to read

Sep 30 20:16:17 nems nagios[12213]:      the HTML documentation regarding the config files, as well as the

Sep 30 20:16:17 nems nagios[12213]:      'Whats New' section to find out what has changed.

Sep 30 20:16:17 nems systemd[1]: nagios.service: Control process exited, code=exited status=8

Sep 30 20:16:17 nems systemd[1]: Failed to start LSB: Starts and stops the Nagios monitoring server.

-- Subject: Unit nagios.service has failed

-- Defined-By: systemd

-- Support: https://www.debian.org/support

-- 

-- Unit nagios.service has failed.

-- 

-- The result is failed.

Sep 30 20:16:17 nems systemd[1]: nagios.service: Unit entered failed state.

Sep 30 20:16:17 nems systemd[1]: nagios.service: Failed with result 'exit-code'.

Sep 30 20:16:22 nems systemd[1]: [email protected]: Service has no hold-off time, scheduling restart.

Sep 30 20:16:22 nems systemd[1]: Stopped Getty on tty1.

-- Subject: Unit [email protected] has finished shutting down

-- Defined-By: systemd

-- Support: https://www.debian.org/support

-- 

-- Unit [email protected] has finished shutting down.

Sep 30 20:16:22 nems systemd[1]: Started Getty on tty1.

-- Subject: Unit [email protected] has finished start-up

-- Defined-By: systemd

-- Support: https://www.debian.org/support

-- 

-- Unit [email protected] has finished starting up.

-- 

-- The start-up result is done.

Sep 30 20:16:52 nems systemd[1]: [email protected]: Service has no hold-off time, scheduling restart.

Sep 30 20:16:52 nems systemd[1]: Stopped Getty on tty1.

-- Subject: Unit [email protected] has finished shutting down

-- Defined-By: systemd

-- Support: https://www.debian.org/support

-- 

-- Unit [email protected] has finished shutting down.

Sep 30 20:16:52 nems systemd[1]: Started Getty on tty1.

-- Subject: Unit [email protected] has finished start-up

-- Defined-By: systemd

-- Support: https://www.debian.org/support

-- 

-- Unit [email protected] has finished starting up.

-- 

-- The start-up result is done.

Sep 30 20:16:52 nems sudo[12467]:     john : TTY=pts/0 ; PWD=/home/john ; USER=root ; COMMAND=/bin/journalctl -xe

Sep 30 20:16:52 nems sudo[12467]: pam_unix(sudoConfusedession): session opened for user root by john(uid=0)

Sep 30 20:17:01 nems wpa_supplicant[726]: wlan0: Failed to initiate sched scan

Sep 30 20:17:01 nems CRON[12589]: pam_unix(cronConfusedession): session opened for user root by (uid=0)

Sep 30 20:17:01 nems CRON[12588]: pam_unix(cronConfusedession): session opened for user root by (uid=0)

Sep 30 20:17:01 nems CRON[12595]: (root) CMD (/root/nems/nems-migrator/support-sd.sh > /dev/null 2>&1)

Sep 30 20:17:01 nems CRON[12597]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Sep 30 20:17:01 nems CRON[12589]: pam_unix(cronConfusedession): session closed for user root

Sep 30 20:17:01 nems CRON[12588]: pam_unix(cronConfusedession): session closed for user root

Sep 30 20:17:14 nems sudo[12467]: pam_unix(sudoConfusedession): session closed for user root

Sep 30 20:17:23 nems systemd[1]: [email protected]: Service has no hold-off time, scheduling restart.

Sep 30 20:17:23 nems systemd[1]: Stopped Getty on tty1.

-- Subject: Unit [email protected] has finished shutting down

-- Defined-By: systemd

-- Support: https://www.debian.org/support

-- 

-- Unit [email protected] has finished shutting down.

Sep 30 20:17:23 nems systemd[1]: Started Getty on tty1.

-- Subject: Unit [email protected] has finished start-up

-- Defined-By: systemd

-- Support: https://www.debian.org/support

-- 

-- Unit [email protected] has finished starting up.

-- 
-- The start-up result is done.


I am stuck at this time and not sure how to progress without rebuilding the whole system.  Any help would be greatly appreciated.


 Reply
#2
Chances are there's a syntax error in the modifications you made, so the service cannot start. I try to create many useful check commands out of the box (and NEMS 1.5 will be a big improvement on this) but if you create your own or modify the stock ones, you might need to do some extra troubleshooting.

If at a loss, generate a support.nems file and let me know a bit more details about what changes you made, and we'll go from there.

Cheers,
Robbie
Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
 
 
Forum Jump:

Users browsing this thread: 1 Guest(s)