Nagios Support Forum

Hello all. I have an issue that is partly covered here in the formus, but I am unable to solve on my own.

Version -- Nagios XI 2014R2.0
OS -- Red Hat Enterprise Server 6.5 (64 bit)
Manual installation by following the steps in Manual Installation Instructions document
Special configurations:
We are using the automouter deamon on our network, which has control over how directories are written in the /home directory.
During the Nagios XI installation process, which completed without errors, there was no /home/nagios directory created, although a nagios user was created

My issue seems to be occuring when I run any configuration wizards, namely Auto-Discovery and Linux Server Monitoring Wizard.

The auto-discovery wizard finds all the hosts on our network without issues. But during the configuration, it simply hangs after the request for verification has been sent.
Same problem with using the linux monitoring wizard. I follow the steps to provide the IP address, the Red Hat enterprise distribution, the pre-selected server metrics, and monitoring settings. I click 'finish' and the request goes out

Linux Server Monitoring Wizard

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

That last part never finishes.

I read on one of the posts of a person having a similar issue who commented about their system not having '/home/nagios' and he created that directory which seemed to solve his issue.

For me, that is not as simple as it sounds because of how automounter is working across our network.

Is there any way I can change the default settings for the nagios user home directory? Or is there a different issue causing my configuraiton wizard problem?

Thanks for any inputs!

First of all, you have some timezone errors. Pleas refer to the following doc:
http://assets.nagios.com/downloads/nagi ... m_Time.pdf
Next, have you implemented ssl/forced ssl/offloaded dbs/ramdisk/etc?

Thanks for the reply. I have went through and made adjustments with the timezone following the document and this shows up in the System Profile:

PHP Timezone: America/New_York
PHP Time: Thu, 04 Dec 2014 08:49:31 -0500
System Time: Thu, 04 Dec 2014 08:49:31 -0500

Can you be more specific about ssl / forced ssl, etc... please?

This is a new installation on a new system and our Linux administrator is on another program now. So I'm unable to give a clear answer to that question.

I got a little bit closer by taking a step this user suggested but configuration is still failing:

Re: Waiting for configuration verification stuck

Postby vladimir_vinnik » Fri Sep 12, 2014 6:43 pm
Just wanted to let everybody know that I found the problem. Apparently /home/nagios folder was missing on the server after the installation, which seems to be a mandatory part of the installation.

Our systems use the automounter service autofs and when I stop autofs on the system hosting Nagios XI I am able to create /home/nagios which gets me a little bit further than before.

Now that the /home/nagios directory exists, when I run the configuration wizard from the Config screen I get this output:

Linux Server Monitoring Wizard

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

Configuration Error

An error occurred while attempting to apply your configuration to the monitoring engine. Contact your Nagios administrator if this problem persists.

Run this monitoring wizard again
Run another monitoring wizard

View the latest configuration snapshots

The latest profile is at the top of this post.

Hello,

Can you navigate to CCM > Tools > Write Configs Tool, then click write followed by verify, and it should point out where your configuration error lies so that you can fix it, and get a cleanly applied configuration.

There are no apparent errors

After the 'write'

Write host configurations ...
Host configuration files successfully written!

Write service configurations ...
Service configuration files successfully written!

Configuration file: hostgroups.cfg successfully written!
Configuration file: servicegroups.cfg successfully written!
Configuration file: hosttemplates.cfg successfully written!
Configuration file: servicetemplates.cfg successfully written!
Configuration file: timeperiods.cfg successfully written!
Configuration file: commands.cfg successfully written!
Configuration file: contacts.cfg successfully written!
Configuration file: contactgroups.cfg successfully written!
Configuration file: contacttemplates.cfg successfully written!
Configuration file: servicedependencies.cfg successfully written!
Configuration file: hostdependencies.cfg successfully written!
Configuration file: serviceescalations.cfg successfully written!
Configuration file: hostescalations.cfg successfully written!
Configuration file: serviceextinfo.cfg successfully written!
Configuration file: hostextinfo.cfg successfully written!

And after the verify:

Nagios Core 4.0.8
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 08-12-2014
License: GPL

Website: http://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 8 services.
Checked 1 hosts.
Checked 1 host groups.
Checked 0 service groups.
Checked 2 contacts.
Checked 2 contact groups.
Checked 116 commands.
Checked 8 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 1 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 8 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

Does the NPRE agent need to be running on the remote host to be monitored before the verification will complete successfully?

It does not need to be running, nagios will never verify a remote agent when doing config verifies. The apply config will absolutely hang without a home directory for nagios, although we do not really care where it is. Reason being that apply config relies on cron, and our cron tasks cannot run without a home dir. You could alter where it goes, to your normal location and resolve in /etc/passwd or however you manage that. You might also try editing the php files referenced in /etc/cron.d/nagiosxi but I'm not sure how far that will actually get you.

OK. The apply config wizard no longer hangs. I had to stop the autofs service on the Nagios XI host and leave it off to make a /home/nagios directory.

New issue is, and I'll start a new thread if I cannot get this resolved, the apply config wizard is failing. =/

The Auto-Discover Wizard appears to be working now.

One symptom I found was a login issue with NAGIOSQL when I tried repairing the databases.
Once that failed I decided to run /usr/local/nagiosxi/scripts/uninstall_xi.sh and do a full install again, but this time I ensured the autofs service was off and the /home/nagios directory existed.

The auto discovery wizard completed successfully.

Sounds a lot better! Are we clear to close this thread up now?