Splunk AppDynamics

Controller server don´t start

CommunityUser
Splunk Employee
Splunk Employee

Hi 

I´am new in Appdynamics have some problem after shutdown (./stopController.sh) it wont start anymore or it seems to start but it dosen´t work when i try to connect to the console i get http error 500 and i get this messagen in the server.log

[#|2017-04-24T13:43:51.174+0200|SEVERE|glassfish 4.1|javax.enterprise.system.core|_ThreadID=31;_ThreadName=RunLevelControllerThread-1493034179004;_TimeMillis=1493034231174;_LevelValue=1000;
_MessageID=NCLS-CORE-00026;|Exception during lifecycle processing
org.glassfish.deployment.common.DeploymentException: Error in linking security policy for controller -- Inconsistent Module State
at com.sun.enterprise.security.ee.SecurityUtil.linkPolicyFile(SecurityUtil.java:336)
at com.sun.enterprise.security.ee.SecurityDeployer.linkPolicies(SecurityDeployer.java:319)
at com.sun.enterprise.security.ee.SecurityDeployer.access$100(SecurityDeployer.java:87)
at com.sun.enterprise.security.ee.SecurityDeployer$AppDeployEventListener.event(SecurityDeployer.java:145)
at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131)
at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:328)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:496)
at com.sun.enterprise.v3.server.ApplicationLoaderService.processApplication(ApplicationLoaderService.java:406)
at com.sun.enterprise.v3.server.ApplicationLoaderService.postConstruct(ApplicationLoaderService.java:243)
at org.jvnet.hk2.internal.ClazzCreator.postConstructMe(ClazzCreator.java:326)
at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:374)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:471)
at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:228)
at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:85)
at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2072)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:114)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:88)
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(CurrentTaskFuture.java:1213)
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.run(CurrentTaskFuture.java:1144)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java)
at java.lang.Thread.run(Thread.java:745)
|#]

[#|2017-04-24T13:43:51.175+0200|SEVERE|glassfish 4.1|javax.enterprise.system.core|_ThreadID=31;_ThreadName=RunLevelControllerThread-1493034179004;_TimeMillis=1493034231175;_LevelValue=1000;|Exception while loading the app|#]

[#|2017-04-24T13:43:51.266+0200|SEVERE|glassfish 4.1|javax.enterprise.web|_ThreadID=31;_ThreadName=RunLevelControllerThread-1493034179004;_TimeMillis=1493034231266;_LevelValue=1000;_MessageID=AS-WEB-GLUE-00192;|Undeployment failed for context /controller|#]

//Thomas

Labels (3)
0 Karma
1 Solution

Rajesh_Putta
Communicator

Hi Thomas,

Can you please do a stepwise restart of controller and let us know your observations.

  1. Stop the controller app-server
    /controller/bin/controller.sh stop-appserver

  2. Stop the DB
    /controller/bin/controller.sh stop-db

  3. Make sure that the mysql and java processes are not running on the machine, if it exists, kill them. Below command should not return any process:
    ps -ef | grep java
    ps -ef | grep mysql

  4. Start the DB
    /controller/bin/controller.sh start-db

  5. Start the controller app-server
    /controller/bin/controller.sh start-appserver

This should hopefully fix the issue.


Let us know how it goes. Please wait for 10-15 mins once you see the controller has started message after you run point #5. 

One reason where you see HTTP 500 error is that controller could be in a state of warming up and it might take controller to do some house keeping tasks related to database. During that time, you could expect to see HTTP 500

Thanks

Rajesh

View solution in original post

0 Karma

Rajesh_Putta
Communicator

Hi Thomas,

Can you please do a stepwise restart of controller and let us know your observations.

  1. Stop the controller app-server
    /controller/bin/controller.sh stop-appserver

  2. Stop the DB
    /controller/bin/controller.sh stop-db

  3. Make sure that the mysql and java processes are not running on the machine, if it exists, kill them. Below command should not return any process:
    ps -ef | grep java
    ps -ef | grep mysql

  4. Start the DB
    /controller/bin/controller.sh start-db

  5. Start the controller app-server
    /controller/bin/controller.sh start-appserver

This should hopefully fix the issue.


Let us know how it goes. Please wait for 10-15 mins once you see the controller has started message after you run point #5. 

One reason where you see HTTP 500 error is that controller could be in a state of warming up and it might take controller to do some house keeping tasks related to database. During that time, you could expect to see HTTP 500

Thanks

Rajesh

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi

I reinstalled the controller and now it works fine.

//Thomas

0 Karma

Rajesh_Putta
Communicator

Hi Thomas,

Glad to hear this good news.

Thanks

Rajesh

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...