Warning: Failed to clean up LiveUpdate downloaded content
Article ID: 234874
Updated On:
Products
Issue/Introduction
On occasion, the Symantec Endpoint Protection Manager (SEPM) will display the following warning: Failed to clean up LiveUpdate downloaded content.
The following will be logged in the PackagePublisherTask-0.log:
2022-02-09 06:30:05.024 THREAD 34 WARNING: PackageTask>> is SEPM just started: false
2022-02-09 06:30:05.024 THREAD 34 WARNING: PackageTask>> isIdcEnabled in file system: false
2022-02-09 06:30:05.040 THREAD 34 WARNING: PackageTask>> idcEnabled in SEPM root property: false
2022-02-09 06:30:05.040 THREAD 34 WARNING: PackageTask>> has Idc setting changed: false
2022-02-09 06:30:06.946 THREAD 34 WARNING: PackageTask>>doContentCleanup : Clean up content: {EF89727B-85D9-4608-A2DB-22FF1AB39A3C}:{67F66706-F04B-4432-9947-F8354949D2A6}:211208002
2022-02-09 06:30:06.946 THREAD 34 WARNING: (rep lock) locking guid=6028C6E625754ECE4312D41CB963A039, tableName=BASIC_METADATA
2022-02-09 06:30:06.962 THREAD 34 WARNING: (rep lock) locked guid=6028C6E625754ECE4312D41CB963A039, tableName=BASIC_METADATA
2022-02-09 06:30:07.493 THREAD 34 WARNING: Updated LuDownloadedContentArray.xml
2022-02-09 06:30:08.212 THREAD 34 WARNING: (rep lock) locking guid=6028C6E625754ECE4312D41CB963A039, tableName=BASIC_METADATA
2022-02-09 06:30:08.228 THREAD 34 WARNING: (rep lock) locked guid=6028C6E625754ECE4312D41CB963A039, tableName=BASIC_METADATA
2022-02-09 06:30:08.759 THREAD 34 WARNING: Updated LuDownloadedContentArray.xml
2022-02-09 06:30:11.244 THREAD 34 WARNING: Content cleanup failed: com.sygate.scm.server.util.ServerException: Unexpected server error.
com.sygate.scm.server.metadata.MetadataException: Transaction (Process ID 152) 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.getMetadata(MetadataManager.java:1651)
at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:403)
at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:428)
at com.sygate.scm.server.configmanager.ConfigManagerCache.getTopLevelObject(ConfigManagerCache.java:293)
at com.sygate.scm.server.configmanager.ConfigManager.getTopLevelObject(ConfigManager.java:446)
at com.sygate.scm.server.configmanager.ConfigManager.getLuDownloadedContentArray(ConfigManager.java:3835)
at com.sygate.scm.server.util.LuServerUtility.getDownloadedContentArray(LuServerUtility.java:991)
at com.sygate.scm.server.util.LuServerUtility.getDownloadedContentArray(LuServerUtility.java:948)
at com.sygate.scm.server.liveupdate.ContentCleaner.fetchLatestContentArray(ContentCleaner.java:758)
at com.sygate.scm.server.liveupdate.ContentCleaner.<init>(ContentCleaner.java:96)
at com.sygate.scm.server.liveupdate.ContentsCleaner.processAllContentTypes(ContentsCleaner.java:397)
at com.sygate.scm.server.liveupdate.ContentsCleaner.processAll(ContentsCleaner.java:102)
at com.sygate.scm.server.util.LuServerUtility.cleanupLuDownloadedContent(LuServerUtility.java:1570)
at com.sygate.scm.server.task.PackageTask.publishSecurityContents(PackageTask.java:985)
at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:637)
at java.base/java.util.TimerThread.mainLoop(Timer.java:556)
at java.base/java.util.TimerThread.run(Timer.java:506)
Cause
The Content Cleanup is triggered by the Package Publisher Task. The error will occur if multiple SEPMs in the site are running the task at the same time causing a deadlock.
Resolution
The Package Publisher Task runs every 2 seconds. The content will be cleaned up successfully on the next attempt.
Additional Information
ESCRT-7869
Feedback
