AppD Archive

After installation: "Failed to start the Controller in the timeout period of 45 minutes.

CommunityUser
Splunk Employee
Splunk Employee

I'm trying to test AppDynamics to determine if our company wants to go with it over New Relic. I did the on-premises install using CentOS 6.5 x86_64 with the 14 day trial. 

The first time I tried installing it the system only had 1GB of RAM and I got the following error after the .sh scripts timed out:

/home/AD/AppDynamics/Controller/checkAS.sh
/home/AD/AppDynamics/Controller/checkAS.sh
/home/AD/AppDynamics/Controller/checkAS.sh
/home/AD/AppDynamics/Controller/checkAS.sh
/home/AD/AppDynamics/Controller/checkAS.sh
/home/AD/AppDynamics/Controller/checkAS.sh
/home/AD/AppDynamics/Controller/checkAS.sh
/home/AD/AppDynamics/Controller/checkAS.sh
/home/AD/AppDynamics/Controller/checkAS.sh
/home/AD/AppDynamics/Controller/checkAS.sh
/home/AD/AppDynamics/Controller/checkAS.sh
/home/AD/AppDynamics/Controller/checkAS.sh
/home/AD/AppDynamics/Controller/checkAS.sh
/home/AD/AppDynamics/Controller/checkAS.sh
Failed to start the Controller in the timeout period of 45 minutes.
If you are able to start the Controller manually, try re-installing the Controller after increasing the timeout.
If unable to start the Controller, contact AppDynamics support for assistance.
Finishing installation ...

I upped the memory to 16 GB and verified it shows up in htop and /proc/meminfo. Attempting to install again generates the same timeout of 45 minutes error.

Next I checked the logs. In startAS.log I have:

There is a process already using the admin port 4848 -- it probably is another instance of a GlassFish server.
Command start-domain failed.

However, netstat -tulpn doesn't show any applicaitons using port 4848. 

What could be the problem? Do I need to uninstal and start from scratch? If so how would I go about this?

Attaching all three logs and the tracert command output.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi all,

currently using the free trial version for Linux/64 (OpenSuse), same issue than described here, but valid hostname set instead of IP. Local machine name, but NOT "localhost", as recommeded, DNS resolution correct.

Port 4848 definitively is available, not blocked.

Any ideas how to narrow down this issue?

0 Karma

Arun_Dasetty
Super Champion

Hi,

Can you send the relevant controller install logs and error at console you are seeing once for review, also can you try localhost once while you collect logs?

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Attachments didn't work properly. Zipping and attaching here.

0 Karma

Arun_Dasetty
Super Champion

Hi ,

Can you please kill all java process(assuming no other java process running apart from controller glassfish process) in instance ip "10.0.0.40" where controller installed and reboot the instance and delete the directory /home/AD/AppDynamics/Controller 

Now check whether the IP resolves to any load balancer host where 4848 port is in use or requests redirects by any chance here , check /etc/hosts file to see the host resolved to ip "10.0.0.40" 

If there is no issue in IP resolved to ip "10.0.0.40" now install afresh with below commands

shell> controller.sh -Vad-timeout-in-min=<Controller_timeout> -Vstartup-timeout-in-min=<database_timeout>

ex:

shell> controller.sh -Vad-timeout-in-min=60 -Vstartup-timeout-in-min=60

We do not see much logging in server.log and we suspect this could be due to port conflict or ip resolved in hosts file have issue and that need to be resolved.

Also let us know the command used to list ports in use is listing ports in entire instance or ports used by specific user as such?

let us know if that information helps. Keep us posted how it goes.

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hey Arun, thanks for the suggestions.

I followed your instructions but recieved the same timeout error after an hour. After that I started researching the error in the checkAS.log and found that the local IP wasn't associated with the hostname- the hosts file only had localhost and variations of 127.0.0.1. 

After adding the hostname the installation completed!

Thanks again,

Jordan

0 Karma

Arun_Dasetty
Super Champion

Hi Jordan,

Thanks for the update and glad that my suggestions on /etc/hosts file have helped in resolving the issues. 

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 ...