VontuMonitorController service starts and then shuts down.

Products

• Data Loss Prevention Enforce

Issue/Introduction

Vontu Monitor Controller service starts but immedieatly shuts down.

 

 

MonitorController0.log

Aug 17, 2012 8:18:38 PM com.vontu.itemcatalog.derby.SQLCallable logAndThrowItemCatalogException

SEVERE: The corrupted Derby database could not be deleted. DerbyDatabase [MONITOR_CONTROLLER\INCREMENTAL_INFO, 54697201].

java.io.IOException: The directory could not be deleted.  [C:\Vontu\Protect\scan\incremental_index\MONITOR_CONTROLLER\INCREMENTAL_INFO]

                at com.vontu.itemcatalog.derby.DerbyDatabase.delete(DerbyDatabase.java:288)

                at com.vontu.itemcatalog.derby.DerbyDatabase.delete(DerbyDatabase.java:266)

                at com.vontu.itemcatalog.derby.SQLCallable.deleteDatabase(SQLCallable.java:232)

                at com.vontu.itemcatalog.derby.SQLCallable.handleGetConnectionException(SQLCallable.java:194)

                at com.vontu.itemcatalog.derby.SQLCallable.getConnection(SQLCallable.java:156)

                at com.vontu.itemcatalog.derby.SQLCallable.call(SQLCallable.java:62)

                at com.vontu.itemcatalog.derby.DerbyDatabase$LockingCallable.call(DerbyDatabase.java:127)

                at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

                at java.util.concurrent.FutureTask.run(FutureTask.java:138)

                at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

                at java.lang.Thread.run(Thread.java:662)

Aug 17, 2012 8:18:38 PM com.vontu.itemcatalog.derby.SQLCallable logAndThrowItemCatalogException

SEVERE: Unable to create table to track servers requiring incremental index changes

java.io.IOException: The directory could not be deleted. 

Resolution

This can happen when any of the files or the folder itself is locked or is in use by another process. The issue can typically be resolved by the follow.  Below is a list of options with increasing impact:

1. Restarting all DLP Services
2. Restarting the system
3. Deleting the Incremental Info database manually (see below)

If you have tried the first 2 steps above and are still getting the error, you may need to delete the Incremental Info database manually using the following steps:

 

1. Shut down the VontuMonitorController service.
2. Delete the folder: <DLP_INSTALL>\Protect\scan\incremental_index\MONITOR_CONTROLLER\INCREMENTAL_INFO
3. Restart the VontuMonitorController service.

 

Note: Removing this directory and restarting the service recreates this directory.