topic Re: Events Services can not start up -- immediately after creating a controller with Enterprise Console in Splunk AppDynamics

Events Services can not start up -- immediately after creating a controller with Enterprise Console

Jonathan_Wang — Tue, 13 Aug 2024 15:07:42 GMT

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.

Re: Events Services can not start up -- immediately after creating a controller with Enterprise Console

iamryan — Wed, 14 Aug 2024 16:50:14 GMT

Hi @Jonathan.Wang,

I found this existing post that talks about the same issue. Check it out and let me know if it helps.

https://community.appdynamics.com/t5/Java-Java-Agent-Installation-JVM/Install-Events-service-Error/m-p/52419

Re: Events Services can not start up -- immediately after creating a controller with Enterprise Console

Jonathan_Wang — Fri, 16 Aug 2024 15:13:35 GMT

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

Re: Events Services can not start up -- immediately after creating a controller with Enterprise Console

iamryan — Mon, 19 Aug 2024 17:15:33 GMT

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 on to learn how to manage your cases.

If contact Support or find a solution on your own, please share your learnings as a reply to this post.