>

Disabling .mdmp file creation on SteelCentral AppInternals 10.x agent which are causing disk to fill up

Categories: SteelCentral AppInternals (AppInternals Xpert)
Solution Number: S33405

Issue

We are running SteelCentral AppInternals 10.x on our Windows servers and Agent crashes are creating huge files in /bin and /lib directory which is causing our disk to fill up. We are seeing several .mdmp files in the above locations.

How can we disable the .mdmp creation for the agent if there is a crash?

Solution

The .mdmp file are created in /bin and /lib directory when there is an agent crash. It will also leave an hs_err<PID>.log file for each dump.
Sometimes these files might fill the disk space on the agent and hence we might want to disable the .mdmp files from being created if there is a crash.

Below are the steps which you can do disable the .mdmp creation

For dsa.exe
  1. Navigate to below location
    <install_dir>/Panorama/hedzup/mn/metadata
  2. Edit the file named - process.dsa.json
  3. Include the below entry that is highlighted
{
                "version":"1.0",
                "name":"dsa",
                "start":true,
                "restart":true,
    "restartAfterRequestMSecs" : 5000,
    "restartAfterFailureMSecs" : 30000,
                "restartFailureAttempts" : 2,
                "restartMaxFailureMSecs" : 3600000,
                "restartResetFailCountMSecs" : 300000,
                "upgrade":true,
                "command" : [
                                "dsa",
                                "-d"
                ],
                "osSpecific" : {
        "Windows" : {
            "command" : [
                "DsaServer.exe",
                "-d","-XX:-CreateMinidumpOnCrash"
            ]
        }
    }
}



For agentrt.exe
  1. Navigate to below location
    <install_dir>/Panorama/hedzup/mn/metadata
  2. Edit the file named - process.agentrt.json
  3. Include the below entry that is highlighted
{
                "version":"1.0",
                "name":"agentrt",
                "start":true,
                "restart":true,
                "upgrade":true,
                “environment”: { “JAVA_TOOL_OPTIONS”: ”-XX:-CreateMinidumpOnCrash” },
                "command" : [
                                "agentrt"
                ],
                "osSpecific" : {
        "Windows" : {
            "command" : [
                "agentrt_agent.exe",
                "-c"
            ]
        }
    },
                "dependencies" : [
                                "dsa"
                ]
}


For controller.exe
NOTE: System Reboot might be required if you are doing the below change!
  1. From command prompt navigate to below location
    <install_dir>/Panorama/hedzup/mn/bin
  2. Execute the below command
    >controller.exe -u
  3. Once the service is successfully removed, execute the below command
    NOTE: Make sure you copy the command into a text editor to make sure there are no trailing spaces or unexpected characters. The below command might fail with a "Serivice marked for deletion" message at which point a system reboot might be required to continue
  4. >HostService.exe -i AgentController "Riverbed SteelCentral AppInternals Agent Controller" "Riverbed SteelCentral AppInternals Agent Controller" -je com.riverbed.controller.Controller  -w .\..\bin\ -stack 0 -jre_path .\..\jre\ -jvm_type server -cp  ".\..\lib\service.jar;.\..\lib\controller.jar;.\..\lib\jackson-core-2.8.9.jar;.\..\lib\jackson-databind-2.8.9.jar;.\..\lib\jackson-annotations-2.8.9.jar;.\..\lib\slf4j-api-1.7.21.jar;.\..\lib\logback-core-1.1.7.jar;.\..\lib\logback-classic-1.1.7.jar" -jvm_options "-XX:-CreateMinidumpOnCrash -Xmx50m -Dlogback.configurationFile=.\..\data\controller.xml"
  5. The service should be installed successfully
  6. Execute the below command
    >HostService.exe -start AgentController
The controller should start with the new options at this time.

**Please open a technical support case if you run into any issues or have any questions
 

Environment

Windows, SteelCentral AppInternals 10.x
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Last Modified: 2019-05-09
Can't find an answer? Create a case