Nagios Support Forum

Hi,

We are having some problems running the apply configuration in core. The issues seem to have started today after I ran through a new “windows server creation” wizard in XI but cancelled instead of finishing at the end.

Unfortunately I was not really paying attention of the server name but either put junk in it or 127.0.0.1

If I run a

/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

It completes with out problems

Read object config files okay...

Running pre-flight check on configuration data...

Checking services...
Checked 728 services.
Checking hosts...
Checked 136 hosts.
Checking host groups...
Checked 13 host groups.
Checking service groups...
Checked 24 service groups.
Checking contacts...
Checked 11 contacts.
Checking contact groups...
Checked 3 contact groups.
Checking service escalations...
Checked 0 service escalations.
Checking service dependencies...
Checked 96 service dependencies.
Checking host escalations...
Checked 0 host escalations.
Checking host dependencies...
Checked 0 host dependencies.
Checking commands...
Checked 85 commands.
Checking time periods...
Checked 17 time periods.
Checking for circular paths between hosts...
Checking for circular host and service dependencies...
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors: 0


However If I run the Apply configuration from the gui it never completes.

Applying Configuration

Command submitted for processing...
Waiting for configuration verification............................................ {repeats forever….}

I noticed a FAQ relating to an older version of XI which suggested increasing some php values which I’ve done but it made no difference.

http://support.nagios.com/wiki/index.ph ... _Completes

I’ve also rebooted the system.

It looks like it is still monitoring ok but I’m unable to add new devices

The version we have is Nagios XI 2011R3.3 Copyright © 2008-2013 Nagios Enterprises, LLC.


Has anyone got any ideas?


Cheers

Simon

Lets start by looking for php errors. Do a running tail on the apache error log: Now try to "apply configuration" and post the output here.

Additionally, follow the following steps below from the faq: http://support.nagios.com/wiki/index.ph ... n_Problems
Then also run the following command to begin capturing log output:
And attempt to Apply Configuration from the web interface. After the browser has returned some output to the screen, press Ctrl+C to stop the log tail, and post the cmd.txt file and the reconfig.txt that was generated by the above instructions.

[root@brli149a services]# tail -f /var/log/httpd/error_log
[Wed Apr 03 15:49:39 2013] [notice] caught SIGTERM, shutting down
[Wed Apr 03 15:53:15 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed Apr 03 15:53:15 2013] [notice] Digest: generating secret for digest authentication ...
[Wed Apr 03 15:53:15 2013] [notice] Digest: done
[Wed Apr 03 15:53:16 2013] [notice] Apache/2.2.3 (Red Hat) configured -- resuming normal operations
[Wed Apr 03 16:02:50 2013] [notice] caught SIGTERM, shutting down
[Wed Apr 03 16:02:50 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed Apr 03 16:02:50 2013] [notice] Digest: generating secret for digest authentication ...
[Wed Apr 03 16:02:50 2013] [notice] Digest: done
[Wed Apr 03 16:02:50 2013] [notice] Apache/2.2.3 (Red Hat) configured -- resuming normal operations

and

[root@brli149a services]# cd /usr/local/nagiosxi/scripts
[root@brli149a scripts]# ./reconfigure_nagios.sh &> reconfig.txt
[root@brli149a scripts]# tail -f /usr/local/nagiosxi/var/cmdsubsys.log &> cmd.txt

[root@brli149a scripts]#

nothing in the cmd.txt after 5mins

Cheers

Simon

Post 2:

Just noticed the following line in the reconfig.txt from the commands you suggested before. Is this relavent

Processing object config file '/usr/local/nagios/etc/contacts.cfg'...
Warning: Duplicate definition found for contact 'xi_default_contact' (config file '/usr/local/nagios/etc/contacts.cfg', starting on line 146)
Error: Could not add object property in file '/usr/local/nagios/etc/contacts.cfg' on line 147.
Error processing object config files!

What is on line 147 in the "/usr/local/nagios/etc/contacts.cfg"?

Strange on this

service_notifications_enabled 1
use xi_contact_generic
}

###############################################################################
#
# Contact configuration file
#
# END OF FILE
#
###############################################################################
146,1 Bot

Line 146 is the first line of the end of file # block

Merged posts again:

also if i search the file for xi_default_contact i get...

E486: Pattern not found: xi_default_contact

Top of the file says this

###############################################################################
#
# Contact configuration file
#
# Created by: Nagios QL Version 3.0.3
# Date: 2013-03-05 11:00:19
# Version: Nagios 3.x config file
#
# --- DO NOT EDIT THIS FILE BY HAND ---
# Nagios QL will overwite all manual settings during the next update
#
###############################################################################

What would happen if i delete the file and re- run the Apply Configuration would it get recreated?

Have you made any changes in the configs in the static directory? Run the following command and show the output:

Here's the output you requested from us. The issues seem to have started after running a dummy install of a windows device. I was trying to document some so of the process we have been using. Instead of completeing the wizard by clicking the finish button at the end of the wizard i clicked cancel. We have been having the problems since.

[root@brli149a ~]# cat /usr/local/nagios/etc/static/xitemplates.cfg | grep xi_contact
# name xi_contact_generic
# contactgroups xi_contactgroup_all
contacts xi_contact_default

Email us your latest configuration snapshot at [email protected], and type: "Re: Apply Configuration... Verification stall in GUI" in the subject field. It would be probably easier to continue troubleshooting your issue via emails. Thank you!