Problem with "host escalation" config and monitoring engine

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
morabanc
Posts: 199
Joined: Tue Jul 10, 2012 8:14 am

Problem with "host escalation" config and monitoring engine

Post by morabanc »

Hi guys,

We have problems to apply config in NagiosXI 5.5.7.

Code: Select all

! Nagios restart command failed.
An error occurred while attempting to apply your configuration to Nagios Core. Monitoring engine configuration files have been rolled back to their last known good checkpoint.

Error: Host escalation host name is NULL
Error: Could not register host escalation (config file '/usr/local/nagios/etc/hostescalations.cfg', starting on line 26)
Hostescalation file:

Code: Select all

define hostescalation {
    # config_name            lvl1
    hostgroup_name           Hosts_SMS
    contacts                  contact3
    contact_groups           contact1
    first_notification       1
    last_notification        3
    notification_interval    15
    escalation_period        24x7
}

define hostescalation {
    # config_name            lvl2
    hostgroup_name           Hosts_SMS
    contact_groups           contact2,contact1
    first_notification       4
    last_notification        0
    notification_interval    15
    escalation_period        24x7
}

define hostescalation {
    # config_name            Host_Dummy
    host_name                host_dummy
    contacts                 contact3
    contact_groups           contact1
    first_notification       1
    last_notification        3
    notification_interval    15
    escalation_period        24x7
}
I tried to deactivate all 3 hostescalation and when I applied config, I got the same error.
Also, an interesting thing is that the same config works in another nagiosxi.

Going to Admin --> System information --> System Status, I noticed that monitoring engine is failed and don't become start.

Check config manually

Code: Select all

Nagios Core 4.4.2
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 2018-08-16
License: GPL

Website: https://www.nagios.org
Reading configuration data...
   Read main config file okay...
   Read object config files okay...

Running pre-flight check on configuration data...

Checking objects...
        Checked 903 services.
        Checked 113 hosts.
        Checked 17 host groups.
        Checked 0 service groups.
        Checked 14 contacts.
        Checked 5 contact groups.
        Checked 194 commands.
        Checked 16 time periods.
        Checked 37 host escalations.
        Checked 74 service escalations.
Checking for circular paths...
        Checked 113 hosts
        Checked 0 service dependencies
        Checked 0 host dependencies
        Checked 16 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors:   0

Things look okay - No serious problems were detected during the pre-flight check
/var/log/messages

Code: Select all

Jan  4 10:12:34 nagios4 systemd: nagios.service: main process exited, code=killed, status=6/ABRT
Jan  4 10:12:34 nagios4 kill: kill: cannot find process ""
Jan  4 10:12:34 nagios4 systemd: nagios.service: control process exited, code=exited status=1
Jan  4 10:12:36 nagios4 xinetd[14614]: START: nsca pid=7184 from=::ffff:127.0.0.1
Jan  4 10:12:36 nagios4 systemd: Unit nagios.service entered failed state.
Jan  4 10:12:36 nagios4 systemd: nagios.service failed.
Jan  4 10:12:37 nagios4 xinetd[14614]: EXIT: nsca status=0 pid=7184 duration=1(sec)
systemctl start nagios.service

Code: Select all

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

Code: Select all

