Configuration Snapshot restore is scheduled.

[benjaminsmith]

Hello @TBT,

Trying to restore a config snapshot and the following message is displayed: "Configure snapshot restore has been scheduled."
Also, in the Audit Log states: User restored system to config snapsnot '1549562589'. But I do not see the changes restored.

Your permission settings and sudoers file look correct. I spoke with a developer about this case, and the error message, "Configure snapshot restore has been scheduled.", can occur on a busy system. However, the reason you did not see the changes, is that you must select Apply Configuration for the configuration change to take effect.

Additionally, the errors shown in the log file are not always an indication of a failure. At the bottom of the log you'll notice that the restore did complete and return a proper exit code.

Restoring CCM databases...
Restore Complete.
OUTPUT=Restore Complete.
RETURNCODE=0

The roll-back most likely occurred when the reconfigure script was run earlier. Let me know if you have any questions or have any issues with restoring the configuration.

[TBT]

The restore appears to have applied.

So, what is the schedule based on... time or system resources, please clarify?

When scheduled will the configuration automatically be applied once restored, and if not how does one know when to manually apply configuration?

Perhaps Nagios should revise the notification for cases where the restore is scheduled. It gave no indication that apply configuration was still required or an indication as to status of the scheduled task completion.

Additionally, the documentation made no reference to this either. Rather confusing.

Thanks for the assistance.

[benjaminsmith]

Hi @TBT,

Some good questions. I just spoke to our lead developer and we'll probably re-work this process for Nagios XI 6. Presently, this is how it works. When you select restore, Nagios XI will unpack your archive CCM database, and re-load this into the CCM Manager. At this point, the admin can review the previous config and make any changes, then select Apply Configuration to re-start Nagios with the restored configuration. We don't automatically apply configuration as most users would like to review the changes first.

In this particular case, it took longer (probably due to disk I/O) than what has been set in the timer to re-load the archive database in the CCM Manager and you received the "Configuration snapshot restore has been scheduled message".

Currently, you can review the the log tail -f /usr/local/nagiosxi/var/cmdsubsys.log to find out if the restore has completed. I'll file a feature request on your behalf with your suggestions about adding notifications and status of task completion.

Let know if you have any other questions.