No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Troubleshooting Guide 02

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Maintenance

Maintenance

Large Time Difference Between the NTP Server and Backup Manager or Backup Server

Symptom

There is a large time difference between the NTP server and backup manager or backup server, and the eBackup interface displays an alarm.

Possible Causes

If the network between the NTP server and backup manager or backup server is disconnected or the time of the NTP server is modified, there may be a time difference between the NTP server and backup manager or backup server. When the time difference is greater than 1 minute, the eBackup interface displays an alarm.

The backup manager or backup server attempts to synchronize time with the NTP server. If the time difference is large, a large time change occurs on the backup manager or backup server after time synchronization. As a result, backup jobs are not executed as planned.

NOTE:

If the impact is little according to your assessment, you may take no actions. Otherwise, perform the following steps to resolve the problem. After you perform the following steps, the eBackup service will restart, and the eBackup system cannot provide services externally for a few seconds.

Procedure
  1. Log in to the backup manager or backup server GUI using a browser.

    Login address: https://IP address corresponding to the Workflow-Management-Float-IP field or IP address corresponding to the datamover_management_float_ip field:8088

    Default account: admin. Default password: Cloud12#$ for installation using HUAWEI CLOUD Stack Deploy, and PXU9@ctuNov17! for manual installation.

  2. Choose > System Time & Zone.
  3. Enter the local IP address of the backup server (127.0.0.1) in the NTP Server text box, and click OK.
  4. In the Warning dialog box, click OK.
  5. Re-log in to the backup manager or backup server GUI.
  6. Choose > System Time & Zone.
  7. Enter the IP address of the NTP server in the NTP Server text box, and click OK.
  8. In the Warning dialog box, click OK.

The NTP Service of a Backup Proxy Is Abnormal, the Time of the Backup Proxy Fails to Be Synchronized with that of the backup server, and No Alarm Is Generated

Symptom

The time of a backup proxy is not synchronized with that of the backup server, and no alarm is generated.

Possible Causes

A row starting with server in file /etc/ntp.conf does not exist. As a result, NTP server configurations fail to be updated.

Procedure
  1. Use PuTTY to log in to the backup proxy whose NTP service is abnormal with the management IP address.

    Default account: hcp; default password: PXU9@ctuNov17!

  2. Run the su root command and enter the password of account root to switch to user root.

    The default password of the root account is Cloud12#$.

  3. Run the TMOUT=0 command to prevent the system from exiting due to timeout.

    NOTE:

    After you run the preceding command, the system continues to run even when no operation is performed, posing security risks. For security purposes, you are advised to run the exit command to exit the system after completing your operations.

  4. Run the cat /etc/ntp.conf | grep "^server*" command, and check whether any command output is returned:

    • If any command output is returned, contact technical support engineers.
    • Otherwise, go to 5.

  5. Log in to the backup server GUI using a browser.

    Login address: https://IP address corresponding to the datamover_management_float_ip field:8088

    Default account: admin. Default password: Cloud12#$ for installation using HUAWEI CLOUD Stack Deploy, and PXU9@ctuNov17! for manual installation.

  6. In the navigation tree, choose > Server.
  7. Query the IP address of the internal communication plane of the backup server.

    • HA scenario:

      Query the IP address of the internal communication plane of the backup server whose role is Primary.

    • Non-HA scenario:

      Query the IP address of the internal communication plane of the backup server.

  8. On the abnormal Proxy, run the echo "server IP address prefer minpoll 4 maxpoll 5" >> /etc/ntp.conf command to add an NTP server.

    IP address is obtained in 7.

  9. Run the following commands in sequence to make the settings effective:

    cd /etc/init.d

    hwclock --systohc > /dev/null 2>&1

    service ntp restart > /dev/null 2>&1

    chkconfig ntp 3 > /dev/null 2>&1

    chkconfig ntp 5 > /dev/null 2>&1

    chkconfig ntp on > /dev/null 2>&1

    cd -

  10. Run the service ntp status command, and check whether the command output contains the internal communication IP address of the backup server:

    • If the internal communication IP address is returned, this issue is resolved.

      Example:

    • Otherwise, contact technical support engineers.

Backup, Restore, or Deletion Jobs on eBackup Fail After Cross-AZ Restore Jobs Are Performed

Symptom

