Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
12-14-2021 01:58 AM
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?
Solved! Go to Solution.
12-14-2021 08:39 AM
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.
Please let me know if this helps.
Thanks,
Ryan, Cisco 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.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.
12-14-2021 09:09 AM
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.
User | Count |
---|---|
3 | |
2 | |
2 | |
1 | |
1 | |
1 |
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form