Apply Configuration Failing with no Error

[optionstechnology]

I'm getting this when I try to delete a service-

failednag.PNG

There's no errors in the restart log, and the service has no dependencies

I can delete other services with no issues

I've tried deleting and re-writing the filers in "Config File Management"

[jdunitz]

I'm going to suggest that you manually run the reconfig, and look at what shows up in the cmdsubsys log:

Code: Select all

cd /usr/local/nagiosxi/scripts
./reconfigure_nagios.sh &> /tmp/reconfig.txt

and immediately after:

Code: Select all

tail -f /usr/local/nagiosxi/var/cmdsubsys.log &> /tmp/cmd.txt

Without knowing more about your setup and what you've done, my initial guess is that you might have a service defined somewhere that is defined incorrectly, which is one easy way to cause that kind of error. Let's see what your cmdsubsys log shows us!

[optionstechnology]

reconfig.txt -

--- reset_config_perms.sh ------------
> Setting script permissions
> Setting CCM script permissions
> Setting special script permissions
> Setting special component script permissions
> Setting configuration file/directory permissions
> Setting perfdata directory and RRD permissions
> Setting libexec directory permissions
> Setting Nagios XI config permissions
> Setting NOM checkpoint user:group permissions
> + Setting Nagios Core corelog.newobjects 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
--------------------------------------

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

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

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


Warning: Duplicate ------------------------ big bunch of duplicates but all are only warning level



> Return Code: 139
--------------------------------------
/usr/local/nagiosxi/nom/checkpoints/nagioscore/errors /usr/local/nagiosxi/scripts
tar: Removing leading `/' from member names
/usr/local/nagiosxi/scripts
LATEST NOM SNAPSHOT: /usr/local/nagiosxi/nom/checkpoints/nagioscore/1582889147.tar.gz
/ /usr/local/nagiosxi/scripts
RESTORING NOM SNAPSHOT : /usr/local/nagiosxi/nom/checkpoints/nagioscore/1582889147.tar.gz
/usr/local/nagiosxi/scripts

--- reset_config_perms.sh ------------
> Setting script permissions
> Setting CCM script permissions
> Setting special script permissions
> Setting special component script permissions
> Setting configuration file/directory permissions
> Setting perfdata directory and RRD permissions
> Setting libexec directory permissions
> Setting Nagios XI config permissions
> Setting NOM checkpoint user:group permissions
> + Setting Nagios Core corelog.newobjects user:group permissions
> + Setting CCM configuration file user:group permissions
> + Setting Recurring Downtime file user:group permissions
> + Setting BPI configuration file user:group permissions
--------------------------------------

cmd.txt -

.......................................
PROCESSED 1 COMMANDS
...............connect() timed out!
............................................
PROCESSED 0 COMMANDS
...............connect() timed out!
.............................................
PROCESSED 0 COMMANDS
...............connect() timed out!
.............................................
PROCESSED 0 COMMANDS
..

[optionstechnology]

I've also reversed the change I made and reconfigured config so you can see what it looks like during a successful run-

reconfig.txt

--- reset_config_perms.sh ------------
> Setting script permissions
> Setting CCM script permissions
> Setting special script permissions
> Setting special component script permissions
> Setting configuration file/directory permissions
> Setting perfdata directory and RRD permissions
> Setting libexec directory permissions
> Setting Nagios XI config permissions
> Setting NOM checkpoint user:group permissions
> + Setting Nagios Core corelog.newobjects 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
--------------------------------------

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

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

Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Warning: Duplicate definition


BIG BUNCH OF WARNINGS



Read object config files okay...

Running pre-flight check on configuration data...

Checking objects...

BIG BUNCH OF WARNINGS


has a notification interval less than its check interval! Notifications are only re-sent after checks are made, so the effective notification interval will be that of the check interval.
Checked 5394 services.
Checked 180 hosts.
Checked 104 host groups.
Checked 16 service groups.
Checked 20 contacts.
Checked 10 contact groups.
Checked 179 commands.
Checked 17 time periods.
Checked 10 host escalations.
Checked 454 service escalations.
Checking for circular paths...
Checked 180 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 17 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 389
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check
> Return Code: 0
--------------------------------------
Stopping nagios: .done.
Starting nagios: done.

cmd.txt -

.............................................
PROCESSED 0 COMMANDS
...............connect() timed out!
..............................................
PROCESSED 0 COMMANDS
...............connect() timed out!
............................................
PROCESSED 0 COMMANDS
...............connect() timed out!
............................................
PROCESSED 0 COMMANDS
..............connect() timed out!
...............................................
PROCESSED 0 COMMANDS
...............connect() timed out!
............................................
PROCESSED 0 COMMANDS
...............connect() timed out!
.............................................
PROCESSED 0 COMMANDS
...............connect() timed out!
..............................................
PROCESSED 0 COMMANDS
...............connect() timed out!
............................................
PROCESSED 0 COMMANDS
...............connect() timed out!
............................................

[optionstechnology]

Looks like this is the issue-

> Return Code: 139

[jdunitz]

The fact that you're getting a ton of duplicate errors is a likely cause of this problem, but you should also update your PHP execution timeout, as described here:
https://support.nagios.com/kb/article/n ... e-611.html

After updating that, let's tackle your duplicate errors.
Can you go to Configure -> Core Config -> Config File Management (on the left under Tools) and click "Verify Files"?

VerifyFiles.PNG

That should show you what items you have that are duplicated. Then you'll need to go clean up your duplicate definitions.
Perhaps you have hosts and services associated both individually as well as through host groups, or something like that--that's what you'll need to get sorted.

After you clean up your duplicates and try the reconfig again, you might find that things are working better. If not, please send us a current system profile, and we'll go from there.

Let us know what you find!

To send us your system profile.
Login to the Nagios XI GUI using a web browser
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and share this in a private message and then reply to this post to bring it up in the queue.

[optionstechnology]

I've tried all of the above with no luck

When I try to download a profile I get this -

profilefail.PNG

[jdunitz]

That particular error would suggest that something happened to your sudoers file. Did you (or someone) change it recently?

Here's an article with a link to a script to auto-fix the sudoers file back to an out-of-the-box state.

If you had additional customizations, you might have to put them back manually. Make a backup of your current file.

Have a look at this:
Nagios XI Profile Build Failure

Let us know if you're able to get a profile generated after restoring the sudoers file.

[optionstechnology]

That's the profile download fixed - I've PMed it to you

[lmiltchev]

You have crashed db tables - I see multiple errors in the db log as this one:

200303 9:17:14 [ERROR] /usr/libexec/mysqld: Table './nagios/nagios_systemcommands' is marked as crashed and should be repaired

Let's start with repairing the database:

Code: Select all

/usr/local/nagiosxi/scripts/repair_databases.sh

Check the db log after you run the repair script to see if there are more errors:

Code: Select all

tail /var/log/mysqld.log

You can find more information on the topic here:
https://support.nagios.com/kb/article/n ... es-24.html

Once, you make sure that you no longer have crashed db tables, run the Config File Management tool and check of errors:

Admin > Tools > Config File Management > Delete Files > Write Configs > Verify Files

If you don't see any errors after clicking on each button, apply configuration. If you see some errors, post them on the forum. Thanks!