topic Re: install failing here with fedora in AppD Archive

install failing here with fedora

CommunityUser — Tue, 09 Dec 2014 01:13:57 GMT

i am installing the demo install on fedora 20 (64bit) and as far as i am aware have gone through all the required steps.

on each run-through of the installer, the process crashes with an error message and log dump (after having completed the progress bar process).

i attempted to read through the support docs for appdynamics, however, the support docs also crashed on your website here. specifically, accessing the 'swappiness' page in the installation guide, caused the docs app to crash (and other pages too).

this is not a great start for me here. how do you recommend i proceed?

thanks

Re: install failing here with fedora

Arun_Dasetty — Tue, 09 Dec 2014 08:02:16 GMT

Hi,

We have attached support environments and also the swapiness doc, we apologize for the issue you are facing, Can you please help us provide the complete error message raised while install process is going to assist you better.

Regards,

Arun

Re: install failing here with fedora

CommunityUser — Tue, 09 Dec 2014 10:08:10 GMT

thanks for responding here.

the technical requirements for the controller only list Fedora 14, with no '+' symbol. does that then mean that Fedora 20 has not been tested with your software?

if i find that i am unable to operate the controller using fedora 20, am i then able to switch to use the version of the controller that is hosted by appdynamics remotely? if so, is there a breakdown that shows what type of performance loss this may incur for my website/server?

thanks

Re: install failing here with fedora

Arun_Dasetty — Tue, 09 Dec 2014 10:37:01 GMT

Hi,

The versions listed in docs support list are officially tested test environment for controller installation But that does not mean we do not support higher versions we see lot many customers successfully deployed in higher OS versions.

Regarding other query, We understood that you are referring to saas controller hosted by appdynamics, we see the features and metrics reported by agent and controller will not vary as long as the agent version pointing to whether to local or saas controller UI version is same as well. Hope that answers your query. We have attached few docs for few features that shows what are different performance metrics that AD agents captures , listed for only few screens/features.

It would be great if you provide the error stack trace you are seeing while installing controller this helps to see if error is specific to incompatabiity of OS or error specific to AD controller installer or installation process or permissions.

Regards,

Arun

Re: install failing here with fedora

CommunityUser — Tue, 09 Dec 2014 11:52:47 GMT

ok, thanks for the documents - i will look through those asap.

here's the error log from the failed install process:

Exception:

com.install4j.api.beans.UndefinedVariableException: installer:ping-url
   at com.install4j.runtime.installer.InstallerVariables$InstallerReplacementCallback.handleError(Unknown Source)
   at com.install4j.runtime.installer.InstallerVariables$InstallerReplacementCallback.getReplacement(Unknown Source)
   at com.install4j.runtime.util.StringUtil.replaceVariable(Unknown Source)
   at com.install4j.runtime.installer.InstallerVariables.replaceVariables(Unknown Source)
   at com.install4j.runtime.installer.InstallerVariables.replaceVariables(Unknown Source)
   at com.install4j.runtime.installer.InstallerVariables.replaceVariables(Unknown Source)
   at com.install4j.runtime.installer.config.ActionBeanConfig.getErrorMessage(Unknown Source)
   at com.install4j.runtime.installer.controller.Controller.handleFailure(Unknown Source)
   at com.install4j.runtime.installer.controller.Controller.executeActions(Unknown Source)
   at com.install4j.runtime.installer.controller.Controller.handleCommand(Unknown Source)
   at com.install4j.runtime.installer.controller.Controller.start(Unknown Source)
   at com.install4j.runtime.installer.Installer.runInProcess(Unknown Source)
   at com.install4j.runtime.installer.Installer.main(Unknown Source)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
   at com.install4j.runtime.launcher.Launcher.main(Unknown Source)

System properties:

