Summary
You are unable to create a Deep Security Agent (DSA) diagnostic package due to a timeout in a high-load environment.
The server0.log file shows the following message:
Sep 13, 2013 9:30:13 AM com.thirdbrigade.manager.core.diagnostic.AgentDiagnosticPackageBuilder addAgentDiagnostic
SEVERE: Unable to get the agent diagnostic package in the maximum amount of time
Sep 13, 2013 9:30:13 AM com.thirdbrigade.manager.core.diagnostic.AgentDiagnosticPackageBuilder addAgentDiagnostic
FINE: No file exists
Sep 13, 2013 9:30:13 AM com.thirdbrigade.manager.core.diagnostic.DiagnosticPackageBuilder close
INFO: Closing internal log...
SEVERE: Unable to get the agent diagnostic package in the maximum amount of time
Sep 13, 2013 9:30:13 AM com.thirdbrigade.manager.core.diagnostic.AgentDiagnosticPackageBuilder addAgentDiagnostic
FINE: No file exists
Sep 13, 2013 9:30:13 AM com.thirdbrigade.manager.core.diagnostic.DiagnosticPackageBuilder close
INFO: Closing internal log...
Details
The issue occurs when you exceed the default 10-minute threshold. To resolve the issue, extend the timeout value:
- As an administrator, open the command line on the DSM server.
- Navigate to the DSM installation folder using this command:
cd "c:\Program Files\Trend Micro\Deep Security Manager"
- Run this command to change the timeout value to 20 minutes:
dsm_c -action changesetting -name configuration.diagnosticMaxWaitForAgentDiagnostic -value 1200000