After cross-Availability Zone (AZ) restore jobs are performed, backup, restore, or deletion jobs on eBackup fail. Logs of the corresponding microservices contain error information database disk image is malformed.

Possible Causes

When eBackup performs cross-AZ restore jobs, multiple jobs use file ChainDB.db at the same time. As a result, the file is damaged.

Procedure
  1. Use PuTTY to log in to the backup server.

    Login address: The management IP address can be obtained from the address of backup server GUI.

    Default account: hcp; default password: PXU9@ctuNov17!

  2. Run the su root command and enter the password of user root to switch to user root.

    The default password of the root account is Cloud12#$.

  3. Run the TMOUT=0 command to prevent the system from exiting due to timeout.

    NOTE:

    After you run the preceding command, the system keeps running even when no operation is performed, resulting in security risks. For security purposes, you are advised to run the exit command to exit the system after completing your operations.

  4. Run the cd /opt/huawei-data-protection/ebackup/sbin command to go to the directory where script uds_plug-in resides.
  5. Run the following commands in sequence to set environmental variables:

    export LD_LIBRARY_PATH=/opt/huawei-data-protection/ebackup/libs

    export ODBCINI=/opt/huawei-data-protection/ebackup/conf/odbc.ini

    export ODBCSYSINI=/opt/huawei-data-protection/ebackup/conf

  6. Run the ./uds_plug-in DownloadChainDB <destination_file_absolute_path> <source_volume_id> [backup_storage_type] command to download file ChainDB.db.

    Table 16-3 Parameters

    Parameter

    Description

    destination_file_absolute_path

    Indicates the local path for saving file ChainDB.db after being downloaded. This parameter is mandatory.

    source_volume_id

    Indicates the ID of the volume that fails to be backed up, restored, or deleted. This parameter is mandatory.

    backup_storage_type

    Indicates the backup storage type. This parameter is optional, and the default value is remote.

    • remote, which indicates remote storage.
    • local, which indicates local storage.

    Example:

    • When S3 backup storage is used, run either of the following commands:
      • ./uds_plug-in DownloadChainDB /home/hcp b2aabdd1-be92-427f-9beb-64df4db010fe
      • ./uds_plug-in DownloadChainDB /home/hcp b2aabdd1-be92-427f-9beb-64df4db010fe remote
    • When NFS backup storage is used, run the following command:

      ./uds_plug-in DownloadChainDB /home/hcp 59a9f2cd-9ac9-4639-bf5b-143ca6df0460 local

    During the command execution, input related information as prompted.

    • When the following information is displayed, input the Access Key ID (AK) of the S3 bucket:
      Please enter the Access Key:
    • When the following information is displayed, input the Secret Access Key (SK) of the S3 bucket:
      Please enter the Secret Access Key:

    If the following information is displayed, file ChainDB.db is downloaded successfully:

    Download file success.

    The following table shows the parameters used in the preceding command.

  7. Run the sqlite3 ChainDB.db ".dump" | sqlite3 tmp.db command to repair file ChainDB.db.
  8. Run the pragma integrity_check; command to check the integrity of file ChainDB.db.

    If information shown in the following figure is displayed, the file is repaired.

    After the file is repaired, change tmp.db to ChainDB.db.

  9. Run the ./uds_plug-in UploadChainDB <source_absolute_path> <source_volume_id> [backup_storage_type(remote:remote backup, local:local backup. default: remote)] command to upload the repaired ChainDB.db file.
  10. Perform the failed backup, restore, or deletion jobs again. Check whether the jobs are performed successfully:

    • If the jobs are performed successfully, no further action is required.
    • If the jobs fail to be performed, contact technical support engineers.

After an OpenStack Configuration Fails Due to Incorrect Configuration Information, Re-configuring the OpenStack Still Fails Even Though the Configuration Information Is the Same as the Last Successful Configuration

Symptom

After a successful OpenStack configuration, the second configuration fails due to incorrect configuration information. However, a third configuration still fails even though the configuration information is corrected back.

After the third configuration fails, the page is refreshed. The refreshed page remains to display information about the first configuration no matter whether the current configuration information is correct.

Possible Causes

If the third configuration uses the same information as the first configuration, the page regards the third configuration as an executed one and does not deliver parameter settings for it. As a result, the third configuration fails.

