You can troubleshoot upgrade problems by reviewing the error logs. If the Omnissa Access appliance does not start, you can revert to a previous instance by rolling back to a snapshot.
For specific upgrade error scenarios, see the following topics:
- Checking the Omnissa Access Upgrade Error Logs: Review the upgrade error logs to resolve errors that occur during an upgrade.
- Rolling Back to Snapshots of the Original Omnissa Access Instance: Revert to a snapshot of the original instance if Omnissa Access does not start properly after an upgrade.
- Collecting an Omnissa Access Log File Bundle: Collect a bundle of log files from the Omnissa Access appliance configuration page.
- Chain Omnissa Access Upgrade Fails During the Preupdate Process: Resolve an upgrade failure during the pre-update process caused by duplicate
bc-fipsjar files. - Omnissa Access Cluster Upgrade Hangs at the RPMDB Rebuild Stage: Resolve a stalled cluster upgrade caused by a secondary node that stops responding during the RPMDB rebuild stage.
Questa pagina è stata utile?