Page 2 of 2
Re: Major problem with CCM changes not being committed
Posted: Wed Sep 21, 2011 5:49 pm
by cwscribner
Okay so I finally got some changes to commit. I reversed several of the most recent changes and ran ./reconfigure_nagios.sh. This committed some more devices but several are still showing "Sync Missed" and "Out of Sync". I restarted nagios, nagiosxi, httpd, and mysqld and ran ./reconfigure_nagios.sh. I also ran reset_config_perms and I attempted that fix_global_perms.py script but it requires arguments that I'm unfamiliar with.
Re: Major problem with CCM changes not being committed
Posted: Thu Sep 22, 2011 10:51 am
by mguthrie
Just to make sure our bases our covered, can you make sure your system time is synced correctly, and then lets also make sure you've got enough PHP memory reserved for the large amount of configs that are being added.
Code: Select all
yum install ntp
ntpdate pool.ntp.org
Increase PHP's memory limits:
http://support.nagios.com/wiki/index.ph ... _Completes
Re: Major problem with CCM changes not being committed
Posted: Thu Sep 22, 2011 3:46 pm
by cwscribner
NTP installed and time updated. The offset was -0.005
Code: Select all
max_execution_time = 120
max_input_time = 120
memory_limit = 512M
Re: Major problem with CCM changes not being committed
Posted: Fri Sep 23, 2011 11:21 am
by mguthrie
Can you check the very bottom of the php.ini file and make sure the memory limit isn't being overridden by a second setting that's been appended?
I'm a little bit stumped as to the inconsistency of the configurations being written. Would you be interested in a remote session either this afternoon or Monday to look at this? Send me a PM with times that might work if you're interested.
Re: Major problem with CCM changes not being committed
Posted: Fri Sep 23, 2011 11:48 am
by cwscribner
The memory parameters only show up once in php.ini.
I would definitely be interested in a remote session. The server in question is at a client site so I'll have to get clearance first. I just did an upgrade and encountered a new issue. I'll open a new thread.
Re: Major problem with CCM changes not being committed
Posted: Fri Sep 23, 2011 3:57 pm
by mguthrie
Ok, we'll continue discussion by email or PM and I'll post any solutions I find here.
Re: Major problem with CCM changes not being committed
Posted: Mon Sep 26, 2011 4:15 pm
by mguthrie
Just to follow up on this thread for future users, the issues on the system were resolved with the following:
- Fixing permissions issues. The apache user owned several files and directories under the /usr/local/nagios/var directory. Nagios wasn't able to create a new objects.cache file so new object configurations couldn't be built.
Solution: Ran instructions from the following doc:
http://assets.nagios.com/downloads/nagi ... ssions.pdf
- Due to the larger installation size, and a large amount of new hosts that hadn't yet been written to file, the PHP timeout and memory limits needed to be increased to much higher levels than normal. Memory limit was increased to 768M and the timeout was set to 240 seconds in the php.ini file.
- There was also a configuration error related to a hostgroup being defined in the Core Config Manager, but the group was not set as "active," so it was not being written to file. This group was being referenced by a host, causing a config error, and Nagios XI would roll back the configuration to the last known working config.