Description

This alarm is generated when the XLog archive command fails to be executed for the Coordinator instance or DataNode instance in a cluster.

This alarm is automatically cleared when the XLog archive command is executed successfully.

Attribute

Parameters

Impact on the System

Some Xlog logs may not be archived to the archive directory specified in the archive command. The number of Xlog logs keeps increasing, resulting in insufficient disk space.

Possible Causes

• The archive command is incorrect.
• Users do not have the write permission of the archive directory specified in the archive command.
• The archive directory specified in the archive command does not exist.
• The space of the archive directory specified in the archive command is full. Therefore, data cannot be written into the directory.

Procedure

Modify the archive configuration.

1. Log in to the FusionInsight Manager.
   1. Log in to the ManageOne OM plane using a browser, then choose Alarms.
      • Login address: https://URL for the homepage of the ManageOne OM plane:31943. Example: https://oc.type.com:31943.
      • Default username: admin, default password: Huawei12#$.
   2. In the alarm list, locate and click the target alarm name in the Name column. The Alarm Details and Handling Recommendations dialog box is displayed.
   3. Locate the value in the IP Address/URL/Domain Name column, which is the float IP address of the FusionInsight Manager.
   4. Log in to the FusionInsight Manager using a browser.
      • Login address: https://float IP address of the FusionInsight Manager:28443/web. Example: https://10.10.192.100:28443/web.
      • Default username: admin, default password: obtain it from the system administrator.

2. On FusionInsight Manager, click Alarms. On the alarm list, locate the alarm and obtain the information about the node and instance for which the alarm is generated from Location in the Alarm Details area.
3. Use PuTTY to log in to the node for which the alarm is generated as user root or omm.
   NOTE:

   • omm user: Default user: omm, default password: Bigdata123@.
   • root user: The password is specified by users before the installation. Obtain it from the system administrator.

4. In the postgresql.conf file (for example, /srv/BigData/mppdb/data1/master1/postgresql.conf) of the Coordinator instance or active DataNode instance, check whether the syntax of archive_command is incorrect.
   For details about the syntax of archive_command, see archive_command in Appendix B GUC Parameter Description > Write Ahead Logs > Archiving in the Administrator Guide.

   • If yes, go to 5.
   • If no, go to 6.

5. Correct the command. Wait for 5 minutes, and check whether the alarm reoccurs.

   For the command details, see the comment in postgresql.conf.

   • If yes, go to 6.
   • If no, no further action is required.

6. Check whether the archive directory specified in the archive command does not exist, whether you do not have the write permission, or whether the space is full.
   • If it does not exist, you have no write permission, or the space is full, go to 7.
   • If it exists, you have write permission, or the space is not full, go to 8.

7. Resolve the problem based on the check result and ensure that the archive directory can be written properly. Wait for 5 minutes, and check whether the alarm reoccurs.
   • If yes, go to 8.
   • If no, no further action is required.

Collect fault information.

8. On FusionInsight Manager, choose System > Log Download.
9. Select MPPDB from the Services drop-down list box and click OK.
10. Set Start Time for log collection to 1 hour ahead of the alarm generation time and End Time to 1 hour after the alarm generation time, and click Download.
11. Contact Technical Support and send the collected logs.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

Related Information

None