Application Real-Time Monitoring Service:Troubleshoot ARMS agent manual installation failures

Symptom

The LicenseKey is invalid error appears in the logs in the ArmsAgent/log/ directory.

Cause

The ARMS agent installation package is region-specific. ARMS endpoint information is encapsulated in the package. If you download the package for a region that differs from the region where your application runs, the agent cannot connect to the correct ARMS endpoint.

Solution

1. Verify which region your application runs in.

2. Download the ARMS agent installation package for that specific region. For the download links, see Manually install an ARMS agent.

3. Replace the existing agent directory with the newly downloaded package.

4. Restart your application.

Symptom

The LicenseKey is invalid error appears in the agent logs in the ArmsAgent/log/ directory.

Cause

The license key specified in the startup command does not match the license key assigned to your application in the ARMS console.

Solution

1. Log on to the ARMS console.

2. In the left-side navigation pane, choose Application Monitoring > Application List.

3. On the Applications page, click the name of your application and find the license key.

4. Compare the license key in the console with the value of the -Darms.licenseKey parameter in your startup command. Make sure they are identical.

5. If the values differ, update the startup command with the correct license key and restart your application.

Symptom

The ARMS agent fails to start or does not report data after the application starts.

Cause

Certain early JDK 1.8 versions, specifically 1.8.0_25 and 1.8.0_31, have known compatibility issues that prevent the ARMS agent from functioning correctly.

Solution

1. Check your JDK version:

   java -version

2. If the output shows version 1.8.0_25 or 1.8.0_31, upgrade to a later JDK version.

3. For a complete list of supported JDK versions and frameworks, see Java components and frameworks supported by ARMS.

Symptom

After the application starts, the logs subdirectory does not exist in the ArmsAgent directory.

Cause

The aliyun-java-agent.jar file was not loaded by the JVM. This typically occurs when the ArmsAgent directory has incorrect file permissions, or when the -javaagent parameter in the startup command points to a wrong path.

Solution

1. Verify that the -javaagent parameter in your startup command points to the correct JAR file:

   # Example: check the actual process command line
   ps -ef | grep java | grep javaagent

2. Verify that the ArmsAgent directory and its contents are readable by the user that runs the application:

   ls -la /path/to/ArmsAgent/

3. If the permissions are incorrect, fix them:

   chmod -R 755 /path/to/ArmsAgent/

4. Restart the application and check whether the logs subdirectory is created in the ArmsAgent directory.