Acknowledge Error

[uhiadmin]

When I try to acknowledge a down node I get this error below.
I am a little confused on what I need to do.
Any help would be appreciated.


Whoops!

Error: Could not read object configuration data!

Here are some things you should check in order to resolve this error:

Verify configuration options using the -v command-line option to check for errors.
Check the Nagios log file for messages relating to startup or status data errors.

Make sure you read the documentation on installing, configuring and running Nagios thoroughly before continuing. If all else fails, try sending a message to one of the mailing lists. More information can be found at http://www.nagios.org.

--------------------------------------------------------------------------------------------------------------------------------------------

I also noticed that when I try to apply a config I get this error below. But is wont make a config snapshot to review the error.
Applying Configuration

Command submitted for processing...
Waiting for configuration verification............................................................
Configurations failed to write to file.

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.

View a snapshot of this configuration error

[scottwilkerson]

I would run the fixing global permissions procedure
http://library.nagios.com/library/produ ... -nagios-xi

Then go to Configure -> Core Config Manager -> Tools -> Write Config Tool

And click the top 3 go buttons from the top down looking for errors.

If you have no errors you can click the 4th button.

[uhiadmin]

We are still getting the "Acknowledge this problem" in Quick Actions Box in "Host Status Detail " error after applying the global permissions procedure:

Whoops!

Error: Could not read object configuration data!

Here are some things you should check in order to resolve this error:

Verify configuration options using the -v command-line option to check for errors.
Check the Nagios log file for messages relating to startup or status data errors.

Make sure you read the documentation on installing, configuring and running Nagios thoroughly before continuing. If all else fails, try sending a message to one of the mailing lists. More information can be found at http://www.nagios.org.

***Then we tried this:
Then go to Configure -> Core Config Manager -> Tools -> Write Config Tool

And click the top 3 go buttons from the top down looking for errors.

If you have no errors you can click the 4th button.

and the same acknowledgement error shows up. Config verification shows warnings, but no errors.

[lmiltchev]

Run in terminal:

Code: Select all

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

Then also run the following command to begin capturing log output:

Code: Select all

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

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 both, the cmd.txt file and the reconfig.txt that was generated by the above instructions.

[uhiadmin]

Here are the cmd.txt and reconfig.txt file.

[lmiltchev]

Run the following command in terminal and post the output:

Code: Select all

ll /usr/local/nagiosxi/scripts

Also, check if SELinux is running:

Code: Select all

sestutus

If it is running, stop it:

Code: Select all

setenforce 0

then try to apply configuration.

Let me know if this helps.

[uhiadmin]

