Linux SLES SP7 AWS becomes unresponsive after installing SEP 16
Article ID: 451747
Updated On:
Products
Issue/Introduction
Linux SLES SP7 AWS becomes unresponsive after installing SEP 16
Environment
SEP 16 installed on Linux version 6.4.0-150700.53.31-default (gcc (SUSE Linux) 7.5.0, stored in AWS
Cause
Our Linux file-activity monitoring performs a file-attribute check while evaluating file-open/execute activity, including on NFS-mounted files. That check has no timeout — if the NFS server or network path becomes unreachable, it can block indefinitely, and because it sits in a shared part of the monitoring pipeline, this can back up file-open/execute processing across the whole system.
The agent's own internal monitoring detects this condition and automatically recovers the affected service — confirmed in your own logs completing in well under a minute, which also clears the broader backlog at the same time. In practice, this is likely to show up as a repeating pattern of brief disruptions rather than one sustained outage.
Resolution
Engineering made available the fix for this issue through Liveupdate on August 5th 2026.
Additional Information
Errors noticed in logs:
"*** Producer Thread is busy (Perm scan count: 0). System may be hung !!!"
"Failed to start Broadcom Endpoint Security Agent for SeaCoreService."
Feedback
