Nagios XI - Apply Configuration Never Completes

Problem Description

If you attempt to Apply Configuration and you're seeing the following output:

The following error message is produced:

* Configuration submitted for processing...
* Waiting for configuration verification..................

The configuration never applies, the page may be timing out.

There are several reason why this problem may be occurring, each one of them is outlined below.



Editing Files

In many steps of this article you will be required to edit files. This documentation will use the vi text editor. When using the vi



Missing / Incorrect sudoers Entries

The backend components in Nagios XI require high level privileges, these are accommodated for in sudoers entries. This allows for high level commands to be executed by scripts without requiring user input. If these entries are missing then they can cause unexpected results.

Examples Of Errors / Behaviours

When tailing the log /usr/local/nagiosxi/var/cmdsubsys.log you see:

Another reconfigure process is still running, sleeping...
Another reconfigure process is still running, sleeping...
Another reconfigure process is still running, sleeping...
Another reconfigure process is still running, sleeping...


sudo: no tty present and no askpass program specified


Another error occurs if you su as the nagios user and execute the following commands:

su nagios
cd /usr/local/nagiosxi/scripts

You are prompted for the password for the nagios user:

URL: http://localhost/nagiosxi/includes/components/ccm/
/usr/bin/wget --save-cookies nagiosql.cookies --keep-session-cookies http://localhost/nagiosxi/includes/components/ccm/ --no-check-certificate --post-data 'submit=Login&hidelog=true&loginSubmitted=true&username=nagiosxi&password=n@gweb' -O nagiosql.login--2016-08-03 09:40:38-- http://localhost/nagiosxi/includes/components/ccm/
Resolving localhost... ::1,
Connecting to localhost|::1|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “nagiosql.login”

[ <=> ] 31,509 --.-K/s in 0.01s

2016-08-03 09:40:38 (2.61 MB/s) - “nagiosql.login” saved [31509]

IMPORTING CONFIG FILES...URL: http://localhost/nagiosxi/includes/components/ccm/
[sudo] password for nagios:


You should not be prompted for the password, this is another indication that the sudoers entries are incorrect/missing.


You may eventually get the following error on the Apply Configuration screen:

Reset config permissions 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


Fixing the sudoers Entries

The following steps shows you how to get the correct sudoers entries from the XI installation file. It is not possible to provide all the entries in this KB article as they may change in newer versions of XI. These steps ensure you get the correct entries for your version of Nagios XI.

First you must download the XI installation file to your Nagios XI server. You'll do this with the wget command. Please refer to the following link to get the correct download link for your version of Nagios XI:

Download Page - Nagios XI Versions

Open an ssh session to your Nagios XI host. If you are already connected as the nagios user (in the step above) you will need to exit to become an admin.

Execute the following commands (use your XI version download link in the wget command):

cd /tmp


Once downloaded you'll need to use the name of the downloaded file in the next command, in this example xi-5.5.7.tar.gz is the name being used:

tar xzf xi-5.5.7.tar.gz nagiosxi/nagiosxi/nagiosxi.sudoers --strip-components 2

This will have extracted a file called nagiosxi.sudoers and this file contains all the correct entries.

Run all these commands to fix your /etc/sudoers file to make sure it has all the correct entries:

grep -v NAGIOSXI /etc/sudoers > /etc/
mv -f /etc/ /etc/sudoers
rm -rf /etc/sudoers.d/nagiosxi
sed -i 's/^Defaults requiretty/#Defaults requiretty/g' /etc/sudoers
cat /tmp/nagiosxi.sudoers >> /etc/sudoers
chmod 440 /etc/sudoers

Run this one last command to ensure the old lock file is removed:

rm -f /usr/local/nagiosxi/scripts/reconfigure_nagios.lock


After making these changes try and "Apply Configuration" from CCM and your problem should be resolved.



Large Amount Of Objects

Sometimes when creating a large amount of objects the apply configuration process is taking longer than expected and PHP may time out or exceed limits.

These are defined in the php.ini file, The location of the php.inifile differs depending on your operating system / version. The following command will determine the location:

find /etc -name php.ini

If there are multiple results then the one in the apache directory is the one that needs changing.

Edit /etc/php.ini and increase these values:

max_execution_time = 60
max_input_time = 60
memory_limit = 256M


After making these changes you'll need to restart the Apache service using one of the commands below:


RHEL 7 | CentOS 7 | Oracle Linux 7

systemctl restart httpd.service


Debian | Ubuntu 16/18

systemctl restart apache2.service


If you are still seeing the same problem, bump them up a bit more, and/or contact the Nagios Support team for assistance. These are explained in more detail in the following KB article:

Nagios XI - PHP Variables



SSL/TLS Redirection

When implementing SSL/TLS certificates on your Nagios XI server, the option use_https needs to be defined as true in the file.

Edit /usr/local/nagiosxi/html/ and define the option as follows:

$cfg['use_https'] = true;


This step is included as part of the following documentation:

Documentation - How To Configure SSL/TLS



localhost Missing From /etc/hosts

The following KB article may also resolve your problem:

Nagios XI - Apply Configuration Fails - Backend login to the Core Configuration failed



Final Thoughts

For any support related questions please visit the Nagios Support Forums at:

Article ID: 34
Created On: Tue, Jan 27, 2015 at 3:46 PM
Last Updated On: Tue, Feb 9, 2021 at 10:12 AM
Authored by: slansing

Online URL: