Machine Agent Not reporting

[CommunityUser]

I am using the  4.1.3.1 version controller agent and machine-agent .

java version "1.7.0_80"

My controller and application agent are fine . 

I am tring install machine agent unsuccessfully.. 

Command:

sudo java -Xmx128m -Dappdynamics.agent.uniqueHostId=ip-172-31-32-188 -Dmetric.http.listener=true -Dmetric.http.listener.port=8081 -jar machineagent.jar

machineagent.log : 

[main] 30 Aug 2015 07:26:36,474 INFO SystemAgent - ####################################################################################
[main] 30 Aug 2015 07:26:36,474 INFO SystemAgent - Agent Install Directory [/opt/AppDynamics/machineagent]
[main] 30 Aug 2015 07:26:36,474 INFO SystemAgent - Using Agent Version [Machine Agent v4.1.2.0 GA Build Date 2015-08-07 11:48:21]
[main] 30 Aug 2015 07:26:36,494 INFO SystemAgent - JVM Runtime:
java.home=/usr/lib/jvm/java-7-oracle/jre
java.vm.vendor=Oracle Corporation
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.runtime.version=1.7.0_80-b15
java.io.tmpdir=/tmp
user.language=en
user.country=US
user.variant=
Default locale=en_US
[main] 30 Aug 2015 07:26:36,494 INFO SystemAgent - OS Runtime:
os.name=Linux
os.arch=amd64
os.version=3.13.0-48-generic
user.name=root
user.home=/root
user.dir=/opt/AppDynamics/machineagent
[main] 30 Aug 2015 07:26:36,512 INFO SystemAgent - JVM Args : -Xmx128m | -Dappdynamics.agent.uniqueHostId=ip-172-31-32-188 | -Dmetric.http.listener=true | -Dmetric.http.listener.port=8081 |
[main] 30 Aug 2015 07:26:36,715 INFO SystemAgent - JVM Runtime Name: 6242@ip-172-31-32-188
[main] 30 Aug 2015 07:26:36,716 INFO SystemAgent - JVM PID: 6242
[main] 30 Aug 2015 07:26:36,716 INFO SystemAgent - Machine Agent is resolving bootstrap info....
[main] 30 Aug 2015 07:26:39,325 INFO SystemAgent - Orchestration is disabled - disabling virtualization resolvers by default.
[main] 30 Aug 2015 07:26:39,526 INFO SystemAgent - Full Agent Registration Info Resolver found system property [appdynamics.agent.create.agent.info.if.missing] for appdynamics.agent.create.agent.info.if.missing [false]
[main] 30 Aug 2015 07:26:39,567 INFO SystemAgent - Default Host Identifier Resolver found system property [appdynamics.agent.uniqueHostId] for unique host identifier [ip-172-31-32-188]
[main] 30 Aug 2015 07:26:39,648 INFO SystemAgent - Default IP Address Resolver found IP addresses [[fe80:0:0:0:806:e0ff:fe81:f45%2, 172.31.32.188]]
[main] 30 Aug 2015 07:26:39,731 INFO SystemAgent - Full Agent Registration Info Resolver is forcing the agent registration configuration
[main] 30 Aug 2015 07:26:39,749 INFO SystemAgent - Full Agent Registration Info Resolver using selfService [false]
[main] 30 Aug 2015 07:26:39,749 INFO SystemAgent - Full Agent Registration Info Resolver using application name [MyApp]
[main] 30 Aug 2015 07:26:39,749 INFO SystemAgent - Full Agent Registration Info Resolver using tier name [MyTier]
[main] 30 Aug 2015 07:26:39,749 INFO SystemAgent - Full Agent Registration Info Resolver using node name [Tomcat@ip-172-31-32-188]
[main] 30 Aug 2015 07:26:39,831 INFO SystemAgent - XML Controller Info Resolver found controller host [52.20.219.151]
[main] 30 Aug 2015 07:26:39,831 INFO SystemAgent - XML Controller Info Resolver found controller port [8090]
[main] 30 Aug 2015 07:26:39,853 INFO SystemAgent - XML Agent Account Info Resolver using account name [system]
[main] 30 Aug 2015 07:26:39,853 INFO SystemAgent - XML Agent Account Info Resolver using account access key [12627d3a-45cb-11e5-9d83-0a06e0810f45]
[main] 30 Aug 2015 07:26:43,596 INFO SystemAgent - Machine Agent resolved bootstrap info!
[main] 30 Aug 2015 07:26:43,598 INFO SystemAgent - Creating machine agent scheduler, pool size: 2
[main] 30 Aug 2015 07:26:43,761 INFO SystemAgent - Creating machine agent monitor scheduler, pool size: 4
[main] 30 Aug 2015 07:26:43,764 INFO SystemAgent - Started Agent Schedulers
[main] 30 Aug 2015 07:26:43,764 INFO SystemAgent - Scheduling Machine Agent Registration ....
[main] 30 Aug 2015 07:26:43,782 INFO RegistrationChannel - Reregistration Check is : [disabled].
[Agent-Scheduler-1] 30 Aug 2015 07:26:43,865 INFO RegistrationChannel - using controller host [52.20.219.151]; controller port [8090]
[Agent-Scheduler-1] 30 Aug 2015 07:26:44,187 INFO RegistrationChannel - setting unique host information Host Name [ip-172-31-32-188]
[Agent-Scheduler-1] 30 Aug 2015 07:26:44,187 INFO RegistrationChannel - setting agent version [Machine Agent v4.1.2.0 GA Build Date 2015-08-07 11:48:21]
[Agent-Scheduler-1] 30 Aug 2015 07:26:44,187 INFO RegistrationChannel - setting agent properties [null]
[Agent-Scheduler-1] 30 Aug 2015 07:26:44,187 INFO RegistrationChannel - setting agent install dir [/opt/AppDynamics/machineagent]
[Agent-Scheduler-1] 30 Aug 2015 07:26:44,187 INFO RegistrationChannel - setting agent type [MACHINE_AGENT]
[Agent-Scheduler-1] 30 Aug 2015 07:26:44,187 INFO RegistrationChannel - setting agent application [MyApp]
[Agent-Scheduler-1] 30 Aug 2015 07:26:44,187 INFO RegistrationChannel - setting agent tier name [MyTier]
[Agent-Scheduler-1] 30 Aug 2015 07:26:44,187 INFO RegistrationChannel - setting agent node name [Tomcat@ip-172-31-32-188]
[Agent-Scheduler-1] 30 Aug 2015 07:26:44,187 INFO RegistrationChannel - Sending Registration request
[Agent-Scheduler-1] 30 Aug 2015 07:26:47,824 INFO RegistrationChannel - Auto agent registration attempted: Application Name [MyApp] Component Name [MyTier] Node Name [Tomcat@ip-172-31-32-188]
[Agent-Scheduler-1] 30 Aug 2015 07:26:47,825 INFO RegistrationChannel - Auto agent registration SUCCEEDED!
[Agent-Scheduler-1] 30 Aug 2015 07:26:47,825 INFO SystemAgent - Registered Machine Agent with machine ID [2]
[Agent-Scheduler-1] 30 Aug 2015 07:26:47,876 INFO SystemAgent - Starting Machine Agent....
[Agent-Scheduler-1] 30 Aug 2015 07:26:47,877 INFO ControllerTimeSkewHandler - Skew Handler is : [disabled].
[Agent-Scheduler-1] 30 Aug 2015 07:26:47,877 INFO ControllerTimeSkewHandler - Controller Time Skew Handler Run Aborted - Skew Check is Disabled
[Agent-Scheduler-1] 30 Aug 2015 07:26:48,078 INFO ManagedMonitorDelegate - Started Agent Metric Generation Service
[Agent-Scheduler-1] 30 Aug 2015 07:26:48,179 INFO ManagedMonitorDelegate - Event Service is : [disabled].
[Agent-Scheduler-1] 30 Aug 2015 07:26:48,488 INFO ManagedMonitorDelegate - Metric Service is : [disabled].
[Agent-Scheduler-1] 30 Aug 2015 07:26:48,548 INFO ManagedMonitorDelegate - Started Agent Env Properties Service
[Agent-Scheduler-1] 30 Aug 2015 07:26:48,549 INFO ManagedMonitorDelegate - Scheduled Continuous Task Monitor with frequency [30000]ms
[Agent-Scheduler-1] 30 Aug 2015 07:26:51,473 INFO MetricAndEventReporter - Setup Request Handler Servlet
[Agent-Scheduler-1] 30 Aug 2015 07:26:51,925 INFO MetricAndEventReporter - Started metric and event publisher at: localhost/8081
[Agent-Scheduler-1] 30 Aug 2015 07:26:51,965 INFO AgentMonitorManager - Initialized System Monitor Manager with directory [/opt/AppDynamics/machineagent/monitors]
[Agent-Scheduler-1] 30 Aug 2015 07:26:51,965 INFO SystemAgent - Set up agent monitor manager
[Agent-Scheduler-1] 30 Aug 2015 07:26:51,984 INFO SystemAgent - Orchestration is disabled - disabling one-way agent transport. The agent will not be able to execute workflow tasks.
[Agent-Scheduler-1] 30 Aug 2015 07:26:52,716 INFO SystemAgent - Set up agent re-registration task
[Agent-Scheduler-1] 30 Aug 2015 07:26:52,800 INFO SystemAgentConfigManager - Scheduling configuration refresh at an interval of 60 seconds
[Agent-Scheduler-1] 30 Aug 2015 07:26:52,801 INFO SystemAgentConfigManager - Configuration refresh task interval is 60 seconds
[Agent-Scheduler-1] 30 Aug 2015 07:26:52,801 INFO SystemAgent - Configuration manager successfully configured
[Agent-Scheduler-1] 30 Aug 2015 07:26:52,960 INFO RunbookHandler - Runbook Operation Execution is : [disabled].
[Agent-Scheduler-1] 30 Aug 2015 07:26:52,960 INFO SystemAgent - Started AppDynamics Machine Agent Successfully.
[AD Thread Pool-Global0] 30 Aug 2015 07:26:58,721 INFO SystemAgent - Agent is now: [enabled].
[AD Thread Pool-Global0] 30 Aug 2015 07:26:58,778 INFO RegistrationChannel - Reregistration Check is : [enabled].
[AD Thread Pool-Global0] 30 Aug 2015 07:26:58,778 INFO ControllerTimeSkewHandler - Skew Handler is : [enabled].
[AD Thread Pool-Global0] 30 Aug 2015 07:26:58,778 INFO RunbookHandler - Runbook Operation Execution is : [enabled].
[AD Thread Pool-Global0] 30 Aug 2015 07:26:58,778 INFO ManagedMonitorDelegate - Metric Service is : [enabled].
[AD Thread Pool-Global0] 30 Aug 2015 07:26:58,778 INFO ManagedMonitorDelegate - Event Service is : [enabled].
[AD Thread Pool-Global0] 30 Aug 2015 07:26:58,778 INFO NodeMonitorManager - Monitors are now: [enabled].
[AD Thread Pool-Global0] 30 Aug 2015 07:26:58,819 INFO MonitorConfigReader - Reading monitor config file:/opt/AppDynamics/machineagent/monitors/JavaHardwareMonitor/monitor.xml
[AD Thread Pool-Global0] 30 Aug 2015 07:26:59,099 INFO MonitorConfigReader - os name [linux] version [3.13.0-48-generic]
[AD Thread Pool-Global0] 30 Aug 2015 07:26:59,179 INFO NodeMonitorManager - Initializing managed monitor [JavaHardwareMonitor]
[AD Thread Pool-Global0] 30 Aug 2015 07:26:59,179 INFO ManagedMonitorDelegate - Initializing managed monitor [SigarHardwareMonitor]
[AD Thread Pool-Global0] 30 Aug 2015 07:26:59,180 INFO ManagedMonitorDelegate - Executing managed monitor [SigarHardwareMonitor], task name [null]
[AD Thread Pool-Global0] 30 Aug 2015 07:26:59,180 INFO ManagedMonitorDelegate - Task [null] for monitor [SigarHardwareMonitor] is SCHEDULED
[AD Thread Pool-Global0] 30 Aug 2015 07:26:59,424 INFO JavaTaskCreator - Task classpath not specified,System classpath will be used.
[AD Thread Pool-Global0] 30 Aug 2015 07:27:01,297 WARN SigarConfig - No task file found. Will use default configuration. /opt/AppDynamics/machineagent/monitors/JavaHardwareMonitor/task.xml
[AD Thread Pool-Global0] 30 Aug 2015 07:27:01,297 INFO SigarDelegate - Operating system is supported [Linux]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:02,384 INFO SigarAppAgentMonitor - Full Agent Registration Info Resolver using selfService [false]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:02,395 INFO SigarAppAgentMonitor - Full Agent Registration Info Resolver using selfService [false]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:02,395 INFO SigarAppAgentMonitor - Full Agent Registration Info Resolver using application name [AppDynamics Controller]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:02,395 INFO SigarAppAgentMonitor - Full Agent Registration Info Resolver using tier name [App Server]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:02,395 INFO SigarAppAgentMonitor - Full Agent Registration Info Resolver using node name [Node1]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:02,776 INFO SigarAppAgentMonitor - Full Agent Registration Info Resolver using selfService [true]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,018 INFO SigarAppAgentMonitor - Full Agent Registration Info Resolver using selfService [true]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,018 INFO SigarAppAgentMonitor - Full Agent Registration Info Resolver using application name [MyApp]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,018 INFO SigarAppAgentMonitor - Full Agent Registration Info Resolver using tier name [unknown]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,018 INFO SigarAppAgentMonitor - Full Agent Registration Info Resolver using node name [null]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,341 WARN NodeMonitorManager - Invalid file in monitor directory nohup.out
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,341 INFO MonitorConfigReader - Reading monitor config file:/opt/AppDynamics/machineagent/monitors/HardwareMonitor/monitor.xml
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,343 INFO MonitorConfigReader - os name [linux] version [3.13.0-48-generic]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,442 INFO NodeMonitorManager - Initializing managed monitor [HardwareMonitor]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,442 INFO ManagedMonitorDelegate - Not initializing managed monitor [HardwareMonitor] - Disabled in configuration file.
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,442 INFO MonitorConfigReader - Reading monitor config file:/opt/AppDynamics/machineagent/monitors/analytics-agent/monitor.xml
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,570 INFO MonitorConfigReader - os name [linux] version [3.13.0-48-generic]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,571 INFO NodeMonitorManager - Initializing managed monitor [analytics-agent]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,571 INFO ManagedMonitorDelegate - Not initializing managed monitor [AppDynamics Analytics Agent] - Disabled in configuration file.
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,571 INFO MonitorConfigReader - Reading monitor config file:/opt/AppDynamics/machineagent/monitors/TakipiMonitor/monitor.xml
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,751 INFO MonitorConfigReader - os name [linux] version [3.13.0-48-generic]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,752 INFO NodeMonitorManager - Initializing managed monitor [TakipiMonitor]
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,752 INFO ManagedMonitorDelegate - Not initializing managed monitor [TakipiMonitor] - Disabled in configuration file.
[AD Thread Pool-Global0] 30 Aug 2015 07:27:03,752 INFO NodeMonitorManager - Directory [/opt/AppDynamics/machineagent/monitors/unmanaged] not found, continuing.

