Dedupe server may become unresponsive or Dedupe service may crash.

book

Article ID: 100048556

calendar_today

Updated On:

Cause

The drive where the DLO application is installed, runs out of space, causing the 'Mindtree StoreSmart Dedupe Server' service to crash.

 

Resolution

  • Ensure there is enough space available on the drive where DLO is installed.
  • Verify the maxActive and maxWait settings have been updated, as discussed in the following article:

After upgrading or installing Desktop and Laptop Option (DLO) 9.3.2 Dedupe Server becomes unresponsive and can no longer be managed.

NOTE: This issue is resolved in DLO 9.4. These settings are automatically updated during DLO 9.4 upgrade.

 

Ways to help reduce the amount of space being used by DLO\Dedupe logs are given below:

  • Remove older catalina logs from path: '..\Program Files\Veritas\Veritas DLO\Dedupe\Tomcat\logs\'  to free up disk space.

 

  • To reduce the catalina log sizes, perform the following steps:

1. Go to "..\Program Files\Veritas\Veritas DLO\Dedupe\Tomcat\conf\"
2. Look for 'logging.properties' file
3. Create a backup of the file --> Copy the file to same folder and rename it to 'logging.properties.BAK'
3. Edit 'logging.properties' file
4. Look for following line:


    .handlers = 1catalina.org.apache.juli.AsyncFileHandler, java.util.logging.ConsoleHandler

.. and replace with


    .handlers = 1catalina.org.apache.juli.FileHandler

5. Save 'logging.properties' file.
6. Restart the 'Mindtree StoreSmart Dedupe Server' service, to read that new logging settings.
 

Issue/Introduction

Dedupe server may become unresponsive or the 'Mindtree StoreSmart Dedupe Server' service may crash.