AppD Archive

Queries don't load in case of mysql DB monitioring

CommunityUser
Splunk Employee
Splunk Employee

On clicking Query Page we get follwing message and screen shows "Loading..."

"We aren't able to load data from the event service. If this is a SaaS controller, please open a support ticket. If this is on-premise installation, please make sure that the event service is running. See the documentation for instructions on starting the event service. For more details on this error, please see the controller server log."

Dashboard and Live view do provide information.

When I see DB agent logs, I see this error trace

12:31:57,596 WARN [AD Thread-Metric Reporter0] DBEntitySubscriber:184 - Error reading the response.
com.singularity.ee.rest.ResponseReadException: Error in controller in processing binary request Wait Time Measurement - null
at com.singularity.ee.rest.controller.request.ABinaryControllerRequest.<init>(ABinaryControllerRequest.java:65)
at com.singularity.ee.rest.controller.request.dbmon.WaitTimeMeasurementCollectorRequest.<init>(WaitTimeMeasurementCollectorRequest.java:34)
at com.singularity.ee.agent.dbagent.service.dbmonitorservice.DBEntitySubscriber.reportMeasurements(DBEntitySubscriber.java:182)
at com.singularity.ee.agent.dbagent.service.dbmonitorservice.DBMonitorService.reportMeasurements(DBMonitorService.java:215)
at com.singularity.ee.agent.dbagent.service.dbmonitorservice.DBEntityReporter.run(DBEntityReporter.java:87)
at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:107)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
at java.lang.Thread.run(Thread.java:745)

Can someone tell what I am missing here.

0 Karma

Arun_Dasetty
Super Champion

Hi,

We see both you have both saas and onPremise contorller as per our portal , Can you see if below suggestions helps:

a) If onPremise controller:

cmd> contorller.bat/sh stop-events-service

cmd> contorller.bat/sh start-events-service

and then restart db agent java process and see how it goes with error in UI?

b) As the message itself say "Error in controller in processing binary request Wait Time Measurement - null" controller failed to process request send by db agent , So can you try below:

- stop the db agents and delete the target affected collector config from add collectors section in UI 

- now create a new collector in UI with new name say: mysqldbtest  and restart db agent as follows and see how it goes:

java -Ddbagent.name="mysqldbtest " -Dappdynamics.agent.uniqueHostId="mysqldbtest " -Ddbagent.is.backup.for="mysqldbtest" -jar <dbagent_install_dir>/db-agent.jar

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

First of all thanks alot for answering. It really helped.

I restarted controller using :

cmd> contorller.bat/sh stop-events-service

cmd> contorller.bat/sh start-events-service

and then had to restart DB agent twice.

After that system seems to run fine.

Only concern i now have is, that every time we add new agent, do we need to restart controller/event-service. Ideally that shouldnt be the case, as far as i understand, or this was just one time issue.

0 Karma

Arun_Dasetty
Super Champion

Hi,

Glad to hear that news from you, regarding latest query, i confirm you would not need to restart events service when you start new agent for sure, Hope that clarifies.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
Ok. Thanks AKumar for clarifying.

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