Pleas, any suggestion??

Hodaya..

[CommunityUser]

Hi , 

It works!!

Many thanks . 

[CommunityUser]

controller-info.xml:

<?xml version="1.0" encoding="UTF-8"?>
<controller-info>
<!-- For a more detailed information on different configurations that an agent can support
and the respective rules, one should reference following URL:
https://docs.appdynamics.com/display/PRO40/Java+Agent+Configuration+Properties
In general configuration properties may be set in different ways. Here is the order
of precedence how the agent will read and respect specific configurations.
1. Environment Variables
2. System Properties
3. Version specific controller-info.xml. See .../$(Agent-Base-Install-Dir)/ver$(agent-version-no)/conf/controller-info.xml
4. Default/Root controller-info.xml. See .../$(Agent-Base-Install-Dir)/conf/controller-info.xml -->

<!-- This is the host name or the IP address of the AppDynamics Controller e.g. 192.168.1.22 or myhost or myhost.abc.com
This is the same host that you use to access the AppDynamics browser based User interface.
This can be overridden with an environment variable 'CONTROLLER_HOST_NAME' or
the system property '-Dappdynamics.controller.hostName' -->
<controller-host>52.20.219.151</controller-host>

<!-- This is the http(s) port of the AppDynamics Controller , If 'controller-ssl-enabled' below is set to true, you must
specify the HTTPS port of the Controller, otherwise specify the HTTP port. The default values are 8090 for HTTP and 8181 for HTTPS
This is the same port that you use to access the AppDynamics browser based User interface.
This can be overridden with an environment variable 'APPDYNAMICS_CONTROLLER_PORT' or
the system property '-Dappdynamics.controller.port' -->
<controller-port>8090</controller-port>

