how to deal with Database Space Is Going to Be Insufficient alarm on FusionCompute V1R5C00 version

2

This alarm is generated when the system detects that the database space usage of management nodes hits 80%.

This alarm is cleared when the database space usage is less than 80%.
Confirm the IP address of the faulty node.

On the FusionCompute portal, click Monitoring, and choose Alarm in the navigation tree on the left. On the Alarm page, locate the row that contains the alarm and click the name in the Alarm Object column.
The Service and Management Node page is displayed.

On the Service and Management Node page, view information about the management nodes and obtain the management IP address of the node whose name is the same as that of Alarm Object in Step 1.
Rectify the fault.

Use PuTTY to log in to the faulty node.
Ensure that the management IP address and username gandalf are used to establish the connection.

Run the following command and enter the password of user root to switch to user root:

su - root


Run the following command to query the space usage of each database.
df -l

Information similar to the following is displayed:

VRM8810:~ # df -l
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 10317828 2033244 7760468 21% /
devtmpfs 8147620 212 8147408 1% /dev
tmpfs 8147620 0 8147620 0% /dev/shm
/dev/sda6 1027768 17912 957648 2% /etc/galax
/dev/sda10 880874308 204948 835923520 1% /extend
/dev/sda8 1106800 34188 1016388 4% /opt/galax/upgrade
/dev/mapper/vg_vrm-lv_gaussdb
18578172 627648 17006808 4% /opt/gaussdb
/dev/sda5 18572112 316568 17312132 2% /var
/dev/mapper/vg_vrm-lv_backup
30834692 176196 29092188 1% /var/backup

NOTE:
Filesystem: specifies the name of a disk partition.
1K-blocks: specifies the disk capacity.
Used: specifies the used disk capacity.
Available: specifies the available disk capacity.
Use%: specifies the disk usage.
Mounted on: specifies the directory to which the disk is attached.

Enter the directory that contains the alarm object, and delete the files that are unnecessary or that you have copied.

NOTICE:
File deletion is a high-risk operation. Therefore, make sure that the files to be deleted are not those that are stored in the system directory or in the directory that contains important in-use services.


After 10 or 15 minutes, check whether the alarm is cleared

Other related questions:
How to deal with MAC Address Resource Is Going to Be Insufficient alarm on FusionCompute V1R5C00 version
The Virtualization Resource Management (VRM) node collects statistics information about the ranges of Media Access Control (MAC) address segments that are configured in the system and the number of assigned MAC addresses in the segments every hour. This alarm is generated when the number of assigned MAC addresses in the segments reaches 80%. This alarm is cleared when the number of assigned MAC addresses in the segments is less than 80%. Add MAC address resource. On the FusionCompute portal, choose Network Pool > MAC Address Pool. On the MAC Address Pool page, add a new MAC address segment or modify the segment range. After 60 minutes, check whether the alarm is cleared.

how to deal with HA Resource in a Cluster Is Going to Be Insufficient alarm on FusionCompute V1R5C00 version
This alarm is generated when the high availability (HA) resource in a cluster is going to be insufficient. This alarm is cleared when the HA resource in the cluster is sufficient. On the Real-Time Alarms page, locate the row that contains the alarm and click the cluster name in the Alarm Object column. The cluster page is displayed. Check the hosts in the cluster and restore the faulty ones. Check the non-HA VMs running in the cluster and stop the unnecessary ones. Add hosts to the cluster. Check whether the alarm is cleared.

