Problem Symptom
During an upgrade, a node is faulty and repeatedly powered off or restarted. As a result, a file system is damaged, the FSM node upgrade fails, and the upgrade cannot be resumed.
Problem Diagnosis
The upgrade is paused, and the faulty node is displayed on DeviceManager.
Log in to the faulty node and run the cat /var/log/oam/fsm/manager/script/fsm.deploy.script.log command to check the failure cause. The log shows that some database operations fail.
Run the cat /var/log/oam/oam-u/oam-gaussdb/run/gaussdb.log command to view the GaussDB log. The log contains information indicating that a file or directory is damaged.
Causes
The file system where GaussDB is located is damaged due to a node fault (repeated power-off or restart). As a result, GaussDB is abnormal, and database commands fail to be executed.
Solution
Log in to the faulty node and run the su - ommdba command to switch to user ommdba.
Run the gs_ctl build command to rebuild the database.
Check After Recovery
Check whether the upgrade can be performed successfully.
Suggestion and Summary
N/A
Applicable Versions
All
