Safely backout of a failed configuration push in RSA Web Threat Detection
2 years ago
Originally Published: 2016-07-20
Article Number
000067197
Applies To
RSA Product Set: Web Threat Detection
RSA Product/Service Type: Mitigator
RSA Version/Condition: 4.6 - 6.0 
 
Issue
A change was made via SIlvercat(Configuration Manger) and when this change was pushed, it caused a failure and now the Configuration manager will not come up in the browser. 

The customer needs to restore the system and roll-back the change. 
Resolution
1.  The way to restore the system is to go to 

       https://,your-wtd-system>:4448/safemode

2.  This will display the following message-- (unless you never saved UIServer Configuration)
-----------------------
Safe mode allows UIServer to come up with a previously-saved UIServer configuration file.

Last saved at: Fri Jul 8 16:37:23 2016.

Please click Ok to proceed
--------------------------

3. Click the OK button and it will bring your configuration back to the previous configuration. 

​

 
Notes
Once the change has rolled back you can also go to the /silvercat/home directory and look at the History of previous changes. 

The reason for the failure to push could be due to wrong syntax of the config file, or an attribute syntax, but now you are able to troubleshoot the cause. 
Don't see what you're looking for?