AppD Archive

Trying out Lite getting java exceptions in Database Monitoring > Databases

CommunityUser
Splunk Employee
Splunk Employee

Hi,

Not sure what's wrong. The controller url is running on port 8090 fine. Any suggestions greatly appreciated.

image.png

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

This generally means that the event service on the controller has not been started or that port 9080, which the event service uses, is not available.

To start the event service on the controller cd to <CONTROLLER-HOME>/bin and execute controller.sh (or controller.bat) start-events-service

This will run the events service on port 9080.

In addition, that the db-agent is communicating with the controller by looking at the list of agents. There should be an agent called Database Monitoring Master.

Hope this helps.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi

I'm having the same issue as thread author, but the events service does not want to launch for me.

When I do the suggested command I see that for few seconds there is something on  the 9080 port but then it dissapears

c:\AppDynamics\Controller\bin>controller.bat start-events-service
[INFO] Using mysql from "c:\AppDynamics\Controller"\db\bin
[INFO] Using mysql configuration file: "c:\AppDynamics\Controller"\db\db.cnf
-Xmx512m -Xms512m
JVM heap options are set in JAVA_OPTS. Default heap options will not be added
Starting analytics-processor with the arguments -y conf\analytics-all.yml -p con
f\analytics-all.properties -Xmx512m -Xms512m -XX:MaxPermSize=512m -XX:ReservedCo
deCacheSize=64m -XX:+UseConcMarkSweepGC -XX:+UseCMSInitiatingOccupancyOnly -XX:C
MSInitiatingOccupancyFraction=70 -XX:+UseParNewGC -XX:+ScavengeBeforeFullGC -XX:
+DisableExplicitGC -XX:+PrintPromotionFailure -XX:+PrintClassHistogramBeforeFull
GC -XX:+PrintTenuringDistribution -XX:+PrintGCDateStamps -XX:PrintFLSStatistics=
1 -XX:+PrintGCDetails -XX:GCLogFileSize=64m -XX:NumberOfGCLogFiles=2 -XX:+UseGCL
ogFileRotation -verbose:gc
c:\AppDynamics\Controller\bin>netstat -a -n -o | find "9080"
  TCP    0.0.0.0:9080           0.0.0.0:0              LISTENING       3900
  TCP    [::]:9080              [::]:0                 LISTENING       3900

c:\AppDynamics\Controller\bin>netstat -a -n -o | find "9080"

c:\AppDynamics\Controller\bin>

EDIT:

ok I found the problem - there are two versions of lucene in this product, and elastic search works only with 4.9. After deleting 4.10.2 it started to work

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Awesome. Working now. Thanks.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,

Tried but can't find the readme.htm in local folder or online docs for this next error. Any suggestion where I can find it?

image.png

Thanks,

Brian

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Thanks again. It was the  "allow full access to the WBEM Scripting Locator"  🙂

0 Karma
Get Updates on the Splunk Community!

Splunk Observability Cloud’s AI Assistant in Action Series: Analyzing and ...

This is the second post in our Splunk Observability Cloud’s AI Assistant in Action series, in which we look at ...

Elevate Your Organization with Splunk’s Next Platform Evolution

 Thursday, July 10, 2025  |  11AM PDT / 2PM EDT Whether you're managing complex deployments or looking to ...

Splunk Answers Content Calendar, June Edition

Get ready for this week’s post dedicated to Splunk Dashboards! We're celebrating the power of community by ...