Procedure
  1. If the backend database is accessible, perform the following steps to handle this problem:

    1. Refer to Logging In to the eBackup Server to log in to the eBackup-Manager.
    2. Run the su root command and enter the password of user root to switch to user root.

      The default password of the root account is Cloud12#$.

    3. Run the TMOUT=0 command to prevent system timeout.
      NOTE:

      After the preceding command is executed, the system remains running even when no operation is performed, which poses security risks. For security purposes, run the exit command to exit the system after you finish performing operations.

    4. Run the cd /opt/huawei-data-protection/ebackup/db/bin command to go to the /opt/huawei-data-protection/ebackup/db/bin directory.
    5. Run the export LD_LIBRARY_PATH=/opt/huawei-data-protection/ebackup/db/lib/ command to import environmental variables.
    6. Run the ./gsql -d WFVMWAREDB -U gaussdb -p 6432 -h floating IP address of the internal communication plane command to enter the VMware database.

      For example,

      ./gsql -d WFVMWAREDB -U gaussdb -p 6432 -h 10.133.192.145.

    7. Run the delete from openstackconfig; command to delete the content of the openstackconfig table in the VMware database.

      See the following figure.

    8. Log in to the backup manager GUI using a browser.

      Login address: https://IP address corresponding to the Workflow-Management-Float-IP field:8088

      Default account: admin. Default password: Cloud12#$ for installation using HUAWEI CLOUD Stack Deploy, and PXU9@ctuNov17! for manual installation.

    9. On the navigation bar, choose > Configuration > OpenStack Settings and reconfigure OpenStack information.

  2. If there are multiple authentication servers, perform the following steps to handle this problem:

    1. Log in to the backup manager GUI using a browser.

      Login address: https://IP address corresponding to the Workflow-Management-Float-IP field:8088

      Default account: admin. Default password: Cloud12#$ for installation using HUAWEI CLOUD Stack Deploy, and PXU9@ctuNov17! for manual installation.

    2. On the navigation bar, choose > Configuration > OpenStack Settings.
    3. Configure the authentication server that is not used in the first OpenStack configuration.
    4. Re-log in to the GUI of backup manager and select > Configuration > OpenStack Settings to configure OpenStack information.

  3. If the status is still abnormal, contact technical support engineers for help.

Failed to Clear Alarms Indicating Microservices Are Stopped After Backup Proxies Are Removed

Symptom

After backup proxies are removed and deregistered on the eBackup GUI, alarms indicating that the backup and copy microservices are stopped are reported. The alarms are reported continuously after being manually cleared.

Possible Causes

The backup server uses the heartbeat detection mechanism to check the status of microservices. If the heartbeat detection times out, alarms indicating that microservices are stopped are reported. When backup proxies are removed, the backup server fails to detect the status of microservices on backup proxies. Therefore, alarms are being reported continuously.

Procedure
  1. Use PuTTY to log in to the backup server.

    Login address: The management IP address can be obtained from the address of backup server GUI.

    Default account: hcp; default password: PXU9@ctuNov17!

  2. Run the su root command and enter the password of user root to switch to user root.

    The default password of the root account is Cloud12#$.

  3. Run the TMOUT=0 command to prevent PuTTY from exiting due to timeout.

    NOTE:

    After the preceding command is executed, the system keeps running even when no operations are performed, posing security risks. To ensure system security, run the exit command to exit the system after performing your operations.

  4. Run the sed -i "/server internal heartbeat IP address of a removed backup proxy:.*down/d" /opt/huawei-data-protection/ebackup/microservice/ebk_lb_*/bin/nginx/conf/nginx.conf command to clear the configuration information of the deregistered node.

    Command example:

    sed -i "/server 192.168.0.1:.*down/d" /opt/huawei-data-protection/ebackup/microservice/ebk_lb_*/bin/nginx/conf/nginx.conf

  5. Run the following commands to restart the governance microservice:

    cd /opt/huawei-data-protection/ebackup/microservice/ebk_governance_*/script

    source ebackup_env.sh

    sh ebackup_stop.sh

  6. Re-log in to the GUI of backup server.
  7. Select Monitor > Alarm, select alarms indicating microservices are stopped, and then click Clear. When the confirmation dialog box is displayed, click OK.
Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 1138

Downloads: 12

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next