Not able to move the DLP agent from one group to another
search cancel

Not able to move the DLP agent from one group to another

book

Article ID: 241847

calendar_today

Updated On:

Products

Data Loss Prevention Endpoint Prevent Data Loss Prevention Core Package

Issue/Introduction

Unable to move the DLP agent from one group to another.

Error on Enforce console: Unable to move (1) selected agents to "groupname"

Error in localhost Logs: 

File: Enforce/logs/tomcat/localhost
Date: 5/4/2022 10:39:40 AM
Thread: 59441
Level: WARNING
Source: com.vontu.manager.admin.endpoint.health.TroubleshootController
Message: Unable to move agents to selected group "groupname"
Cause:
com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast instance is not active!com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast instance is not active!

Environment

15.x

Cause

While we do not see any outofmemory errors in the localhost log, this error is caused due to less java heap size for the DLP Manager service. 

Resolution

Increase the java heap size of the DLP manager service. 

 

1. On Enforce Server, Edit the file SymantecDLPManager.conf

Linux: 

/opt/Symantec/DataLossPrevention/EnforceServer/Services

Windows: 

C:\Program Files\Symantec\DataLossPrevention\EnforceServer\Services

Note: Ensure you take a backup of the SymantecDLPManager.conf file before making any changes. 

 

2. Default value for Java Heap size in SymantecDLPManager.conf:

# Initial Java Heap Size (in MB)

wrapper.java.initmemory = 1378

# Maximum Java Heap Size (in MB)

wrapper.java.maxmemory = 2048

 

New values that needs to be configured:

# Initial Java Heap Size (in MB)

wrapper.java.initmemory = 2048

# Maximum Java Heap Size (in MB)

wrapper.java.maxmemory = 4096

 

3. After making the above changes, Restart all DLP services in order. 

Restart DLP Enforce services in the correct order

 

4. You should be able to change the DLP agent group now without any error.