java.runtime.name=Java(TM) SE Runtime Environment
exe4j.moduleName=/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh
sun.boot.library.path=/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre/lib/amd64
java.vm.version=24.55-b03
java.vm.vendor=Oracle Corporation
java.vendor.url=http://java.oracle.com/
path.separator=:
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
file.encoding.pkg=sun.io
user.country=US
sun.java.launcher=SUN_STANDARD
sun.os.patch.level=unknown
install4j.exeDir=/mypath/appdynamics/
java.vm.specification.name=Java Virtual Machine Specification
user.dir=/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir
java.runtime.version=1.7.0_55-b13
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.endorsed.dirs=/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre/lib/endorsed
os.arch=amd64
java.io.tmpdir=/tmp
line.separator=

java.vm.specification.vendor=Oracle Corporation
os.name=Linux
exe4j.totalDataLength=455698836
proxySet=false
sun.java2d.noddraw=true
sun.jnu.encoding=ANSI_X3.4-1968
java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
sun.awt.enableExtraMouseButtons=true
java.specification.name=Java Platform API Specification
java.class.version=51.0
sun.management.compiler=HotSpot 64-Bit Tiered Compilers
os.version=2.6.32-042stab093.4
i4j.vpt=true
install4j.cwd=/mypath/appdynamics
user.home=/root
user.timezone=Europe/London
java.awt.printerjob=sun.print.PSPrinterJob
file.encoding=ANSI_X3.4-1968
install4j.jvmDir=/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre
java.specification.version=1.7
java.class.path=i4jruntime.jar:user.jar:user/ant.jar:user/commons-io-2.4.jar:user/mysql-connector-java-5.1.17-bin.jar
user.name=root
java.vm.specification.version=1.7
sun.java.command=com.install4j.runtime.launcher.Launcher launch com.install4j.runtime.installer.Installer false false   false true false true true 0 0 20 20 Arial 0,0,0 8 500 version 3.9.6.1 20 40 Arial 0,0,0 8 500 -1
java.home=/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre
sun.arch.data.model=64
user.language=en
java.specification.vendor=Oracle Corporation
awt.toolkit=sun.awt.X11.XToolkit
java.vm.info=mixed mode
java.version=1.7.0_55
java.ext.dirs=/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre/lib/ext:/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre/jre/lib/ext
sun.boot.class.path=/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre/lib/resources.jar:/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre/lib/rt.jar:/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre/lib/sunrsasign.jar:/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre/lib/jsse.jar:/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre/lib/jce.jar:/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre/lib/charsets.jar:/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre/lib/jfr.jar:/mypath/appdynamics/controller_64bit_linux-3.9.6.1.sh.16521.dir/jre/classes
install4j.appDir=/mypath/appdynamics/
i4j.vmov=true
java.vendor=Oracle Corporation
file.separator=/
java.vendor.url.bug=http://bugreport.sun.com/bugreport/
sun.font.fontmanager=sun.awt.X11FontManager
sun.io.unicode.encoding=UnicodeLittle
sun.cpu.endian=little
install4j.systemLanguage=en
sun.cpu.isalist=

Re: install failing here with fedora

Arun_Dasetty — Tue, 09 Dec 2014 14:38:17 GMT

Hi,

Unfortunately we do not encounter similar error earlier from past ticket history in other customer environments,
But we see the error is specific to install4j installer and error raised when variable ping-url is not found somehow

Found the following lines in <controller_dir>/.install4j/installation.log from local instance for two different install setups
Variable changed: ping-url=http://127.0.0.1:57162/controller/createAccount?action=ping[class java.lang.String]
Pinging URL: http://127.0.0.1:57162/controller/createAccount?action=ping
Pinging URL: http://127.0.0.1:57162/controller/createAccount?action=ping was successful!
Variable changed: configPort=57162[class java.lang.String]
Property replaceValue: TEMP_DOMAIN_PORT=57162
..
Variable changed: ping-url=http://127.0.0.1:62259/controller/createAccount?action=ping[class java.lang.String]
Pinging URL: http://127.0.0.1:62259/controller/createAccount?action=ping
Pinging URL: http://127.0.0.1:62259/controller/createAccount?action=ping was successful!

