Customers may encounter issues with RHEL VMs in a hung state after Deep Security signature updates. If the DS_agent logs cannot be retrieved as the server is in a hung state, the possible root cause is that secure boot is enabled and the key is not enrolled.
To resolve this issue, customers can follow the recommended action and enroll the Trendmicro key to the OS. For more information, please refer to the following link.
Deep Security20.0
Multiple RHEL VMs are in a hung state after Deep Security signature updates. The DS_agent logs cannot be retrieved as the server is in a hung state.
Sample logs
2024-03-05 11:40:44.154145 [+0800]: [Info/5] | Secure Boot enabled: true | dsa/SecureBoot.lua:161:LogSecureBootStatus | 32522:7F2B45274700:dsa.Scheduler_5904
2024-03-05 11:40:44.154247 [+0800]: [Warning/2] | Key not enrolled: /opt/ds_agent/DS20.der, detail might be logged when Agent is just started | dsa/SecureBoot.lua:171:LogSecureBootStatus | 32522:7F2B45274700:dsa.Scheduler_5904
Customers may encounter issues with RHEL VMs in a hung state after Deep Security signature updates. If the DS_agent logs cannot be retrieved as the server is in a hung state, the possible root cause is that secure boot is enabled and the key is not enrolled.
To resolve this issue, customers can follow the recommended action and enroll the Trendmicro key to the OS. For more information, please refer to the following link.
