AppD Archive

Failure in startup

CommunityUser
Splunk Employee
Splunk Employee

Hi,

I have recently downloaded and installed Appdynamics Lite 3.9.2.2.

Seems installation went successfull and since I am running on windows so I made the exclusions in Microsoft Forefront endpoint security for DB/data folder.

My server.log does not show any error while startup but I am unable to access the console via

http://localhost:8090/controller/

Can anyone help me with this. (I had installed pro version earlier but uninstalled and installed Lite later)

Below is the server.log database.log and startAS.log

server.log

=====================================

Sep 22, 2014 1:31:32 PM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: JVM invocation command line:
-XX:+UnlockDiagnosticVMOptions
-XX:+HeapDumpOnOutOfMemoryError
-XX:+UseParallelOldGC
-XX:HeapDumpPath=C:\AppDynamics\Controller\appserver\glassfish/../../logs
-XX:ParallelGCThreads=13
-XX:+DisableExplicitGC
-XX:MaxPermSize=256m
-XX:PermSize=64m
-XX:-OmitStackTraceInFastThrow
-XX:NewRatio=2
-XX:SurvivorRatio=10
-XX:-UseAdaptiveSizePolicy
-XX:+LogVMOutput
-Xms1024m
-Xmx1024m
-Xss96k
-server
-javaagent:C:/AppDynamics/Controller/appserver/glassfish/lib/monitor/flashlight-agent.jar
-Dappdynamics.analytics.server.store.url=http://localhost:9080
-Dfelix.fileinstall.disableConfigSave=false
-Djavax.net.ssl.keyStore=C:\AppDynamics\Controller\appserver\glassfish\domains\domain1/config/keystore.jks
-Dappdynamics.controller.eum.adrumextension.urltemplate=de8of677fyt0b.cloudfront.net
-Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true
-Dappdynamics.controller.home=C:\AppDynamics\Controller\appserver\glassfish/../..
-Djava.awt.headless=true
-Dcom.sun.grizzly.accept.op.batch.size=32
-Dfelix.fileinstall.poll=5000
-Djava.endorsed.dirs=C:\AppDynamics\Controller\appserver\glassfish/modules/endorsed;C:\AppDynamics\Controller\appserver\glassfish/lib/endorsed
-Dappdynamics.analytics.accountsvc.key=07329426-fa86-4f27-a81f-26da1b36e315
-Dfelix.fileinstall.bundles.startTransient=true
-Dappdynamics.controller.hostName=127.0.0.1
-Djavax.net.ssl.trustStore=C:\AppDynamics\Controller\appserver\glassfish\domains\domain1/config/cacerts.jks
-Dappdynamics.analytics.enable=false
-Dblitz.service.host=localhost
-Dcom.sun.grizzly.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true
-Dcom.sun.enterprise.security.httpsOutboundKeyAlias=s1as
-Dappdynamics.controller.appserver=C:\AppDynamics\Controller\appserver\glassfish
-DANTLR_USE_DIRECT_CLASS_LOADING=true
-Djava.security.auth.login.config=C:\AppDynamics\Controller\appserver\glassfish\domains\domain1/config/login.conf
-Dgosh.args=--nointeractive
-Dappdynamics.controller.eum.analytics.account.access.key=1a59d1ac-4c35-4df1-9c5d-5fc191003441
-Dosgi.shell.telnet.maxconn=1
-Dappdynamics.controller.services.hostName=NOT001635
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Dfelix.fileinstall.dir=C:\AppDynamics\Controller\appserver\glassfish/modules/autostart/
-Dosgi.shell.telnet.port=6666
-Djava.security.policy=C:\AppDynamics\Controller\appserver\glassfish\domains\domain1/config/server.policy
-Dfelix.fileinstall.log.level=2
-Dcom.sun.aas.instanceRoot=C:\AppDynamics\Controller\appserver\glassfish\domains\domain1
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dosgi.shell.telnet.ip=127.0.0.1
-Dcom.sun.enterprise.server.ss.ASQuickStartup=false
-Dcom.sun.aas.installRoot=C:\AppDynamics\Controller\appserver\glassfish
-Djava.ext.dirs=C:\AppDynamics\Controller\jre/lib/ext;C:\AppDynamics\Controller\jre/jre/lib/ext;C:\AppDynamics\Controller\appserver\glassfish\domains\domain1/lib/ext
-Dfelix.fileinstall.bundles.new.start=true
-Dappdynamics.controller.ui.deeplink.url=http://NOT001635:8090/controller
-Dappdynamics.controller.port=8090
-Dappdynamics.controller.eum.cloud.hostName=agg.eum-appdynamics.com
-Dappdynamics.analytics.local.store.url=http://localhost:9080
-Dblitz.service.port=40000
-Dappdynamics.controller.services.port=8090
-Dappdynamics.controller.eum.analytics.service.hostName=analytics.api.appdynamics.com
-Dappdynamics.controller.eum.beacon.hostName=col.eum-appdynamics.com
Sep 22, 2014 1:31:32 PM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: Successfully launched in 93 msec.

==============================================

database.log

==================================================

140922 13:31:09 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140922 13:31:09 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140922 13:31:16 InnoDB: Waiting for the background threads to start
140922 13:31:17 InnoDB: 5.5.37 started; log sequence number 14716507
140922 13:31:17 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3388
140922 13:31:17 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140922 13:31:17 [Note] Server socket created on IP: '0.0.0.0'.
140922 13:31:17 [Note] Event Scheduler: Loaded 0 events
140922 13:31:17 [Note] C:\AppDynamics\Controller\db\bin\mysqld: ready for connections.
Version: '5.5.37-enterprise-commercial-advanced-log' socket: '' port: 3388 MySQL Enterprise Server - Advanced Edition (Commercial)

===============================================

startAS.log

================================================

Attempting to start domain1.... Please look at the server log for more details.....

0 Karma

Arun_Dasetty
Super Champion

Hi,

Can you please send the following to assist you further is the logs you listed in this post from server.log have more stacktrace then listed:

- install.log under C:\AppDynamics\Controller\

- installation.log under C:\AppDynamics\Controller\.install4j folder

- server.log under C:\AppDynamics\Controller\logs path

If the above said is not the case, and the log stack trace listed is the only stack trace listed in server.log and no logging after line from server.log listed below :

"Sep 22, 2014 1:31:32 PM com.sun.enterprise.admin.launcher.GFLauncherLogger info

INFO: Successfully launched in 93 msec." 

We then request you to make sure you re-installed the controller installer with the following changes:

- Make sure you provided NOT001635 as controller host instead 127.0.0.1 value during installation process

- Check whether NOT001635 host value is resovled in hosts file which is usually located in \windows\system32\drivers\etc path, also make usre you add host entries such that localhost, 127.0.0.1 and NOT001635 in windows hosts file 

Also can you confirm whether you see UI is accessible message after controller installation succeeded at the end?

if not we request you to retry installation with the following args in place in addition to hosts file changes:

cmd> controller.exe Vad-timeout-in-min=<Controller_timeout> -Vstartup-timeout-in-min=<database_timeout>

We assume no windows firewal/anti virus is blocking port 8090 and controller glassgish process here.

Regards,

Arun

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