ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

SYSTEM_STATE SQL Deadlocks in Endpoint Protection Manager

book

Article ID: 200842

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

In your SEPM environment, you begin to experience SQL deadlocks that prevent administrators from logging into the SEPM. These deadlocks persist even after they are manually cleared. You can see the following in scm-server.log:

com.sygate.scm.server.metadata.MetadataException: Transaction (Process ID 114) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
 at com.sygate.scm.server.metadata.MetadataManager.getStateMetadata(MetadataManager.java:1632)
 at com.sygate.scm.server.metadata.MetadataManager.getStateMetadata(MetadataManager.java:323)
 at com.sygate.scm.server.configmanager.ConfigManager.getStateObject(ConfigManager.java:1735)
 at com.sygate.scm.server.configmanager.ConfigManager.getSemServerStateObject(ConfigManager.java:6353)
 at com.sygate.scm.server.configmanager.ConfigManager.updateSemServerStateObject(ConfigManager.java:6692)
 at com.sygate.scm.server.task.StateCheckpointTask.run(StateCheckpointTask.java:80)
 at java.base/java.util.TimerThread.mainLoop(Timer.java:556)
 at java.base/java.util.TimerThread.run(Timer.java:506)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 114) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
 at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:262)
 at com.microsoft.sqlserver.jdbc.SQLServerResultSet$FetchBuffer.nextRow(SQLServerResultSet.java:5427)
 at com.microsoft.sqlserver.jdbc.SQLServerResultSet.fetchBufferNext(SQLServerResultSet.java:1758)
 at com.microsoft.sqlserver.jdbc.SQLServerResultSet.next(SQLServerResultSet.java:1016)
 at org.apache.tomcat.dbcp.dbcp2.DelegatingResultSet.next(DelegatingResultSet.java:1160)
 at org.apache.tomcat.dbcp.dbcp2.DelegatingResultSet.next(DelegatingResultSet.java:1160)
 at com.sygate.scm.server.metadata.StateMetadataCollection.getMetadataFromResultSet(StateMetadataCollection.java:674)
 at com.sygate.scm.server.metadata.StateMetadataCollection.getMetadata(StateMetadataCollection.java:87)
 at com.sygate.scm.server.metadata.MetadataManager.getStateMetadata(MetadataManager.java:1630)

In your SQL server logs, you can see that the deadlock occurred when updating the "SYSTEM_STATE" table.

Environment

14.2 RU1, 14.3, and 14.3 MP1 SEPM environment with two or more SEPMs in a site sharing the same SQL database. 

Resolution

This issue is resolved in SEP 14.3 RU1, which contains a fix for the deadlock condition when two SEPMs attempt to update the SYSTEM_STATE table simultaneously. 

Additional Information

      ESCRT-4749