● nagios.service - Nagios Core 4.4.2
   Loaded: loaded (/usr/lib/systemd/system/nagios.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2019-01-04 10:17:11 CET; 22s ago
     Docs: https://www.nagios.org/documentation
  Process: 8161 ExecStopPost=/usr/bin/rm -f /usr/local/nagios/var/rw/nagios.cmd (code=exited, status=0/SUCCESS)
  Process: 8152 ExecStop=/usr/bin/kill -s TERM ${MAINPID} (code=exited, status=1/FAILURE)
  Process: 9585 ExecStart=/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg (code=exited, status=254)
  Process: 9583 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
 Main PID: 8109 (code=killed, signal=ABRT)
journalctl -n

Code: Select all

Jan 04 10:17:11 nagios4 nagios[9583]: Checking global event handlers...
Jan 04 10:17:11 nagios4 nagios[9583]: Checking obsessive compulsive processor commands...
Jan 04 10:17:11 nagios4 nagios[9583]: Checking misc settings...
Jan 04 10:17:11 nagios4 nagios[9583]: Total Warnings: 0
Jan 04 10:17:11 nagios4 nagios[9583]: Total Errors:   0
Jan 04 10:17:11 nagios4 nagios[9583]: Things look okay - No serious problems were detected during the pre-fl...check
Jan 04 10:17:11 nagios4 systemd[1]: nagios.service: control process exited, code=exited status=254
Jan 04 10:17:11 nagios4 systemd[1]: Failed to start Nagios Core 4.4.2.
Jan 04 10:17:11 nagios4 systemd[1]: Unit nagios.service entered failed state.
Jan 04 10:17:11 nagios4 systemd[1]: nagios.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
Also I tried to restart mariadb process, nagios process and repair all DB.

Any idea ?

Thanks in advance
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Problem with "host escalation" config and monitoring eng

Post by scottwilkerson »

Can you post the output of the following:

Code: Select all

chage -l nagios
tail -10 /var/log/cron
It could be an expired user and you are just seeing the same error from a previous run.
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
nmunoz
Posts: 9
Joined: Fri Jan 04, 2019 1:57 am
Location: Andorra
Contact:

Re: Problem with "host escalation" config and monitoring eng

Post by nmunoz »

Hello Scott,

It seems that the user is not expired:

Code: Select all

chage -l nagios
Last password change                                    : Nov 14, 2018
Password expires                                        : never
Password inactive                                       : never
Account expires                                         : never
Minimum number of days between password change          : 0
Maximum number of days between password change          : 99999
Number of days of warning before password expires       : 7

Code: Select all

tail -10 /var/log/cron
Jan  4 16:51:01 nagios4 CROND[13670]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/reportengine.php >> /usr/local/nagiosxi/var/reportengine.log 2>&1)
Jan  4 16:51:01 nagios4 CROND[13671]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/cleaner.php >> /usr/local/nagiosxi/var/cleaner.log 2>&1)
Jan  4 16:51:01 nagios4 CROND[13672]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/perfdataproc.php >> /usr/local/nagiosxi/var/perfdataproc.log 2>&1)
Jan  4 16:51:01 nagios4 CROND[13673]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/deadpool.php >> /usr/local/nagiosxi/var/deadpool.log 2>&1)
Jan  4 16:51:01 nagios4 CROND[13674]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/nom.php >> /usr/local/nagiosxi/var/nom.log 2>&1)
Jan  4 16:51:01 nagios4 CROND[13675]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php >> /usr/local/nagiosxi/var/feedproc.log 2>&1)
Jan  4 16:51:01 nagios4 CROND[13676]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/event_handler.php >> /usr/local/nagiosxi/var/event_handler.log 2>&1)
Jan  4 16:51:01 nagios4 CROND[13677]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/eventman.php >> /usr/local/nagiosxi/var/eventman.log 2>&1)
Jan  4 16:51:01 nagios4 CROND[13678]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/cmdsubsys.php >> /usr/local/nagiosxi/var/cmdsubsys.log 2>&1)
Jan  4 16:51:01 nagios4 CROND[13679]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php >> /usr/local/nagiosxi/var/sysstat.log 2>&1)
I hope this help

Thanks
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Problem with "host escalation" config and monitoring eng

Post by scottwilkerson »

Can you run the following from the command line and report the output

Code: Select all

getenforce
ll /usr/local/nagios/etc/import
cd /usr/local/nagiosxi/scripts/
./reconfigure_nagios.sh
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
nmunoz
Posts: 9
Joined: Fri Jan 04, 2019 1:57 am
Location: Andorra
Contact:

Re: Problem with "host escalation" config and monitoring eng

Post by nmunoz »

Hello Scott

Code: Select all

getenforce
Disabled

Code: Select all

ll /usr/local/nagios/etc/import
total 60
-rw-rw-r--  1 apache nagios 46010 Nov  8 12:35 backup_nagios5.tar.gz
drwxrwxr-x. 2 apache nagios  4096 Dec 18 10:26 hosts
drwxrwxr-x. 2 apache nagios     6 Sep 17 15:24 import
drwxrwxr-x. 4 apache nagios   246 Dec 18 10:26 pnp
drwxrwxr-x. 2 apache nagios  4096 Dec 18 10:26 services
drwxrwxr-x. 2 apache nagios    68 Dec 18 10:26 static
You have new mail in /var/spool/mail/root

Code: Select all

./reconfigure_nagios.sh