Can you please try the following and see if that makes any difference:
- Stop the installation process and make sure you remove old install directory , backup install logs if exists
- Create response.varfile (refer attached temp file) and create required properties as stated in doc link:
https://docs.appdynamics.com/display/PRO39/Install+an+On-Premise+Controller+Silently
- Also add below property names in response.varfile:
configPort=57182
TEMP_DOMAIN_PORT=57182
ping-url=http://127.0.0.1:57162/controller/createAccount?action=ping

- Now start the installer again in silent mode instead in GUI mode pointing to response.varfile with updated changes
- Also make sure the host name provided in response.varfile for controller installation is resolved in /etc/hosts files in physical instance.

if issue persists please send the install4j logs and install.log and installation.log under controller directory, we suspect the
error just raised could be due to installer failed to find variable ping-url on this instance somehow.

Regards,

Arun

Re: install failing here with fedora

CommunityUser — Tue, 09 Dec 2014 20:17:21 GMT

i have used the method described to create a silent install process and the following output was created:

Unpacking JRE ...
Preparing JRE ...
Starting Installer ...
The installation directory has been set to /home/ura/AppDynamics/Controller.
/home/ura/AppDynamics/Controller/checkLibaio.sh
Extracting files ...
Starting AppDynamics Controller Database.
Applying User Configuration to AppDynamics Controller Database State...
Applying User Configuration Complete.
Starting AppDynamics Controller...
/home/ura/AppDynamics/Controller/checkAS.sh
Failed to reach Controller at http://127.0.0.1:57162/controller/createAccount?action=ping!

Contact AppDynamics support for assistance.

Setup will now quit.
Rolling back changes ...

Re: install failing here with fedora

Arun_Dasetty — Wed, 10 Dec 2014 05:49:07 GMT

Hi,

We understood that this time the earlier error have not raised and we see different error after changes suggested. We see a typo in my earlier update, Can you update response.varfile and make sure the port is not in use as well and retry install process again:

configPort=57182
TEMP_DOMAIN_PORT=57182
ping-url=http://127.0.0.1:57182/controller/createAccount?action=ping

Let us know how it goes.

Regards.

Arun

Re: install failing here with fedora

CommunityUser — Wed, 10 Dec 2014 14:14:09 GMT

i saw that the port number was probably incorrect, though i thought best that you identify that at your end.

i ran the installer with the corrected port and now i am informed that the IIOP port (3700) is in use.

i ran netstat and saw that java is using that port, which i presume is a previous version of appdynamics software.

i looked for the uninstall script to run for appDynamics, however, there is no uninistall script on my server now, neither in the old or present install location of the appDynamics software.

is there a service i need to stop?

Re: install failing here with fedora

Arun_Dasetty — Wed, 10 Dec 2014 14:26:46 GMT

Hi,

Good to hear that we overcome the old error, thanks for trying out, Can you please try following for new issue:

- stop all JVMs and mysql process (we assume no production jvms are running in this instance)

shell> ps -ef | grep "java"

- Take a backup of response.varfile with all the changes used for recent controller installation process

- now restart physical instance and delete the old controller installation directory itself, as this is not windows instance deleting controller directory should help after making sure no java and mysql process initiated by controller is running

- Check if by any chance the port is in use using commands:

shell> netstat -anp | grep 3700

shell> lsof -i | grep 3700

- Now retry controller installer process and see if issue persists , Please stop all java and mysql process and delete old controller directory and update the following property to another open port and see how it goes, sample property entry in response.varfile:

iiopPort=3708

Keep us posted how it goes.

Regards,

Arun

Re: install failing here with fedora

CommunityUser — Wed, 10 Dec 2014 15:44:15 GMT

when i run: ps -ef | grep "java"

i see a long list of appdynamics related results. what is the appropriate syntax to end them?

Re: install failing here with fedora

Arun_Dasetty — Thu, 11 Dec 2014 06:33:07 GMT

Hi,

The command is listed below:

shell> killall java

But please do not issue above command, as we would like to get clarity on why you want to kill appdynamics controller process. is the controller installation succeeded , if not but if <Controller_dir>/bin path exists, and if controller installaiton is not succeeded and if you want to delete old directory, peform the following steps:

shell> cd <Controller_install_dir>/bin

shell> ./controller.sh stop-appserver

