Splunk AppDynamics

Data Base Agent error

Farzaneh_Dehgha
New Member

Hello,

The reason for my question is that I have installed the database agent, but on the Controller, I can't see queries and activities.


When I take a look at the logs, I have the following:

image.png

and on controller UI I get this message:

image.png

Thanks for your Help!

Labels (1)
Tags (1)
0 Karma

iamryan
Community Manager
Community Manager

Hi @Farzaneh.Dehghani,

Is your Controller On-prem or SaaS? Can you let me know what Controller version you are running? 

0 Karma

Farzaneh_Dehgha
New Member

Hi Ryan Paredez,

my controller is On-prem and the version is 21.4.4-1301.

Thanks for your Help

0 Karma

iamryan
Community Manager
Community Manager

Hi @Farzaneh.Dehghani,

I found this information in an existing support ticket. Please use it as general guidelines for potentially helping you debug this and finding a solution.

In the problematic environments, below is the component versions:
controller version : 4.5.17
db agent version: 22.2.
ES version : 4.5.2.20599


2nd problematic Env: 
controller version : 4.5.17
db agent version: 4.5.18
 
- So we started by checking the 500 error in UI. Also, you were not getting any metrics for wait state/queries or activity tab of the database agent, rest all data was reporting.
 
- Since this error meant a problem from the ES(Event Service) side, we thought of checking if other components using ES were working or not on this controller but you didn't have EUM or analytics setup.
 
- But when we went on the Analytics dashboard we could see the "Failed to receive query results [HtTTP 401 Unauthorized]" error there
 
- So We logged into the admin.jsp and checked if the ES key was correctly stored there or not as compared to the ES properties file. And we could see some keys had mismatch.
 
- The "on.premise.event.service.key" was not equals to the value of "ad.accountmanager.key.controller" key in the in events-service-api-store.properties file of ES.
 
- So we fixed it by setting the value correctly in admin.jsp. However still 401 error was showing up.
- We checked the ES file again and noticed that one more key was incorrect. Basically, all these below property value should be same :
ad.accountmanager.key.controller=[Redacted]
ad.accountmanager.key.mds=[Redacted]
ad.accountmanager.key.ops=[Redacted]
However in your case, "ad.accountmanager.key.ops" key was also different from the other two.
 
 
- So we added value for ad.accountmanager.key.mds in events-service-api-store.properties as same as ad.accountmanager.key.controller's value and restarted the event service.
 
- However ES failed to stop due to JAVA_HOME missing. So we set the JAVA_HOME first : 
export JAVA_HOME= "/opt/appdynamics/platform/product/jre/<version>"
 
- Then it was able to stop and restart. 
- Post restart we reloaded the UI and we could see the error was gone and all the db mon data was also reporting now. 
- So the issue is resolved for this controller and everything is working fine now.  Attaching a few screenshots captured during the call.
 
 
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!

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

SplunkTrust Application Period is Officially OPEN!

It's that time, folks! The application/nomination period for the 2026-2027 SplunkTrust is officially open. If ...

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