From: Dan M <da...@st...> - 2013-07-31 14:22:38
|
I am in the process of moving an existing installation of nagios 3.2.1 with Centreon to nagios 3.5.0 with Monarch 2.5.0. The old nagios installation had it's config files kind of jacked up due to a handful of admins working with it over the years, but I finally for everything tidied up to the point that I can load the config files and do a pre-flight test with no errors and no warnings. I can also commit with apparently no issues, but after printing out the results of the "nagios -v nagios.cfg" and showing 0 warning and 0 errors, but still reports an error. Specifically, the last few lines of the "commit" screen show: Total Warnings: 0 Total Errors: 0 Things look okay - no serious problems were detected during the pre-flight check. Running configuration check... CONFIG ERROR! Restart aborted. Check your Nagios configuration. So, what would seem to be the problem here? I'll dig in to the source code and see if I can figure it out for myself, but if someone else has seen this before I'd appreciate a pointer. Also, a minor issue. In the "nagios main configuration" screen I still see lines for aggregate_status_updates, downtime_file, and comment_file variables. These are no longer needed in nagios 3.5.0 (the preflight check indicates that all status file updates are now aggregated, and downtime entries and comments are now stored in the status and retention files. |