shell> ./controller.sh stop-db

Now delete the controller install directory and start afresh controller installation , Hope that information helps, Also let us know the error and provide the install.log under path <Controller_install_dir>/ if installation failed partially.

Regards,

Arun

Re: install failing here with fedora

CommunityUser — Thu, 11 Dec 2014 14:26:48 GMT

i looked into the directory listed in response.varfile, which is:

sys.installationDir=/home/username/AppDynamics/Controller

and there are folders in there, though there is no bin folder, so i am unable to access the controller.sh script. obviously there has been quite a major failure in the installation process here.

Re: install failing here with fedora

Arun_Dasetty — Fri, 12 Dec 2014 09:08:31 GMT

Hi,

Can you provide the install.log under /home/username/AppDynamics/Controller path and installation.log and response.varfile under /home/username/AppDynamics/Controller/.install4j and also server.log and database.log and startAs.log under /home/username/AppDynamics/Controller/logs path for our review.

Once you collected above logs, please delete the directory /home/username/AppDynamics/Controller after making sure no java and mysql process are running and restart afresh controler install and please copy the completd console stacktrace at shell prompt when installation started using response.varfile process once installation process is completed as well.

To speed up the debug process, Can you mention the account/company name Or email id used to login appdynamics site to see if you have permissions to file a help ticket here ?

Regards,

Arun

Re: install failing here with fedora

CommunityUser — Fri, 12 Dec 2014 15:13:24 GMT

there is no install.log file in: /home/username/AppDynamics/Controller

and there is no hidden folder: /home/username/AppDynamics/Controller/.install4j

so i cannot send you the first 3 files you asked for here.

there are many server.log files and they are constantly being updated, so i have extracted just one of them (5MB size).
(see attached)

i have deleted the controller folder and stopped all java machines - however, you were not explicit in the description of how to ensure mysql instances are stopped that relate to AppDynamics. i am using mysql on my production server here and so cannot just stop all mysql instances. the scripts that i have seen mentioned for stopping the database service(s) in relation to appDynamics do not exist on my server - so i await your explanation of exactly what you advise here in relation to mysql.

"Can you mention the account/company name Or email id used to login appdynamics site to see if you have permissions to file a help ticket here ?"

i am unsure why you are asking me this, since i am logged into the forum here already, how would i be able to write this message if i weren't logged in and had already provided an email address which you can access?

thanks

Re: install failing here with fedora

CommunityUser — Fri, 12 Dec 2014 15:14:40 GMT

the forum software here would not allow me to upload the 3 files i have here correctly. several different meaningless errors were produced and in the end i just clicked 'post' without any attachments. i think that one attachment may have made it through to you.

Re: install failing here with fedora

Arun_Dasetty — Fri, 12 Dec 2014 17:24:41 GMT

Hi,

Apologies for any disconnect here, from forum we do not have option to check user email id have permissions to file help ticket or not , advantage using help ticket system is we can involve experts team to see if it is platform support issue or any workaround could be done, but we have an option to check whether user have provision to file help ticket at help.appdynamics.com from portal team if we have user email id/company name details so that we thought to join a gotomeeting call with you to do quick help to resolve the issue in more faster way. Hope you understand the reason for asking details earlier.

In the server log we see the following error, from which it is evident that mysql is not running so you could kill java process and remove controller dir and start afresh:

[#|2014-12-12T11:26:26.348+0000|WARNING|glassfish3.1.2|javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors|_ThreadID=100;_ThreadName=Thread-2;|RAR5117 : Failed to obtain/create connection from connection pool [ controller_mysql_pool ]. Reason : com.sun.appserv.connectors.internal.api.PoolingException: Connection could not be allocated because: Communications link failure

It looks controller could not establish mysql connection itself, you can check mysql process list and kill only mysql process if running for process initiated by controller installer as follows:

shell> ps -ef | grep "mysql"

Or restarting instance will make sure no controller related process is running and you can deleted controller directory and run afresh install using response.varfile and send use the complete console of stacktrace shown during install process.

Keep us posted if that clarifies your query.

Regards,

Arun