Data Center Security Server 6.6: Agent Status: Update Pending, policies don't get applied to agents.
Article ID: 163406
Updated On:
Products
Issue/Introduction
When applying policies to agents (Assign Security Group) the Agent Status remains showing: Update Pending.
sis-agent.x.log
109362 2016-06-01 09:50:45.319 [ERROR] [UpdateHandler:66] [{HOSTNAME.EN_US}:{IP_ADDRESS.EN_US}/windows] [SQL:1205] Transaction (Process ID 63) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
java.sql.SQLException: Transaction (Process ID XX) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
sis-console.x.log
25931 2016-05-19 15:00:55.410 [ERROR] [ExecuteHandler:272] [SQL:1205] Transaction (Process ID 61) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
java.sql.BatchUpdateException: Transaction (Process ID 61) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
sis-restapi.x.log
14382 2016-05-13 14:12:34.253 [WARN ] [SASecurityGroupsController:234] An error was encountered while attempting to execute the database query
com.symantec.sis.server.exception.ServerException: [107] An error was encountered while attempting to execute the database query
{
"Sql": "DELETE FROM SECURITYGROUP_POLICY_MAP WHERE SECURITYGROUPRID = ? AND ELEMENTRID = ? AND ELEMENTTYPE = ? {1501, 2922, 'app.cust.policy'}"
"SQL Code": 1205
}
....
Caused by: java.sql.SQLException: Transaction (Process ID 70) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
.... xx more
curstate.txt (obtained by the "getserverinfo.bat" script)
-- Running Processes [tasklist /v] --
Image Name PID Session Name Session# Mem Usage Status User Name ============ === =========== ======= ========== ======= ========
SISManager.exe 848 Services 0 1,210,044 K Unknown N/A
Cause
The DCS:SA 6.6 32bit java based SISManager.exe service can only use up to 1.2Gb of memory. In addition, some SQL queries used by the DCS manager's internal workings are not optimal.
Resolution
Upgrade to DCS:SA 6.6 MP1. DCS:SA 6.6 MP1 comes with a 64bit JVM which by default is configured to use up to 4Gb of memory. In addition, during the upgrade to 6.6MP1 the database is upgraded too and several database optimizations are implemented preventing deadlocks.
Feedback
