engines goes into CRASHLOOPBACKOFF state, Replica mode

RE: engines goes into CRASHLOOPBACKOFF state, Replica mode

Rama Krishna Golla — Wed, 03 Jan 2024 03:14:08 GMT

There is license issue. Get the updated license and try it will work.

RE: engines goes into CRASHLOOPBACKOFF state, Replica mode

jong8218 — Wed, 19 Apr 2023 14:33:58 GMT

Old call, but I found the issue to be as Tushar described. Needed the k3.lic file in <APPIAN_HOME>/server/_bin/k/linux64/, then all came up without error.

RE: engines goes into CRASHLOOPBACKOFF state, Replica mode

Sai Manam — Thu, 10 Feb 2022 13:00:43 GMT

i tried this approach but still i do face the same issue. any other ideas

RE: engines goes into CRASHLOOPBACKOFF state, Replica mode

Sai Manam — Thu, 10 Feb 2022 12:59:58 GMT

i am facing similar issue. were you able to resolve?

RE: engines goes into CRASHLOOPBACKOFF state, Replica mode

Tushar — Tue, 08 Feb 2022 15:52:53 GMT

I resolved this issue for my local windows machine by following below steps.

1. remove k3, k4 license file from Appian home directory

2. place correct k3, k4 license file in repo home directory

3. run appian configuration again

Note: while I was getting this error (CRASHLOOPBACKOFF ) I was able to see below error in service_manager.log

com.appian.komodo.engine.connection.InvalidKLicenseException: execution02 failed to start due to an invalid K license.

RE: engines goes into CRASHLOOPBACKOFF state, Replica mode

smithaa0003 — Tue, 08 Feb 2022 10:24:20 GMT

I am facing the same issue. I am trying to implement HA architecture for appian (Self managed instance on linux) .The license is correct. I have installed the latest license. Still the application is stuck in crash loopback off