Hello! I am ejmorrow's co-worker and am putting "another pair of eyes" on this. We seem to have one large issue at the moment and that is that nagios now will not start at all because of some object config file issues. So once I can get this started again, I hope to start from square one.
Here is what we are currently getting trying to start up "service nagios start":
[root@esnagxiprd01 storebacknagiosxi]# service nagios start
Starting nagios:
Nagios Core 4.2.4
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 12-07-2016
License: GPL
Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Error: Unexpected EOF in file '/usr/local/nagios/etc/services/esappj64.uits.iupui.edu.cfg' on line 283 - check for a missing closing bracket.
Error: Failed to locate check_period 'xi_timeperiod_24x7' for host 'absappp1.uits.iupui.edu'!
Error: Could not register host (config file '/usr/local/nagios/etc/hosts/absappp1.uits.iupui.edu.cfg', starting on line 16)
Error processing object config files!
***> One or more problems was encountered while processing the config files...
Check your configuration file(s) to ensure that they contain valid
directives and data defintions. If you are upgrading from a previous
version of Nagios, you should be aware that some variables/definitions
may have been removed or modified in this version. Make sure to read
the HTML documentation regarding the config files, as well as the
'Whats New' section to find out what has changed.
I then attempted to restore a configuration snapshot and the CCM hangs at Waiting for configuration verification.(..........).
Once we can get nagios to at least start, I would then run down what we are seeing.
Try this procedure to see if you can fix the configuration error that is keeping the nagios service from starting.
Go to the Core Config Manager
Under "Tools", click "Write Config Files" or if you are running a newer versions of XI, The menu is called "Config File Management"
Click the click the "Write" button, then the "Delete" button then click the "Write" button and then the "Verify" button
If you get any errors, resolve them and click on the "Delete" button, "Write", "Verify" until all of the errors are resolved.
Click the Apply Configuration link and click the "Apply Configuration" button after all of the errors are resolved.
After this, the nagios service should be running.
Be sure to check out our Knowledgebase for helpful articles and solutions!
I just tried doing that. Once the files were written out, the notification to apply configuration appeared. It is hanging on "Waiting for configuration verification."(..........).
We seem to still not be starting and it is complaining about the same files:
[root@esnagxiprd01 perfdata]# service nagios start
Starting nagios:
Nagios Core 4.2.4
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 12-07-2016
License: GPL
Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Error: Unexpected EOF in file '/usr/local/nagios/etc/services/esappj64.uits.iupui.edu.cfg' on line 283 - check for a missing closing bracket.
Error: Invalid max_check_attempts value for host 'localhost'
Error: Could not register host (config file '/usr/local/nagios/etc/hosts/localhost.cfg', starting on line 16)
Error processing object config files!
***> One or more problems was encountered while processing the config files...
Check your configuration file(s) to ensure that they contain valid
directives and data defintions. If you are upgrading from a previous
version of Nagios, you should be aware that some variables/definitions
may have been removed or modified in this version. Make sure to read
the HTML documentation regarding the config files, as well as the
'Whats New' section to find out what has changed.
[root@esnagxiprd01 perfdata]# service nagios status
No lock file found in /usr/local/nagios/var/nagios.lock
What is our next step? We have the following config snapshots available to us if we have to attempt a fallback: