Restarting a CBH Instance

To fix an abnormal instance, you can try restarting it.

Before restarting a bastion host instance, make sure no operations or O&M tasks are in progress. Once the bastion host instance is restarted, ongoing operations and O&M tasks will be forcibly logged out immediately.
You can restart a bastion host instance in the Running status.
Restarting a bastion host instance will interrupt services of the mapped system for about 5 minutes. During this period, the instance status is Restarting, so that the bastion system is unavailable.

Log in to the CBH console.
Click in the upper left corner on the displayed page and select a region.
Locate the row containing the instance you want to restart. In the Operation column, choose More > Restart.
In the displayed dialog box, click OK.

To forcibly restart a CBH instance, select the Forcibly restart check box. Forcibly restarting an instance may cause data loss. Make sure all data files have been saved before performing this operation, and no operations are performed in the mapped CBH system.
The restart process usually takes about 5 minutes. During the restart, the instance status will change to Restarting.

The restart may take a longer time if both the CBH instance version upgrade and capacity expansion are performed.

During the restart, an error might be reported indicating that the instance is abnormal and asking you to contact technical support. This is normal.
Check the instance status. If it changes to Running, the bastion host system is available.