Home » Categories » Products » Nagios XI » Troubleshooting » Common Problems

Nagios XI - 2014 Upgrade Issue - CONFIG ERROR

Overview

The most common error experienced during the XI 2014 upgrade process is the following core config error:

CONFIG ERROR! Restart aborted. Check your Nagios configuration.

 

XI 2014 introduced some new mechanisms to guard against and remove the dreaded "ghost config" errors as well as some issues pertaining to escalations/dependencies. Due to these changes though, you may receive the above error during the upgrade, immediately after the installation of nagios core 4.

The most common resolution requires fixing the config errors in the CCM, writing and verifying the config, and then re-running the upgrade script. Enumerated steps are below:

  1. Run ./upgrade until the error occurs. Do not roll back the VM or installation. XI will now be half-upgraded and the config errors will have to be resolved before the upgrade can continue.

  2. In XI, browse to the CCM: Configure > Core Config Manager > Tools > Write Config Files.

  3. Click "Write" and then "Verify". You should receive at least one error. The text of the error should be fairly descriptive concerning which object is having issues and what those issues potentially are. If you do not see any descriptive errors, you may have issues with escalations or service/host dependencies. You will most likely want to de-activate these definitions until the upgrade is complete.

  4. Resolve the error in the Core Config Manager (CCM). An easy method is to de-activate the config item it is talking about as this will let you proceed past the problem and continue with the upgrade.

  5. Once the detected errors are resolved, re-run the "Write" and "Verify" process from the "Write Config Files" tool. Resolve any further errors in the CCM, repeating the process above as many times as necessary until all config errors are resolved.

  6. Only when the "Verify" process completes without and error should you proceed.

  7. Click "Apply Configuration" - it should complete without error at this point.

  8. Now, return to the shell and re-run ./upgrade. The upgrade process should continue past the core 4 upgrade and nagios process restart.

 

A more detailed explanation of the Write and Verify steps are outlined in this article:

Configuration Verification Failed

 

Final Thoughts

For any support related questions please visit the Nagios Support Forums at:

http://support.nagios.com/forum/

0 (0)
Article Rating (No Votes)
Rate this article
  • Icon PDFExport to PDF
  • Icon MS-WordExport to MS Word
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
Nagios XI - Oracle Services Critical After Nagios XI Upgrade
Viewed 929 times since Wed, Jan 27, 2016
Nagios XI - Missing localhost Alerts
Viewed 1929 times since Sun, Nov 5, 2017
Nagios XI - Profile Build Failed
Viewed 1848 times since Tue, Aug 2, 2016
Nagios XI - Upgrade errors - root.crontab.orig: cannot overwrite existing file
Viewed 806 times since Tue, Jan 26, 2016
Nagios XI - Event Data Is Stale
Viewed 963 times since Wed, Jan 27, 2016
CCM says unapplied changes exist, but none listed
Viewed 877 times since Mon, Feb 27, 2017
Nagios XI - SNMP MIB Upload Problems
Viewed 1706 times since Mon, Apr 10, 2017
Nagios XI - Some BPI Checks Show "Unknown BPI Group Index" After Upgrade
Viewed 386 times since Wed, Sep 18, 2019
Nagios XI - Empty Screen for Wizard, Component, Dashlet
Viewed 1038 times since Wed, Jan 27, 2016
Nagios XI - Modifying The Contents Of /usr/local/nagios/etc
Viewed 940 times since Tue, Jan 26, 2016