<!-- This specifies if the AppDynamics agent should use SSL(HTTPS) to connect to the Controller. If you set this to true,
the controller port property above should be set to the HTTPs port of the Controller.
This can be overridden with an environment variable 'APPDYNAMICS_CONTROLLER_SSL_ENABLED' or
the system property '-Dappdynamics.controller.ssl.enabled' -->
<controller-ssl-enabled>false</controller-ssl-enabled>

<!-- Set this flag to 'true' to enable features required for AppDynamics Orchestration, including the following:
1) Enables the agent to execute tasks specified in AppDynamics Orchestration workflows.
2) Enables the agent to resolve the AppDynamics Controller host and port when the host
machine where this agent resides is created through AppDynamics Orchestration. -->
<enable-orchestration>false</enable-orchestration>

<!-- If the AppDynamics Controller is running in multi-tenant mode or you are using the AppDynamics SaaS Controller
you must specify the account name and account access key for this agent to authenticate with the controller.
If you are running in single-tenant mode (the default) there is no need to configure these values.
This can be overridden with an environment variable 'APPDYNAMICS_AGENT_ACCOUNT_NAME' or
the system property '-Dappdynamics.agent.accountName' -->
<account-name>system</account-name>

<!-- This can be overridden with an environment variable 'APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY' or
the system property '-Dappdynamics.agent.accountAccessKey' -->
<account-access-key>12627d3a-45cb-11e5-9d83-0a06e0810f45</account-access-key>

