In order to safely upgrade an Appian environment, the engines in the source environment must be shut down using the stop script. Ungraceful shutdowns can introduce data inconsistencies and can lead to a failed upgrade.
The isSuitableForUpgrade.sh script can be used to detect if engines are not shutdown gracefully before the upgrade is performed. This helps validate the state of the engine data and confirms whether the data is in a state in which it can be safely be upgraded to a higher Appian version.
This script currently only works with single node and highly available(HA) topologies where the service_manager.log is in a central location. This script currently does not work with distributed topologies where the service_manager.log can be present on multiple servers.
How to execute the script:
<APPIAN_HOME>/shared-logs
<APPIAN_HOME>/logs
chmod +x isSuitableForUpgrade.sh
./isSuitableForUpgrade.sh -p <your_service_manager_password>
Date of evaluation: * The below results refer to the shutdown performed at * If the timestamp is incorrect, please start and stop your engines then try again.15 engines are suitable for upgrade15 total engines detected All engines are suitable for upgradeIt is safe to proceed with the upgrade
Date of evaluation: * The below results refer to the shutdown performed at * If the timestamp is incorrect, please start and stop your engines then try again.12 engines are suitable for upgrade15 total engines detectedOne or more engines is unsuitable for upgradePlease perform a full start-up of all engines, gracefully shut down all engines, then try again
Note: If you are consistently unable to show that all engines are suitable for upgrade, please create a case with Appian Support.
This article applies to self-managed versions of Appian 19.4 and later hosted on Linux
Last Reviewed: August 2023