--- reset_config_perms.sh ------------
> Setting CCM script permissions
> Setting script permissions
> Setting special component script permissions
> Setting configuration file/directory permissions
> Setting perfdata directory and RRD permissions
> Setting NOM checkpoint user:group permissions
> + Setting CCM configuration file user:group permissions
> + Setting Recurring Downtime file user:group permissions
> + Setting BPI configuration file user:group permissions
--------------------------------------

--- ccm_import.php -------------------
> Setting import directory: /usr/local/nagios/etc/import/
> Importing config files into the CCM
  No files to import
--------------------------------------
Another reconfigure process is still running, sleeping...

--- ccm_export.php -------------------
> Writing CCM configuration to Nagios files
  Finished writing out configuraton
--------------------------------------

--------------------------------------
> Verifying configuration with Nagios Core
> Output:
Nagios Core 4.4.2
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 2018-08-16
License: GPL

Website: https://www.nagios.org
Reading configuration data...
   Read main config file okay...
   Read object config files okay...

Running pre-flight check on configuration data...

Checking objects...
        Checked 903 services.
        Checked 113 hosts.
        Checked 17 host groups.
        Checked 0 service groups.
        Checked 14 contacts.
        Checked 5 contact groups.
        Checked 194 commands.
        Checked 16 time periods.
        Checked 37 host escalations.
        Checked 74 service escalations.
Checking for circular paths...
        Checked 113 hosts
        Checked 0 service dependencies
        Checked 0 host dependencies
        Checked 16 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors:   0

Things look okay - No serious problems were detected during the pre-flight check
> Return Code: 0
--------------------------------------
Job for nagios.service failed because the control process exited with error code. See "systemctl status nagios.service" and "journalctl -xe" for details.
nmunoz
Posts: 9
Joined: Fri Jan 04, 2019 1:57 am
Location: Andorra
Contact:

Re: Problem with "host escalation" config and monitoring eng

Post by nmunoz »

Hello Scott,

I send you the output of "status nagios.service" and "journalctl -xe"

Code: Select all

