Splunk AppDynamics

Cannnot Upgrade Enterprise console version

Tadeu_Alves
Explorer

Hi there everyone,


Today i'm trying to update my Enterprise Console to the latest version, right now i'm using the AppDynamics Version 20.7.0-22903.


Downloaded the Enterprise Console 21.4.6
that is the latest version avaliable from my management interface


Following all steps i got stuck in this action:

image.png

The the database is running without errors, i can access the controller host database at the console host through bash without problems. Even with everything working everytime i try to update or execute the platform-setup-x64-linux-21.4.6.24635.sh script get this message. Is there something more that i can debug to find out what is going on?

Thank you.

Labels (3)
Tags (2)
0 Karma
1 Solution

Tadeu_Alves
Explorer

Yeah it worked man.

Had to change most of the passwords, cause someone changed and didn't leave the right credentials...

View solution in original post

iamryan
Community Manager
Community Manager
0 Karma

Tadeu_Alves
Explorer

Yeah it worked man.

Had to change most of the passwords, cause someone changed and didn't leave the right credentials...

iamryan
Community Manager
Community Manager

Hi @Tadeu.Alves,

Thanks for following back up! Glad to see its working now.

0 Karma

Tadeu_Alves
Explorer

Yeah great to see that it's not complicated if you have all the credentials...

O yeah do you know what could be that my controller is critical in console even if everything is working fine?

image.jpeg

and thanks again for the help!!!

0 Karma

iamryan
Community Manager
Community Manager

Hey @Hiroki.Ito,

Do you happen to know anything about @Tadeu.Alves recent comment above?

0 Karma

Hiroki_Ito
Contributor

Hi @Tadeu.Alves ,

CC: @Ryan.Paredez ,

There can be several reasons, so it may be necessary to investigate the log of enterprise console.
Could you please check <ec_home>/platform-admin/logs/platform-admin-server.log ?
You may see logs like "Discovered Primary controller health status on host '<hostname>': UNHEALTHY."
Could you please check if there are any ERROR or suspicious logs around that line and share the result?

If there is a line like "Controller status check failed for the url http://<hostname>:8090/controller/rest/serverstatus" could you also share the result of curl command to the url?
curl -v http://<hostname>:8090/controller/rest/serverstatus

Best Regards,
Hiroki
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!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...