cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

Infrastructure (Server, Network, Database)

AppD shows Database Agent as Active yet not shown as a process on the server

SOLVED
Richard.Bowen
Creator

AppD shows Database Agent as Active yet not shown as a process on the server

I am attempting to upgrade the Database Agents because of the issue with Logs4J. In AppD I can see four servers that have the database agent installed and are listed as 'Active'.

 

I've connected to the first Windows server to stop the process, allowing me to upgrade and I can't see 'db-agent' listed as a running process. How do I find the process id on Windows to shut it down?

Tags (2)
By replying you agree to the Terms and Conditions of the AppDynamics Community.
AppD shows Database Agent as Active yet not shown as a process on the server
2 REPLIES 2
Ryan.Paredez
Community Manager

Hi @Richard.Bowen,

 

I found this AppD Docs page on the DB agent that talks about how to upgrade it. I did not see anything about the process ID, but please check out the sidebar on that page for the other Docs related to the DB agent.

 

https://docs.appdynamics.com/21.4/en/database-visibility/administer-the-database-agent/upgrade-the-d...

 

Please let me know if this helps.

 

 


Thanks,
Ryan, AppDynamics Community Manager



Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Richard.Bowen
Creator

I read all the documentation and it helped. I didn't install the database agents, so was having to find how they'd been configured. One was running as a Scheduled Task and the others were running as services. I started with the server using the scheduler and there didn't appear to be a matching spid. However, once I found it I was able to upgrade the agent to the latest version.