AppD Archive

Controller dashboard does not show anything

CommunityUser
Splunk Employee
Splunk Employee

Hi,

I have been trying to setup on-premise controller along with Java appagent.

My agent is running started successfully and running fine (Log attached)

My controller is also running fine (Log attached)

When I click on Node dashboard, it just hangs and does not show anything.

Controller (Windows machine)

App Agent (Linux machine)

Any help will be highly appreciated.

thanks

Rajeev

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,

Even i am getting similar error which is "11 Sep 2016 04:29:01,243 ERROR [AD Thread-Metric Reporter0] ManagedMonitorDelegate:30 - Fatal transport error while connecting to URL [/controller/instance/55587/metrics]: org.apache.http.conn.ConnectTimeoutException: Connect to tesco898.saas.appdynamics.com:443 [tesco898.saas.appdynamics.com/69.27.44.146] failed: Read timed out
" Error . I have attached the full logs of db-agent.

Could you please help me out , ?

Thanks

Praveen

0 Karma

Arun_Dasetty
Super Champion

Hi Praveen,

Is the db agent java process still running, Can you pleae check behaviour post below changes:

- We see user and password are not provided in edit view of db collector config in UI, we do see in agent in past it connected to contorller fine, and would like to check if recently we wrong updated, check once all settings and resave changes in UI

- Also check if any network issues at your network end form db agent instance to saas host or check output of "telnet tesco898.saas.appdynamics.com 443" as we see no specific errors for 55587 id in controller monitoring tools logs

also can you start without uniquehost id -D jvm arg as you are using default db agent option in collector config, see if that information helps.

If issue exists send the latest logs and screenshot of Setup -> License screen and edit view collector in UI.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,

Thank you for quick reply and I appreciate your support.

Answer to your questions

1. " We see user and password are not provided in edit view of db collector config in UI".

We dont have username and password for db , so we are not passing any username and password( authentications ).

2. telnet tesco898.saas.appdynamics.com 443

    I am able to connect to the above host and below is response i got from the above command

Trying 69.27.44.146...
Connected to tesco898.saas.appdynamics.com.
Escape character is '^]'.

3. can you start without uniquehost id -D jvm arg as you are using default db agent option in collector config,

I have tried this as well and now i am getting "com.mongodb.CommandFailureException: { "serverUsed" : "localhost:27017" , "ok" : 0.0 , "code" : 18 , "errmsg" : "Authentication failed."}" Error. I have attached db agents full logs and collector screen shot as you wanted.

 

Thank you,

Praveen

0 Karma

Arun_Dasetty
Super Champion

Hi Praveen,

Upgrade dbagent from 4.1.8.7 to 4.2.x latest db agent and see how it goes and also check whethre the user running db agent have acccess to mongodb admin for below url and check permissions link below and see if that information helps

localhost:27017/admin

https://docs.appdynamics.com/display/PRO42/MongoDB+Database+Permissions

02:36:02,110  INFO [main] DBAgent:46 - Using Agent Version [Database Agent v4.1.8.7 GA Build Date 2016-01-12]

0 Karma

Arun_Dasetty
Super Champion

Hi Rajeev,

Please find our analysis of the the logs provided and plan of action:
1) We see you are using agent node name as "Node1" which we do not recommend, please update the node name to different name say: CTMSAdapterNode1 in /home/tibco/CTIP/monitoring/appagent/conf/controller-info.xml under
<node-name> xml element and save the changes and restart the server with agent configured:
[Thread-0] 11 Jul 2014 10:34:07,388 INFO XMLConfigManager - Full Agent Registration Info Resolver using node name [Node1]

2) We see network errors in agent logs for agent registration and this could also be reason that agent registration failed, please make sure you have checked
network connectivity between agent instance "172.16.189.45" and controller machine "172.16.208.16", you can check as follows:
shell> telnet 172.16.208.16 8090

==========================================
[AD Thread Pool-Global0] 11 Jul 2014 10:35:13,252 INFO ConfigurationChannel - Sending Registration request with: Application Name [CTMSAdapter_1010B], Tier Name [App Server], Node Name [Node1], Host Name [not-tibco-952v.pii.pxl.int] Node Unique Local ID [Node1], Version [Server Agent v3.8.4.0 GA #2014-06-30_13-26-26 r5dc2d8d219673e698b0b455657ac469bc8b59337 4-3.8.4.next]
[AD Thread Pool-Global0] 11 Jul 2014 10:35:18,260 ERROR ConfigurationChannel - Fatal transport error: The host did not accept the connection within timeout of 5000 ms
[AD Thread Pool-Global0] 11 Jul 2014 10:36:23,272 ERROR ConfigurationChannel - Exception: The host did not accept the connection within timeout of 5000 ms
org.apache.commons.httpclient.ConnectTimeoutException: The host did not accept the connection within timeout of 5000 ms
at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:155)
..Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
=========================================

On a side note:
1) we see your license is about to expire we hope this is yet to expire please get the license extended before license get expired:
[#|2014-07-11T10:34:41.567+0100|WARNING|glassfish3.1.2|com.singularity.ee.controller.beans.ControllerChecker|_ThreadID=130;_ThreadName=Thread-6;|License is about to expire in 0 days, 21 hours, 25 minutes . Please renew the license|#]

2) We see below eror but this can be ignored as you can access controller UI fine as per your comments:
[#|2014-07-10T16:38:18.920+0100|SEVERE|glassfish3.1.2|null|_ThreadID=201;_ThreadName=Thread-6;|Config Listener class org.glassfish.admin.monitor.MonitoringBootstrap notification took too long
java.util.concurrent.TimeoutException

If issue still persist after checking above steps, please send the screenshot from controller UI and latest agents logs, also let us know if there are any firewall or proxy in place that could block connectivity between agent and controller on port 8090.

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Thanks Arun for such a quick response

1. Have changed the Node name from Node1 to something else

2. Seems there was a firewal running on my machine which did not allow agent to connect on 8090 port, have got firewall edited and seems agent is running fine and able to connect to controller and register itself

3. Have got my license extended for another 2 weeks.

Issue on the controller console still persists as it just hangs and does not show anything. (screenshot attached)

thanks for the help

Rajeev

0 Karma

Arun_Dasetty
Super Champion

Hi Rajeev,

As per screenshot we see you are logged in different context of controller UI where only controller internal agent details and controller internal application will be displayed, issue the following steps to monitor your application "CTMSAdapter_1010B" associated at /controller context in controller UI:

1) Logout controller UI session which you have logged in as root user in UI

2) clear browser cache

3) Now hit the URL http://localhost:8090/controller in new browser tab
4) Provide the username/password under account/password , which you should have provided during controller installation

5) Now check whether you see an application with name "CTMSAdapter_1010B"  in /contrller context controller UI

Let us know if that information helps, 

Regards,

Arun

CommunityUser
Splunk Employee
Splunk Employee

thank you very much Arun,

It does work and I can see the appagent.

Will continue with my evaluation now.

thanks

Rajeev

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...