To resolve the error, identify first the cause of the issue by checking the server0.log. Below are the possible causes of the issue and their respective solutions:
Note that this error has many possible causes aside from the two causes listed below. For other possible reasons why the error occurs, check the related server0 logs.
The server0.log shows the following error:
SEVERE: Unable to initialize java.lang.Exception: Insufficient Disk Space at com.thirdbrigade.manager.core.Core.checkDiskSpace(Core.java:2033) at com.thirdbrigade.manager.core.Core.startFull(Core.java:390) at com.thirdbrigade.manager.core.Core.startFull(Core.java:261) at com.thirdbrigade.manager.webclient.initialization.InitializeServlet.init(InitializeServlet.java:65) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1206) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1026) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4421) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4734) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057) at org.apache.catalina.core.StandardHost.start(StandardHost.java:840) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at org.apache.catalina.startup.Embedded.start(Embedded.java:825) at com.thirdbrigade.manager.service.Tomcat.startTomcat(Tomcat.java:134) at com.thirdbrigade.manager.service.DSMService$WorkerThread.run(DSMService.java:226
As shown by server0.log, the issue occurs because the DSM has insufficient disk space, which makes the Apache Tomcat Web Server unable to start.
To resolve the issue, make sure there is enough available disk space to start the console.
The server0.log shows the following:
INFO: No global web.xml found Jan 04, 2017 3:35:46 PM com.thirdbrigade.manager.core.Core startFull INFO: ThID:15Initiating core full startup... Jan 04, 2017 3:36:11 PM com.thirdbrigade.manager.core.Core processInitDatabase WARNING: ThID:15|TID:0|TNAME:Primary|UID:-1|UNAME:|Unable to connect to the database. Retrying in 10 seconds java.sql.SQLException: Network error IOException: Connection timed out: connect at net.sourceforge.jtds.jdbc.JtdsConnection.<init>(JtdsConnection.java:437)
To resolve the issue:
- Check the communication between the database and the DSM, and verify if SQL server is available.
- Restart the Deep Security Manager service.
- Refresh the DSM console. You should now be able to properly access it.