Fortify SSC Stuck in Maintenance Mode
Our organization is currently using SSC on a Windows server. We restarted the service with Tomcat when prompted in the admin console after making some config changes. When we restart SSC we seem to be stuck in maintenance mode. We've tried restarting Tomcat and SSC every way possible as well as copying over our dB files to the new SSC folder that gets generated, but no matter how we start it we seem to be stuck. Are we missing a step? The documentation doesn't seem to describe how to perform a service restart.
Fortify SSC version 188.8.131.5209
Operating System: Microsoft Windows Server 2019 Datacenter 10.0.17763 N/A Build 17763
Re: Fortify SSC Stuck in Maintenance Mode
What config changes were made? SSC usually goes into maintenance mode when forced via the admin console or it is unable to locate the version.properties file located in the fortify.home\ssc\conf directory (as it assumes this is a new install).
There are a couple of ways to recover from this depending on what put it in this state:
- Run through the initialization again.
- Set maintenance.mode=false in the version.properties file.
- Replace/restore the missing files from the fortify.home\ssc\conf directory.
The datasource.properties file and some fields in the database contain encrypted entries that rely on the secret.key file. So, if you are moving your SSC instance from one computer to another you also need to move the secret.key file...not just your database files.