CCE Access FAQs and Solutions

Agent Fails to Be Installed Through CCE, and No Log Is Printed

Cause: JAVA_TOOL_OPTIONS does not take effect. The user starts the service using sudo. The script started by using sudo ignores all environment variables.

Solution: Run the following command to open the file and change Defaults env_reset to Defaults !env_reset:

/etc/sudoers

Agent Can Be Started Through CCE, But It Goes Offline Later and No Data Is Reported

Cause: The adt user is specified to conduct the startup in the script. However, when the script is started from CCE, the root user executes the startup script and then the user is switched to the adt user. As a result, the Agent can be started from CCE, but it goes offline later and no data is reported.

• apm.log.0 exists in the root directory of the root user.
• JavaAgent automatically goes offline. There is no heartbeat or log.
• If the user deletes the corresponding instance when the Agent goes offline, it seems that no application is connected.

Solutions:

• Workaround: Switch to the user that matches the script, for example, adt, in the container, and then execute the startup script. In this way, the Agent can be started and data can be reported.
• Solution: Modify the permission of the adt user to write logs to the /home directory, or manually specify log.path in the apm.config file.

No Data Is Found When CCE is Connected to APM Through Fuxi

Check for the apm.log file. If the file does not exist, the Agent is not connected during startup.

Check the main configuration of Fuxi.

"JAVA_TOOL_OPTIONS": "-javaagent:/paas-apm2/javaagent/apm-javaagent/apm-javaagent.jar"

Check whether the JAVA_TOOL_OPTIONS environment variable exists in container 1 on CCE.

Check whether container 2 exists on CCE, check the instance startup event, and check whether the SWR image of JavaAgent has been loaded.

Agent Fails to Be Connected Through CCE (Log Shows That the Master Address Is Null)

During connection through CCE, select the Agent of the noroot version. For details, see Installing Agents for the Java Applications Deployed in CCE Containers.

"master address illegal" Is Reported When the Agent Is Connected to APM in CCE Access Mode

Solution: Security hardening has been performed on the container. To solve the problem, switch to the Agent of the noroot version.