Apply Configuration Failing with no Error

[jdunitz]

After repairing the database, if the issue persists, please check the following:

You might want to temporarily comment your livestatus out of your /usr/local/nagios/etc/nagios.cfg file:

Code: Select all

# MKLivestatus
# broker_module=/usr/local/lib/mk-livestatus/livestatus.o /usr/local/nagios/var/rw/live

...and then restart Nagios core.


But first...

You're getting a bunch of these warnings about your notification intervals being less than their check intervals:

Code: Select all

Checking objects...
Warning: Service 'Services - Microsoft Shadow Copy' on host 'stcadsync01p' 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.
Warning: Service 'Services - Microsoft Shadow Copy' on host 'stcctx01d' 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.
Warning: Service 'Services - Microsoft Shadow Copy' on host 'stcctx01e' 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.

So, you need to go find what templates are assigned to each of your services, edit the templates, and fill in the notification interval, making sure that it matches the check interval. You might need to do this with a number of your templates, then when you apply the config, that should reduce the number of warnings you get...and hopefully the 139 will go away as well.

So, give that a try and let us know what happens.

[optionstechnology]

OK, DB repair done

Got the following-

===============
REPAIR COMPLETE
===============
Stopping ndo2db: done.
Starting ndo2db: done.
Stopping nagios: .done.
Starting nagios: done.

=======================
nagios database repair succeeded
nagiosql database repair succeeded
nagiosxi database repair succeeded

From the log-

200306 16:54:01 [Note] /usr/libexec/mysqld: Shutdown complete
200306 16:54:01 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
200306 16:54:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200306 16:54:02 InnoDB: Initializing buffer pool, size = 8.0M
200306 16:54:02 InnoDB: Completed initialization of buffer pool
200306 16:54:02 InnoDB: Started; log sequence number 4 2487665647
200306 16:54:02 [Note] Event Scheduler: Loaded 0 events
200306 16:54:02 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution

I've deleted and re-wrote the config - but the verify does this-

varifyfail.PNG

I reasonably sure its not livestatus or the warnings as both of these exist when the system restarts successfully - there's about 20 services that I cannot deactivate without triggering this bug

[benjaminsmith]

Hello @optionstechnology,

Thanks for your patience. Let's move this issue over to a support ticket as we may need to login to the system to further troubleshoot. Before doing so, please run the following command to reset the configuration permissions, and they try applying configuration once more.

1. Reset Config Permisisions

Code: Select all

/usr/local/nagiosxi/scripts/reset_config_perms.sh

2. Perform the Delete, Write and Verify steps again. Does it work this time?

3. Open a support ticket and attach a fresh system profile.

To open a support ticket, go to:

https://support.nagios.com/tickets/

there's about 20 services that I cannot deactivate without triggering this bug

Lastly, we have imported the configs on a test server, which services are triggering the error? Thanks.

[optionstechnology]

looks like the reset_config_perms has fixed the problem!

thanks

This can be closed

[optionstechnology]

Oh, sorry spoke too soon - it allowed me to delete about 15 services

and then the same error happened again - this time however the permission fix doesnt fix it

I will raise a support ticket

[benjaminsmith]

Hello @optionstechnology,

Ok. Sounds good. Please reference this post and attach a fresh system profile to the ticket. Thanks.