<!-- For Auto Agent Registration specify the application name, tier name,
and optionally, node name. If the application and/or tier does not exist
already it will be created. If there is already a registered app server agent
installed on the same host as this machine agent then Auto Agent Registration
is not necessary for this machine agent.
This can be overridden with an environment variable 'APPDYNAMICS_AGENT_NODE_NAME' or
the system property '-Dappdynamics.agent.nodeName' -->
<application-name>MyApp</application-name>
<!-- <application-name>AppDynamics Controller</application-name> -->

<!-- This can be overridden with an environment variable 'APPDYNAMICS_AGENT_TIER_NAME' or
the system property '-Dappdynamics.agent.tierName' -->
<tier-name>MyTier</tier-name>
<!-- <tier-name>App Server</tier-name> -->

<!-- This can be overridden with an environment variable 'APPDYNAMICS_AGENT_NODE_NAME' or
the system property '-Dappdynamics.agent.nodeName' -->
<node-name>Tomcat@ip-172-31-32-188</node-name>
<!-- <node-name>Node1</node-name> -->

<!-- Change to 'true' only under special circumstances where this agent has been moved to a new application and/or tier
from the UI but you want to override that move by specifying a new application name and/or tier name in the agent configuration.
If there is already a registered app server agent installed on the same host as this machine agent then this override DOES not work.
If you want to override the UI in this case, you must force the agent registration change from the app server agent configuration. -->
<force-agent-registration>true</force-agent-registration>

