search cancel

DetectionServerDatabase stuck in starting phase

book

Article ID: 162160

calendar_today

Updated On:

Products

Data Loss Prevention Endpoint Prevent Data Loss Prevention

Issue/Introduction

1. On Enforce console, Under System --> Servers --> Overview.
2. DetectionServerDatabase component of any detection server is showing as starting instead of Running.

 

Following are entries in DetectionServerDatabase0.log
-------------------+++++++++++++++++++++++++++++++++++++++++++++++++----------------------------
Apr 2, 2015 5:26:42 PM com.vontu.detectionserver.database.DetectionServerDatabase$HeartbeatSender run
INFO: DetectionServerDatabase is not operational. Will be retried after 10 seconds
Apr 2, 2015 5:26:57 PM com.vontu.detectionserver.database.EmbeddedDerbyServerProvider isOperational
SEVERE: Could not connect to or create the operational database: DetectionServerOperationalDB SQLState: XJ041
java.sql.SQLException: Failed to create database 'DetectionServerOperationalDB', see the next exception for details.
                at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
-------------------+++++++++++++++++++++++++++++++++++++++++++++++++----------------------------
 

Cause

The "SymantecDLPDetectionServerControllerService", also known as the "VontuMonitor" in previous versions of DLP,  has failed to create new copy of the "DetectionServerOperationalDB".

Path for DLP 15.7/15.8:
C:\ProgramData\Symantec\DataLossPreventionDetectionServer\<version>\scan\catalog\DetectionServerOperationalDB.

Path for previous versions:
C:\SymantecDLP\Protect\scan\catalog\DetectionServerOperationalDB.

Resolution

DLP 15.5/15.7/15.8 Instructions:

  1. Stop the "SymantecDLPDetectionServerService" on the Detection Server.
  2. Rename the "DetectionServerOpertionalDB" to "DetectionServerOperationalDB.bak".
    • C:\ProgramData\Symantec\DataLossPrevention\DetectionServer\<version>\scan\catalog\DetectionServerOperationalDB.
  3. Start the "SymantecDLPDetectionServerService" on the Detection Server.
  4. Check the status fo the server in the Enforce Console.

 

DLP 14.6 and 15.0 Instructions:

  1. Stop the "VontuMonitor" service on the Detection Server.
  2. Rename the "DetectionServerOperationalDB" to "DetectionServerOperationalDB.bak".
    • ​​C:\SymantecDLP\Protect\scan\catalog\DetectionServerOperationalDB.
  3. Start the "VontuMonitor" service on the Detection Server.
  4. Check the status of the server in the Enforce Console.

*You may also want to check that these directories have sufficient permissions so that the DB can be read and written to.

Additional Information

You may need to rename another subdirectory if you see a severe message in the filreader log that shows, 

Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (DERBY SQL error: ERRORCODE: 40000, SQLSTATE: XJ041, SQLERRMC: Failed to create database 'CatalogEntryStorage', see the next exception for details.::SQLSTATE: XBM0J)

Ref, 

 

Attachments