how to deal with Available Resources on Management Nodes Are Going to Be Insufficient alarm on FusionCompute V1R5C00 version
The system periodically detects the usage of available resources on management nodes. This alarm is generated when the ratio of used resources to available resources hits 95%. This alarm is cleared when the ratio is less than 95%. Confirm the IP address of the faulty node. On the FusionCompute portal, click Monitoring, and choose Alarm in the navigation tree on the left. On the Alarm page, locate the row that contains the alarm and click the name in the Alarm Object column. The Service and Management Node page is displayed. On the Service and Management Node page, view information about the management nodes and obtain the management IP address of the node whose name is the same as that of Alarm Object in Step 1. Rectify the fault. Use PuTTY to log in to the faulty node. Ensure that the management IP address and username gandalf are used to establish the connection. Run the following command and enter the password of user root to switch to user root: su - root Run the following command to query the inode usage of each disk: df -i Information similar to the following is displayed: vrm4050:~ # df -i Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sda1 655360 51954 603406 8% / devtmpfs 0 0 0 - /dev tmpfs 2036905 1 2036904 1% /dev/shm /dev/sda5 1245184 11 1245173 1% /drbd0 /dev/sda6 65280 11 65269 1% /drbd1 /dev/sda7 70416 11 70405 1% /drbd2 /dev/sda8 70416 11 70405 1% /drbd3 /dev/sda9 262144 11 262133 1% /swap /dev/sda10 58671104 3104 58668000 1% /var NOTE: Filesystem: specifies the name of a disk partition. Inodes: specifies the total number of inodes in a disk. IUsed: specifies the number of inodes used. IFree: specifies the number of free inodes. IUse%: specifies the usage of inodes. Mounted on: specifies the directory to which the disk is attached. Enter the directory that contains the alarm object, and delete the files that are unnecessary or that you have copied. NOTICE: File deletion is a high-risk operation. Therefore, ensure that the files to be deleted are not system files or important files involving service running. After 10 or 15 minutes, check whether the alarm is cleared.

how to deal with Standby Node Database Is Abnormal alarm on FusionCompute V1R5C00 version
This alarm is generated when the system detects that the database on the standby Virtualization Resource Management (VRM) node does not work properly. This alarm is cleared when the standby VRM node database works properly. On the FusionCompute portal, click System, and choose System Configuration > Service and Mgmt. Node in the navigation tree on the left. On the displayed Service and Mgmt. Node page, obtain the standby VRM node name in the table of the Service list area, and view the IP address of the standby VRM node in the table of the Management node area. Use PuTTY to log in to the standby VRM node. Ensure that the management IP address and username gandalf are used to establish the connection. Run the following command and enter the password of user root to switch to user root: su - root Run the following command to stop the High Availability (HA) process on the standby node: service had stop Run the following command to stop the database process: su - postgres -c "gs_ctl stop" Run the following command to start the database process: su - postgres -c "gs_ctl start -M standby" Check whether the database is started: If yes, go to Step 8. If no, go to Step 12. Run the following command to rebuild the database: su - postgres -c "gs_ctl build -b incremental -M standby" Check whether the database is rebuilt: If yes, go to Step 10. If no, go to Step 12. Run the following command to start the HA process: service had start After about 5 minutes, log in to the FusionCompute portal and check whether the alarm is cleared.

how to deal with PMCD Process Is Abnormal alarm on FusionCompute V1R5C00 version
This alarm is generated when the system detects that the monitoring processing process pmcd has stopped or is faulty. This alarm is cleared when the pmcd process becomes normal. Identify the management IP address of the node for which the alarm is generated. On the FusionCompute portal, click Monitoring, and choose Alarm in the navigation tree on the left. On the Alarm page, locate the row that contains the alarm and click the name in the Alarm Object column. The Service and Management Node page is displayed. On the Service and Management Node page, view information about the management nodes and obtain the IP address of the node whose name is the same as that of Alarm Object in Step 1. Restart the process of the performance management center. Use PuTTY to log in to the node. Ensure that the management IP address and username gandalf are used to establish the connection. Run the following command and enter the password of user root to switch to user root: su - root Run the following command to restart the process: service pmcd restart NOTE: Restarting the process may cause temporary interruption of monitoring processing service. Run the following command to check the process status: service pmcd status Check whether the command output is as follows: Checking for pmcd: running If yes, go to Step 8. If no, go to Step 9. After 3 or 4 minutes, switch to the Alarm page and check whether the alarm is cleared.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top