Issue upgrading Appian from v22.4 to v24.3

Question

Hi all,

I am writing with regards to an issue that we have found while upgrading from Appian 22.4 to Appian 24.3 in both the Dev and Test environments.

We followed the procedure described in the documentation and found no issues during the upgrade process. However, when starting the Appian engines, we noticed the 3 analytics engines and the 3 execution engines were in CRASHLOOPBACKOFF state. The other engines were in RUNNING state as expected.

We resolved the issue running the recovery script with these parameters:

./recovery.sh -p <password> -s <failing_engines> -ni

Then, the engines started correctly, and all the servers started up fine as well. However, the exiting process instances had disappeared from the Appian design view.

Is there any way to refine the parameters used in the recovery script or another solution to recover the engines in CRASHLOOPBACKOFF state? As the same issue has happened in the Dev and Test environments we are concerned that it could happen again in production, where we dont want to lose running instances.

Kind regards,

Jesus

Hishore Nallasivam · Answer

It seems that checkpointing did not occur properly when stopping the Appian services, which caused the error. To avoid this, ensure that engines are checkpointed properly after stopping the Appian services. Alternatively, you can run a manual checkpoint before stopping the Appian engines.