topic Re: Machine Agent unable to register to the Appd SaaS Controller - Connection timed out in Splunk AppDynamics

Machine Agent unable to register to the Appd SaaS Controller - Connection timed out

ak-amal_Kumar — Mon, 11 Sep 2023 13:01:34 GMT

Hi Team,

I am trying to install the Machine Agent on a Unix Machine hosted in AWS . Installation is fine, i can see the Appd Machine Agent service up and running. But it is not getting registered to the controller .

When i check the logs, it shows up a Timed out error. Is there anything specific i need to do for AWS Ec2 instances that has machine agents installed there

Re: Machine Agent unable to register to the Appd SaaS Controller - Connection timed out

Morelz — Tue, 12 Sep 2023 11:06:31 GMT

Hi Ak-mal

If the machine agent process is up and running, check the following

1. Connectivity from your ec2 instance to the AppDynamics Controller(telnet , Curl etc.)

2. Validate that you have added the machine agent configuration details with the controller host, port, ssl enabled, account and access key info in the controller-info.xml file

Ciao

Re: Machine Agent unable to register to the Appd SaaS Controller - Connection timed out

ak-amal_Kumar — Tue, 12 Sep 2023 11:12:01 GMT

I have checked the telnet 443 , it is connecting fine. I have checked the configurations. all looks fine.

Is there any specific license needed from the controller to connect to the Amazon ec2 instances. and will there be an issue with the user which is running the machine agent

Re: Machine Agent unable to register to the Appd SaaS Controller - Connection timed out

Morelz — Tue, 12 Sep 2023 11:14:44 GMT

Hi, where the machine agent runs is of no concern to AppDynamics. It makes no difference if running in aws, on premise etc.

As long as the user that runs the machine agent process has permissions to read/write to the machine agent directory that's fine.

Can you share your controller-info.xml configuration(Just remove sensitive info), want to check something

Re: Machine Agent unable to register to the Appd SaaS Controller - Connection timed out

ak-amal_Kumar — Tue, 12 Sep 2023 11:57:38 GMT

<controller-info>

<controller-host>xxxx</controller-host>

<controller-port>443</controller-port>

<controller-ssl-enabled>true</controller-ssl-enabled>

<enable-orchestration>false</enable-orchestration>

<!-- The Machine Agent uses the Java API to get the host name of the agent. The results from the API can be
inconsistent, and the same JVM can sometimes return a different value for the same machine each time the machine
agent is restarted. It is recommended to set this field in the following scenarios:

1) The machine host name is not constant
2) You prefer to use a specific name in the UI
3) The machine has both a machine agent and app agents on it.

This can be overridden with the environment variable 'APPDYNAMICS_AGENT_UNIQUE_HOST_ID' or the system property
'-Dappdynamics.agent.uniqueHostId' -->
<unique-host-id>xxxx</unique-host-id>

<account-access-key>xxxxxx</account-access-key>

<account-name>xxxxx</account-name>

<sim-enabled>true</sim-enabled>

<is-sap-machine></is-sap-machine>

<!-- This value is used to create the hierarchy infrastructure view in the UI for this machine. Each hierarchy level
should be separated with a vertical bar ("|"). For example, if this machine belongs to "DataRack1" and it is located
in "Virginia Data Center", then the machine path could be set to "Virginia Data Center|DataRack1|Machine1" and the
UI will display it in that hierarchy ("Virginia Data Center|DataRack1"). The last element of the path indicates the
server name (e.g., "Machine1") and appears as the name on the servers list in the UI. This can be overridden with
the environment variable 'APPDYNAMICS_MACHINE_HIERARCHY_PATH' or the system property
'-Dappdynamics.machine.agent.hierarchyPath'.

Note: The number of characters up to but not including the last vertical bar must not exceed 95. -->
<machine-path></machine-path>

</controller-info>

Re: Machine Agent unable to register to the Appd SaaS Controller - Connection timed out

Morelz — Tue, 12 Sep 2023 12:00:10 GMT

Ok, unless you mistyped anything, it should be all good.

You have SIM Licenses available in the controller as well correct?

Can you possibly zip the logs and share it privately, would need to see the full log to see what is happening.

Re: Machine Agent unable to register to the Appd SaaS Controller - Connection timed out

ak-amal_Kumar — Tue, 12 Sep 2023 12:19:30 GMT

Yes, we do have the Sim licenses available. let me try to share you the logs.

Re: Machine Agent unable to register to the Appd SaaS Controller - Connection timed out

ak-amal_Kumar — Wed, 13 Sep 2023 01:16:48 GMT

this is the machine-agent logs which i get after installing the machine agent on the ec2 Linux server