Issue upgrading Appian from v22.4 to v24.3

RE: Issue upgrading Appian from v22.4 to v24.3

Hishore Nallasivam — Fri, 10 Jan 2025 09:47:37 GMT

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.

RE: Issue upgrading Appian from v22.4 to v24.3

David Jimenez — Fri, 29 Nov 2024 08:34:48 GMT

Check the folders, because in one of latest upgrades we realized that we had to copy another folder... maybe you are missing someone...

Check the list in the updagre guide that correspond to your version..

RE: Issue upgrading Appian from v22.4 to v24.3

jesusa310 — Thu, 28 Nov 2024 11:15:40 GMT

Hi all again,

I am attaching the service manager log with the transaction exception that was added for one of the engines. Other failing engines show a similar error. Is it possible to recover the engines knowing the transaction id without losing running processes? Or at least minimising the number of instances lost?

2024-11-25 13:47:50,920 [KafkaTransactionLogService [execution00]-execution00-REPLICA STARTING] INFO  com.appian.komodo.log.KafkaTransactionLogService - execution00 REPLICA transaction log state calculated in 2 seconds: TransactionLogState{appendedCount=14879, firstTransactionId=Optional[8050800], lastTransactionId=Optional[8065678]}
2024-11-25 13:47:50,921 [shared-cached-threadpool-10] ERROR com.appian.komodo.translog.TransactionReplayer - Unable to find transaction 1 in the transaction log for execution00.  Please verify that an old kdb was not used.
2024-11-25 13:47:50,921 [shared-cached-threadpool-10] ERROR com.appian.komodo.translog.TransactionReplayer - Transaction replay failed for execution00
com.appian.komodo.translog.TransactionNotFoundException: null

RE: Issue upgrading Appian from v22.4 to v24.3

jesusa310 — Wed, 27 Nov 2024 15:42:02 GMT

Thanks for your answers. We use a script that copies the folders from the backup and have been used in multiple upgrades without problems. The cp command did not return any failure.

We also stop Appian in the order indicated in the documentation: tomcat, search-server,. data-server, services

RE: Issue upgrading Appian from v22.4 to v24.3

shrikant.pol — Wed, 27 Nov 2024 07:09:24 GMT

hi jesusa310

As mentioned in issue it seems data file for process are not copied correctly. (/server/process/analytics/0000/gw1/ .../server/process/analytics/0002/gw1/ )

Please copy those files then it will work.

Regards,

Shrikant Pol

RE: Issue upgrading Appian from v22.4 to v24.3

David Jimenez — Tue, 26 Nov 2024 11:39:26 GMT

CRASHLOOPBACKOFF state usually occurs when there is a problem with the sync of the engines..In that situation the only way to recover the system is the recovery script, and you will always loose information....

As a recomendation, always backup your instances, (and if possible database), and stop servers and engines following the order stablished (tomcat, search-server,. data-server, services)....