During the Upgrade of Login Authentication Components Such As iBase, OMM_C, and OAM-GaussDB, the Node Is Faulty and the Upgrade Cannot Be Resumed Afte

Problem Symptom

During the upgrade of login authentication components such as iBase, OMM_C, and OAM-GaussDB on a management node, the node is powered off or restarted unexpectedly. As a result, the upgrade fails. After the node is restored, you cannot log in to DeviceManager, or after retrying the upgrade on the upgrade page of DeviceManager. the upgrade progress of some components such as NMS is 0% and an upgrade failure message is reported. As a result, the upgrade task cannot be automatically resumed.

Problem Diagnosis

1. During the upgrade, error 502 is reported on DeviceManager.

2. During the upgrade, a message is displayed on DeviceManager, indicating that communications with the device are abnormal and you need to check whether the network connection or device status is normal.

3. During the upgrade, after the OAM_GaussDB component is restored, retry the upgrade on DeviceManager. Components such as NMS fail to be upgraded.

Causes

During the upgrade of components such as iBase, OMM_C, and OAM-GaussDB, the node is faulty or restarted. As a result, the upgrade task is interrupted and the process exits. After the upgrade task resumes, tokens need to be obtained from the iBase, OMM_C, and OAM-GaussDB components. However, such processes are abnormal and tokens cannot be obtained. As a result, the entire upgrade task cannot continue.

Solution

1. Use SSH to log in to the active FSM node and switch to user root.

2. Run the ps -ef command to check whether the iBase, /OSM/bin/aa (process name of the OMM_C component), and OAM-GaussDB processes are available.

3. Run the cd /opt/fusionstorage/repository/deploymanager_pkg/micro command to go to the directory where the component packages are stored and find the component package whose process is unavailable in 2. For example, if the iBase process is unavailable, go to the action directory of the iBase component package.

   Run the bash appctl.sh upgrade; bash appctl.sh start; command to upgrade and start the iBase service.

4. Log out of DeviceManager and log in again. On the Upgrade page, click Retry to continue the upgrade.

Check After Recovery

N/A

Suggestion and Summary

N/A

Applicable Versions

All