Last login: Sun Jun 17 10:12:15 2012 from 2ncssw214.uhi.amerco
[root@localhost ~]# ll /usr/local/nagiosxi/scripts
total 2496
-rwxr-xr-x 1 nagios nagios 2757 Jun 12 18:09 backup_xi.sh
-rw-r----- 1 nagios nagios 2758 May 30 22:12 backup_xi.sh~
-rw-r--r-- 1 root root 2340 Jun 14 22:51 cmd.txt
-rwxr-xr-x 1 nagios nagios 649 Jun 12 18:09 export_nagiosql.sh
-rwxr-xr-x 1 nagios nagios 1017 Oct 31 2011 fixperms.sh
-rwxr-xr-x 1 nagios nagios 821 Jun 12 18:09 handle_nagioscore_event.php
-rwxr-xr-x 1 nagios nagios 829 Jun 12 18:09 handle_nagioscore_notification.php
-rwxr-xr-x 1 nagios nagios 429 Jun 12 18:09 import_nagiosql.sh
-rwxr-xr-x 1 nagios nagios 149 Jun 12 18:09 kill_rrdtool.sh
-rw-r--r-- 1 nagios nagios 153 Jun 15 12:08 nagiosql.cookies
-rwxr-xr-x 1 nagios nagios 253324 Jun 12 18:09 nagiosql_defaults.sql
-rw-r----- 1 nagios nagios 22278 Mar 15 16:51 nagiosql.delete.contact
-rwxr-xr-x 1 nagios nagios 970 Jun 12 18:09 nagiosql_delete_contact.php
-rw-r----- 1 nagios nagios 43437 Dec 15 2011 nagiosql.delete.host
-rwxr-xr-x 1 nagios nagios 961 Jun 12 18:09 nagiosql_delete_host.php
-rwxr-xr-x 1 nagios nagios 505 Jun 12 18:09 nagiosql_delete_object.sh
-rw-r----- 1 nagios nagios 31501 Jun 7 2011 nagiosql.delete.service
-rwxr-xr-x 1 nagios nagios 970 Jun 12 18:09 nagiosql_delete_service.php
-rw-r----- 1 nagios nagios 23169 Mar 15 16:51 nagiosql.delete.timeperiod
-rwxr-xr-x 1 nagios nagios 993 Jun 12 18:09 nagiosql_delete_timeperiod.php
-rw-r--r-- 1 nagios nagios 7400 May 31 14:43 nagiosql.export.additional
-rwxr-xr-x 1 nagios nagios 1637 Jun 12 18:09 nagiosql_exportall.php
-rw-r--r-- 1 nagios nagios 4788 Jun 15 12:08 nagiosql.export.monitoring
-rwxr-xr-x 1 root nagios 1323 Jun 12 18:09 nagiosql_importall.php
-rw-r--r-- 1 nagios nagios 1983566 Jun 14 09:19 nagiosql.import.monitoring
-rw-r--r-- 1 nagios nagios 5286 Jun 15 12:08 nagiosql.login
-rwxr-xr-x 1 nagios nagios 1847 Jun 12 18:09 nagiosql_login.php
-rwxr-xr-x 1 nagios nagios 258 Jun 12 18:09 nagiosql_trim_backups.sh
-rwxr-xr-x 1 nagios nagios 515 Jun 12 18:09 nom_create_nagioscore_checkpoint_cond.sh
-rwxr-xr-x 1 nagios nagios 717 Jun 12 18:09 nom_create_nagioscore_checkpoint.sh
-rwxr-xr-x 1 nagios nagios 632 Jun 12 18:09 nom_create_nagioscore_errorpoint.sh
-rwxr-xr-x 1 nagios nagios 784 Jun 12 18:09 nom_restore_nagioscore_checkpoint.sh
-rw-r----- 1 nagios nagios 757 Jun 12 18:09 nom_restore_nagioscore_checkpoint_specific.sh
-rwxr-xr-x 1 nagios nagios 2104 Jun 12 18:09 nom_trim_nagioscore_checkpoints.sh
-rwxr-xr-x 1 nagios nagios 4271 Jun 12 18:09 parse_core_eventlog.php
-rwxr-xr-x 1 nagios nagios 3795 Jun 12 18:09 patch_ndoutils.php
-rw-r--r-- 1 root root 2630 Jun 14 22:34 reconfig.txt
-rw-r--r-- 1 root root 0 Jun 14 09:22 reconfig.txttail
-rwxr-xr-x 1 nagios nagios 597 Jun 12 18:09 reconfigure_nagios.sh
-rwxr-xr-x 1 nagios nagios 1037 Jun 12 18:09 repairmysql.sh
-rwsr-xr-x 1 root root 6798 Jun 13 21:05 reset_config_perms
-rwxr-xr-x 1 nagios nagios 280 Jun 12 18:09 reset_config_perms.c
-rwsr-xr-x 1 root root 691 Jun 13 21:05 reset_config_perms.sh
-rwxr-xr-x 1 nagios nagios 1155 Jun 12 18:09 reset_nagiosadmin_password.php
-rwxr-xr-x 1 nagios nagios 944 Jun 12 18:09 restart_nagios_with_export.sh
-rwxr-xr-x 1 nagios nagios 765 Jun 12 18:09 restore_defaults.sh
-rwxr-xr-x 1 nagios nagios 4010 Jun 12 18:09 restore_xi.sh
-rw-r----- 1 nagios nagios 3039 Jun 12 18:09 uninstall_xi.sh
[root@localhost ~]#

[uhiadmin]

[root@localhost ~]# sestatus
SELinux status: disabled
[root@localhost ~]#
--------------------------------------------------------------------------------------------------------------------------------------------------
[root@localhost ~]# setenforce 0
setenforce: SELinux is disabled
[root@localhost ~]#

[scottwilkerson]

This is starting to sound like database corruption, can I have you run the following procedure
http://library.nagios.com/library/produ ... i-database

You will want to run both databases

Code: Select all

service mysqld stop
/usr/local/nagiosxi/scripts/repairmysql.sh nagios *
/usr/local/nagiosxi/scripts/repairmysql.sh nagiosql *
service mysqld start

Then try applying configuration.

Also, it would be possible that you are out of disk space (or inodes) on a partition
run

Code: Select all

df
cd /usr/local/nagios/libexec
/check_disk -w 10 -c 20