<!-- This value is used to create 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
it could be set to "Virginia Data Center|DataRack1|Machine1" and the UI will display in that hierarchy.
<machine-path></machine-path> -->

</controller-info>

[CommunityUser]

Hi , 

Thanks alot for your reply. 

My login account is really cutomer1 (I confirmed it with the License screen). 

When I run it with this user i get an error that this user doesn't authorized. 

The machine agent log: 

[Agent-Scheduler-2] 01 Sep 2015 08:49:52,636 INFO RegistrationChannel - using controller host [52.20.219.151]; controller port [8090]
[Agent-Scheduler-2] 01 Sep 2015 08:49:52,636 INFO RegistrationChannel - setting unique host information Host Name [ip-172-31-32-188]
[Agent-Scheduler-2] 01 Sep 2015 08:49:52,636 INFO RegistrationChannel - setting agent version [Machine Agent v4.1.2.0 GA Build Date 2015-08-07 11:48:21]
[Agent-Scheduler-2] 01 Sep 2015 08:49:52,636 INFO RegistrationChannel - setting agent properties [null]
[Agent-Scheduler-2] 01 Sep 2015 08:49:52,636 INFO RegistrationChannel - setting agent install dir [/opt/AppDynamics/machineagent]
[Agent-Scheduler-2] 01 Sep 2015 08:49:52,636 INFO RegistrationChannel - setting agent type [MACHINE_AGENT]
[Agent-Scheduler-2] 01 Sep 2015 08:49:52,636 INFO RegistrationChannel - setting agent application [MyApp]
[Agent-Scheduler-2] 01 Sep 2015 08:49:52,636 INFO RegistrationChannel - setting agent tier name [MyTier]
[Agent-Scheduler-2] 01 Sep 2015 08:49:52,636 INFO RegistrationChannel - setting agent node name [Tomcat@ip-172-31-32-188]
[Agent-Scheduler-2] 01 Sep 2015 08:49:52,636 INFO RegistrationChannel - Sending Registration request
[Agent-Scheduler-2] 01 Sep 2015 08:49:52,656 ERROR RegistrationChannel - HTTP Request failed: HTTP/1.1 401 Unauthorized
[Agent-Scheduler-2] 01 Sep 2015 08:49:52,656 WARN RegistrationChannel - Could not connect to the controller/invalid response from controller, cannot get registration information
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,657 INFO RegistrationChannel - using controller host [52.20.219.151]; controller port [8090]
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,657 INFO RegistrationChannel - setting unique host information Host Name [ip-172-31-32-188]
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,657 INFO RegistrationChannel - setting agent version [Machine Agent v4.1.2.0 GA Build Date 2015-08-07 11:48:21]
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,657 INFO RegistrationChannel - setting agent properties [null]
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,657 INFO RegistrationChannel - setting agent install dir [/opt/AppDynamics/machineagent]
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,657 INFO RegistrationChannel - setting agent type [MACHINE_AGENT]
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,657 INFO RegistrationChannel - setting agent application [MyApp]
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,657 INFO RegistrationChannel - setting agent tier name [MyTier]
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,657 INFO RegistrationChannel - setting agent node name [Tomcat@ip-172-31-32-188]
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,657 INFO RegistrationChannel - Sending Registration request
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,676 ERROR RegistrationChannel - HTTP Request failed: HTTP/1.1 401 Unauthorized
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,676 WARN RegistrationChannel - Could not connect to the controller/invalid response from controller, cannot get registration information