systemctl status nagios.service
● nagios.service - Nagios Core 4.4.2
   Loaded: loaded (/usr/lib/systemd/system/nagios.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2019-01-04 17:10:44 CET; 1min 25s ago
     Docs: https://www.nagios.org/documentation
  Process: 8161 ExecStopPost=/usr/bin/rm -f /usr/local/nagios/var/rw/nagios.cmd (code=exited, status=0/SUCCESS)
  Process: 8152 ExecStop=/usr/bin/kill -s TERM ${MAINPID} (code=exited, status=1/FAILURE)
  Process: 23811 ExecStart=/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg (code=exited, status=254)
  Process: 23807 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
 Main PID: 8109 (code=killed, signal=ABRT)

Jan 04 17:10:44 nagios4 nagios[23807]: Checking global event handlers...
Jan 04 17:10:44 nagios4 nagios[23807]: Checking obsessive compulsive processor commands...
Jan 04 17:10:44 nagios4 nagios[23807]: Checking misc settings...
Jan 04 17:10:44 nagios4 nagios[23807]: Total Warnings: 0
Jan 04 17:10:44 nagios4 nagios[23807]: Total Errors:   0
Jan 04 17:10:44 nagios4 nagios[23807]: Things look okay - No serious problems were detected during the pre-flight check
Jan 04 17:10:44 nagios4 systemd[1]: nagios.service: control process exited, code=exited status=254
Jan 04 17:10:44 nagios4 systemd[1]: Failed to start Nagios Core 4.4.2.
Jan 04 17:10:44 nagios4 systemd[1]: Unit nagios.service entered failed state.
Jan 04 17:10:44 nagios4 systemd[1]: nagios.service failed.

Code: Select all

journalctl -xe
-- The start-up result is done.
Jan 04 17:13:01 nagios4 CROND[24829]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/cleaner.php >> /usr/local/nagiosxi/va
Jan 04 17:13:01 nagios4 CROND[24830]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/deadpool.php >> /usr/local/nagiosxi/v
Jan 04 17:13:01 nagios4 CROND[24831]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/perfdataproc.php >> /usr/local/nagios
Jan 04 17:13:01 nagios4 CROND[24832]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php >> /usr/local/nagiosxi/v
Jan 04 17:13:01 nagios4 CROND[24833]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/reportengine.php >> /usr/local/nagios
Jan 04 17:13:01 nagios4 CROND[24834]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/eventman.php >> /usr/local/nagiosxi/v
Jan 04 17:13:01 nagios4 CROND[24835]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/nom.php >> /usr/local/nagiosxi/var/no
Jan 04 17:13:01 nagios4 CROND[24836]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php >> /usr/local/nagiosxi/va
Jan 04 17:13:01 nagios4 CROND[24837]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/cmdsubsys.php >> /usr/local/nagiosxi/
Jan 04 17:13:01 nagios4 CROND[24838]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/event_handler.php >> /usr/local/nagio
Jan 04 17:13:01 nagios4 sudo[24880]:   nagios : TTY=unknown ; PWD=/home/nagios ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/m
Jan 04 17:13:01 nagios4 sudo[24880]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 04 17:13:01 nagios4 sudo[24880]: pam_unix(sudo:session): session closed for user root
Jan 04 17:13:01 nagios4 sudo[24893]:   nagios : TTY=unknown ; PWD=/home/nagios ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/m
Jan 04 17:13:01 nagios4 sudo[24893]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 04 17:13:01 nagios4 sudo[24893]: pam_unix(sudo:session): session closed for user root
Jan 04 17:13:01 nagios4 sudo[24902]:   nagios : TTY=unknown ; PWD=/home/nagios ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/m
Jan 04 17:13:01 nagios4 sudo[24902]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 04 17:13:01 nagios4 sudo[24902]: pam_unix(sudo:session): session closed for user root
Jan 04 17:13:04 nagios4 ndo2db[26579]: Trimming timedevents.
Jan 04 17:13:04 nagios4 ndo2db[26579]: Trimming systemcommands.
Jan 04 17:13:04 nagios4 ndo2db[26579]: Trimming servicechecks.
Jan 04 17:13:04 nagios4 ndo2db[26579]: Trimming hostchecks.
Jan 04 17:13:04 nagios4 ndo2db[26579]: Trimming eventhandlers.
Jan 04 17:13:21 nagios4 sudo[25021]:   nagios : TTY=unknown ; PWD=/home/nagios ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/m
Jan 04 17:13:21 nagios4 sudo[25021]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 04 17:13:21 nagios4 sudo[25021]: pam_unix(sudo:session): session closed for user root
Jan 04 17:13:21 nagios4 sudo[25029]:   nagios : TTY=unknown ; PWD=/home/nagios ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/m
Jan 04 17:13:21 nagios4 sudo[25029]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 04 17:13:21 nagios4 sudo[25029]: pam_unix(sudo:session): session closed for user root
Jan 04 17:13:21 nagios4 sudo[25038]:   nagios : TTY=unknown ; PWD=/home/nagios ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/m
Jan 04 17:13:21 nagios4 sudo[25038]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 04 17:13:21 nagios4 sudo[25038]: pam_unix(sudo:session): session closed for user root
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Problem with "host escalation" config and monitoring eng

Post by scottwilkerson »

Ok there seems to be an error here

Code: Select all

Job for nagios.service failed because the control process exited with error code. See "systemctl status nagios.service" and "journalctl -xe" for details.
can you run the following and report the results:

Code: Select all

systemctl stop nagios
killall -9 nagios
rm -rf /usr/local/nagios/var/nagios.lock /var/run/nagios.lock
systemctl start nagios
systemctl status nagios
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
nmunoz
Posts: 9
Joined: Fri Jan 04, 2019 1:57 am
Location: Andorra
Contact:

Re: Problem with "host escalation" config and monitoring eng

Post by nmunoz »

Code: Select all

[root@nagios4 scripts]# systemctl stop nagios
[root@nagios4 scripts]#

Code: Select all

[root@nagios4 scripts]# killall -9 nagios
[root@nagios4 scripts]# ps -ef |grep nagios
nagios    2343  2333  0 17:33 ?        00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/perfdataproc.php >> /usr/local/nagiosxi/var/perfdataproc.log 2>&1
nagios    2344  2334  0 17:33 ?        00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php >> /usr/local/nagiosxi/var/feedproc.log 2>&1
nagios    2345  2335  0 17:33 ?        00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/event_handler.php >> /usr/local/nagiosxi/var/event_handler.log 2>&1
nagios    2346  2337  0 17:33 ?        00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/cmdsubsys.php >> /usr/local/nagiosxi/var/cmdsubsys.log 2>&1
nagios    2347  2338  0 17:33 ?        00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php >> /usr/local/nagiosxi/var/sysstat.log 2>&1
nagios    2351  2336  0 17:33 ?        00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/eventman.php >> /usr/local/nagiosxi/var/eventman.log 2>&1
nagios    2353  2343  0 17:33 ?        00:00:00 /usr/bin/php -q /usr/local/nagiosxi/cron/perfdataproc.php
nagios    2354  2344  0 17:33 ?        00:00:00 /usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php
nagios    2355  2345  0 17:33 ?        00:00:00 /usr/bin/php -q /usr/local/nagiosxi/cron/event_handler.php
nagios    2356  2346  0 17:33 ?        00:00:00 /usr/bin/php -q /usr/local/nagiosxi/cron/cmdsubsys.php
nagios    2357  2347  0 17:33 ?        00:00:00 /usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php
nagios    2358  2351  0 17:33 ?        00:00:00 /usr/bin/php -q /usr/local/nagiosxi/cron/eventman.php
root      2598 19893  0 17:33 pts/1    00:00:00 grep --color=auto nagios
nagios   14548     1  0 09:26 ?        00:00:01 /usr/local/nagios/bin/npcd -d -f /usr/local/nagios/etc/pnp/npcd.cfg
nagios   26431     1  0 10:45 ?        00:00:00 /usr/local/nagios/bin/ndo2db -c /usr/local/nagios/etc/ndo2db.cfg -f
[root@nagios4 scripts]#
[root@nagios4 scripts]#
[root@nagios4 scripts]#
[root@nagios4 scripts]# rm -rf /usr/local/nagios/var/nagios.lock /var/run/nagios.lock
[root@nagios4 scripts]# systemctl start nagios
You have new mail in /var/spool/mail/root
[root@nagios4 scripts]# systemctl status nagios
● nagios.service - Nagios Core 4.4.2
   Loaded: loaded (/usr/lib/systemd/system/nagios.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2019-01-04 17:34:04 CET; 7s ago
     Docs: https://www.nagios.org/documentation
  Process: 3001 ExecStopPost=/usr/bin/rm -f /usr/local/nagios/var/rw/nagios.cmd (code=exited, status=0/SUCCESS)
  Process: 2958 ExecStop=/usr/bin/kill -s TERM ${MAINPID} (code=exited, status=1/FAILURE)
  Process: 2909 ExecStart=/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
  Process: 2906 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
 Main PID: 2911 (code=killed, signal=ABRT)

Jan 04 17:34:02 nagios4 nagios[2911]: ndomod registered for acknowledgement data'
Jan 04 17:34:02 nagios4 nagios[2911]: ndomod registered for state change data'
Jan 04 17:34:02 nagios4 nagios[2911]: ndomod registered for contact status data'
Jan 04 17:34:02 nagios4 nagios[2911]: ndomod registered for adaptive contact data'
Jan 04 17:34:02 nagios4 nagios[2911]: Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.
Jan 04 17:34:02 nagios4 systemd[1]: nagios.service: main process exited, code=killed, status=6/ABRT
Jan 04 17:34:02 nagios4 kill[2958]: kill: cannot find process ""
Jan 04 17:34:02 nagios4 systemd[1]: nagios.service: control process exited, code=exited status=1
Jan 04 17:34:04 nagios4 systemd[1]: Unit nagios.service entered failed state.
Jan 04 17:34:04 nagios4 systemd[1]: nagios.service failed.
[root@nagios4 scripts]#
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Problem with "host escalation" config and monitoring eng

Post by scottwilkerson »

Something doesn't seem correct, can you show the output of the following:

Code: Select all

grep nagios.lock /usr/local/nagios/etc/nagios.cfg
grep nagios.lock /etc/init.d/nagios
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
nmunoz
Posts: 9
Joined: Fri Jan 04, 2019 1:57 am
Location: Andorra
Contact:

Re: Problem with "host escalation" config and monitoring eng

Post by nmunoz »

Code: Select all

grep nagios.lock /usr/local/nagios/etc/nagios.cfg
lock_file=/var/run/nagios.lock

Code: Select all

grep nagios.lock /etc/init.d/nagios
grep: /etc/init.d/nagios: No such file or directory
Thanks
Locked