Troubleshooting for AP Java Upgrade
List of common issues that occur during AP Java upgrade.
This section describes common issues that may occur during AP Java upgrades and how to resolve them.
| Issue | Symptom | Resolution |
|---|---|---|
| Offline upgrade fails due to a running process error | The offline upgrade fails with an error indicating that a process is still running, even though no AP Java process is active. | 1. Navigate to the <INSTALL_DIR>/upgrader/active_processes directory.2. Check for any stale PID files. 3. Remove the stale PID files. 4. Retry the offline upgrade. |
| Upgrade fails during build extraction when using a local build file | The upgrade fails during the build extraction phase when a local build file path .tgz is provided to the Agent.This happens if an extracted build directory or an inner .tgz file is passed instead of the original build archive. | Ensure that: - You pass only the unextracted build file ( .tgz) to the Agent.- The path does not point to any inner or manually extracted .tgz file.Retry the upgrade after correcting the build file path. |
| Upgrade or auto-rollback fails | The upgrade or the automatic rollback operation does not complete successfully. | - Perform an offline rollback to recover the system state. - After the offline rollback completes, verify system stability before retrying the upgrade. |
| “Upgrade is still in progress” error when starting AP Java | AP Java fails to start and reports that an upgrade is still in progress. | 1. Open the <INSTALL_DIR>/upgrader/data/metadata.ini file.2. Verify that the IsUpgradeInProgress parameter value is set to false.3. If the value is set to true, update it to false.4. Save the file. 5. Restart the AP Java application. |
Feedback
Was this page helpful?