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
08-13-2024 08:07 AM
Hello ALL,
I installed On-Premises AppDynamics 24.7 on Rocky Linux 9.4 host. After complete the Enterprise Console installation (through installation script "platform-setup-x64-linux-24.7.0.10038.sh", I continued to setup the Controller (demo profile) and Events Service. The three jobs completed successfully, as shown below.
Controller starts OK.
But Events Service can not start up. There is Red Critical health status highlighted.
The error message: Task failed: Starting the Events Service api store node ...
How to make Events Service get started up ? Thanks.
08-14-2024 09:50 AM
Hi @Jonathan.Wang,
I found this existing post that talks about the same issue. Check it out and let me know if it 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.
08-16-2024 08:13 AM
After reading through these cases, I can not still figure out an effective way to resolve my issue. I repeated the installation process carefully, but the result was the same. The Events Service resides on the same machine as Enterprise Console and Controller. The machine host name is specified in /etc/hosts as "appd-ctl", the name shown in the error messages. I even shutdown the firewall when starting the Events Service, but there was no difference.
-------------------- error message ------------
Task failed: Starting the Events Service api store node
on host: appd-ctl
as user: root
with message: Connection to [<a href="<a href="http://appd-ctl:9080/_ping" target="_blank">http://appd-ctl:9080/_ping</a>" target="_blank"><a href="http://appd-ctl:9080/_ping" target="_blank">http://appd-ctl:9080/_ping</a></a>] failed due to [Failed to connect to appd-ctl/fe80:0:0:0:be24:11ff:fe59:c94a%2:9080].
---------------------------------------------------------------------
. . . . . . .
INFO [2024-08-16 14:35:06.202] com.appdynamics.orcha.core.executor.DefaultPlaybookExecutor: Executing : Starting the Events Service api store node
ERROR [2024-08-16 14:45:07.060] com.appdynamics.orcha.core.executor.DefaultPlaybookExecutor: Error executing task: TaskSpec[async=false,deleteDir=true,heartbeatInterval=60,ignoreErrors=false,localModule=false,longRunning=false,longRunningInitInterval=500,longRunningPollInterval=1000,longRunningWriteInterval=200,name=Starting the Events Service api store node,operationSpecList=[ShellSpec[chdir=/opt/appdynamics/platform/product/events-service/processor,command=[nohup, bin/events-service.sh, start, -p, conf/events-service-api-store.properties],commandForLogging=<null>,consoleInputFile=<null>,consoleOutputFile=<null>,environment={DONOTDAEMONIZE=true,JAVA_HOME=/opt/appdynamics/platform/product/jre/1.8.0_422},failOnError=true,hideContext=false,spawn=true,timeout=0,assertionSpecList=[],isLocalOperation=false,name=shell], UriSpec[body=<null>,failOnError=true,format=TEXT,fragment=<null>,headers=<null>,hiddenQueryStringVars=<null>,host=<null>,ignoreStatusCode=-1,method=get,path=<null>,port=<null>,query=<null>,scheme=<null>,timeout=60,uri=http://appd-ctl:9080/_ping,userName=<null>,retryInterval=5,retryTimeout=600,assertionSpecList=[],isLocalOperation=false,name=uri]],registerOutputAs=<null>,runLocal=false,separateProcess=false,taskSshTimeout=7200000,uid=<null>,updateThreshold=30]
ERROR [2024-08-16 14:45:07.073] com.appdynamics.orcha.core.OrchaRunnerImpl: Error executing:
ERROR [2024-08-16 14:45:07.085] com.appdynamics.platformadmin.core.job.JobProcessor: Platform/Job [1/818959e9-5f25-49af-9510-591ca406a7f0]: Stage [Start Events Service Cluster] failed due to [Task failed: Starting the Events Service api store node
on host: appd-ctl
as user: root
with message: Connection to [http://appd-ctl:9080/_ping] failed due to [Failed to connect to appd-ctl/fe80:0:0:0:be24:11ff:fe59:c94a%2:9080].]
08-19-2024 10:15 AM - edited 08-19-2024 10:18 AM
Hi @Jonathan.Wang,
Thank you for following up. Since the community has not jumped in yet either. I think the best next step is to contact Support.
AppDynamics is migrating our Support case handling system to Cisco Support Case Manager (SCM). Read ...
If contact Support or find a solution on your own, please share your learnings as a reply to this post.
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.
User | Count |
---|---|
2 | |
1 | |
1 | |
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