Skip to main content
October 26, 2021
Question

Starting_and_Stopping_Appian (Error starting services)

  • October 26, 2021
  • 3 replies
  • 0 views

Hello,

I'm trying to start the Appian instance, and I'm getting a loopback when running the service startup:
./start.sh -p * -s all
keeps returning:

execution01: Start initiated
Starting execution02
execution02: Start initiated

Waiting for services to start...
  analytics00 in STARTING state, REPLICA mode
  analytics01 in STARTING state, REPLICA mode
  analytics02 in STARTING state, REPLICA mode
  channels in STARTING state, REPLICA mode
  content in STARTING state, REPLICA mode
  download-stats in STARTING state, REPLICA mode
  execution00 in STARTING state, REPLICA mode
  execution01 in STARTING state, REPLICA mode
  execution02 in STARTING state, REPLICA mode
  forums in STARTING state, REPLICA mode
  groups in STARTING state, REPLICA mode
  notifications in STARTING state, REPLICA mode
  notifications-email in STARTING state, REPLICA mode
  portal in STARTING state, REPLICA mode
  process-design in STARTING state, REPLICA mode

So far I have followed the steps described in the installation without any problems in the process. Please, can you tell me where I can get a trace to detect the problem, or if someone has already encountered this situation?

Thank you very much in advance.
I will keep investigating.
Best regards.

Jaime.

3 replies

abeerm
October 31, 2021

Me too, I faced the same problem 

is there any declaration??

smithaa0003
February 8, 2022

I am facing the same issue. I am trying to implement HA architecture and when starting the application, it is stuck with CRASHLOOPBACKOFF. The license is active (Not expired). Still facing the same issue.

February 8, 2022

For what it's worth, my problem was with the definitive licence and its relation with the hostname of the machine. You can check the correct relation of the license with the hostname with the command: "<Appian-home>/server/_bin/k/linux64/k"


More information about the boot error can be found in the following log:

<Appian-home>/logs/service_manager.log