WDYT?

[Arun_Dasetty]

Hi Hodaya,

Thanks for the logs, from which it is evident that we have not provided customer1 access key as it looks you are trying to login customer1 but provided system1 account, Can you login /controller URI and copy the "access key" value from Setup -> License screen and provided account name as customer1 and access-key values in controller-info.xml of machine agnet and see how it goes with restart of machineagent java process?

[Agent-Scheduler-2] 01 Sep 2015 08:50:12,676 ERROR RegistrationChannel - HTTP Request failed: HTTP/1.1 401 Unauthorized
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,676 WARN RegistrationChannel - Could not connect to the controller/invalid response from controller, cannot get registration information

Snippet from doc stating the same:

"[Agent-Scheduler-2] 01 Sep 2015 08:50:12,676 ERROR RegistrationChannel - HTTP Request failed: HTTP/1.1 401 Unauthorized
[Agent-Scheduler-2] 01 Sep 2015 08:50:12,676 WARN RegistrationChannel - Could not connect to the controller/invalid response from controller, cannot get registration information
 

To find your account name and account access key, click the settings (gear) icon in the upper right corner of the AppDynamics UI, click License. Click Show to get the access key value. You need account-level permissions to view the license."

[Arun_Dasetty · Accepted solution]

Hi Hodaya,

By default account-name system is used for controller internal agent and user associates apps using cutomer1(if single tenant) or user account name created during/later controller installation, let us know if any reason you are using system account,

- Can you confirm which account you logged, this can be check from Setup -> License screen in controller UI to see whether you logged in system/customer1 account

Because we see machine agent looks registered fine in UI and it looks we are seeing in wrong account, validate above query and confirm us?

[Agent-Scheduler-1] 30 Aug 2015 07:26:47,824 INFO RegistrationChannel - Auto agent registration attempted: Application Name [MyApp] Component Name [MyTier] Node Name [Tomcat@ip-172-31-32-188]
[Agent-Scheduler-1] 30 Aug 2015 07:26:47,825 INFO RegistrationChannel - Auto agent registration SUCCEEDED!
[Agent-Scheduler-1] 30 Aug 2015 07:26:47,825 INFO SystemAgent - Registered Machine Agent with machine ID [2]