Run the df -i | grep -iE "partition name|Filesystem" command to check the current disk Inode usage.# df -i | grep -iE "xvda2|Filesystem"
+- On MRS Manager, choose O&M > Alarm > Alarms and click
in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host and the disk partition for which the alarm is generated. - Log in to the host for which the alarm is generated as user root.
- Run the df -i | grep -iE "partition name|Filesystem" command to check the current disk Inode usage.
# df -i | grep -iE "xvda2|Filesystem"
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/xvda2 2359296 207420 2151876 9% /
- If the Inode usage exceeds the threshold, manually check small files stored in the disk partition and confirm whether these small files can be deleted.
Run the for i in /*; do echo $i; find $i|wc -l; done command to query the number of files in a partition. Replace /* with the specified partition.
@@ -89,7 +89,7 @@ Filesystem Inodes IUsed IFree IUse% Mounted on
- Wait for 5 minutes, and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 6.
Collect fault information.
-
- On the FusionInsight Manager home page of the active cluster, choose O&M > Log > Download.
- Select OMS from the Service and click OK.
- Set Host to the node for which the alarm is generated and the active OMS node.
- Click
in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download. - Contact the O&M personnel and send the collected log information.
+
- On the MRS Manager home page of the active cluster, choose O&M > Log > Download.
- Select OMS from the Service and click OK.
- Set Host to the node for which the alarm is generated and the active OMS node.
- Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
After the fault is rectified, the system automatically clears this alarm.
diff --git a/docs/mrs/umn/ALM-12052.html b/docs/mrs/umn/ALM-12052.html
index 8d6c105f..ade9f482 100644
--- a/docs/mrs/umn/ALM-12052.html
+++ b/docs/mrs/umn/ALM-12052.html
@@ -66,7 +66,7 @@
Possible Causes
- The temporary port cannot meet the current service requirements.
- The system is abnormal.
Procedure
Expand the temporary port number range.
-
- On FusionInsight Manager, click
in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host for which the alarm is generated. - Log in to the host for which the alarm is generated as user omm.
- Run the cat /proc/sys/net/ipv4/ip_local_port_range |cut -f 1 command to obtain the value of the start port and run the cat /proc/sys/net/ipv4/ip_local_port_range |cut -f 2 command to obtain the value of the end port. The total number of temporary ports is the value of the end port minus the value of the start port. If the total number of temporary ports is smaller than 28,232, the random port range of the OS is narrow. Contact the system administrator to increase the port range.
- Run the ss -ant 2>/dev/null | grep -v LISTEN | awk 'NR > 2 {print $4}'|cut -d ':' -f 2 | awk '$1 >"Value of the start port" {print $1}' | sort -u | wc -l command to calculate the number of used temporary ports.
- The formula for calculating the usage of the temporary ports is: Usage of the temporary ports = (Number of used temporary ports/Total number of temporary ports) x 100%. Check whether the temporary port usage exceeds the threshold.
- If yes, go to 7.
- If no, go to 6.
+- On MRS Manager, click in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host for which the alarm is generated.
- Log in to the host for which the alarm is generated as user omm.
- Run the cat /proc/sys/net/ipv4/ip_local_port_range |cut -f 1 command to obtain the value of the start port and run the cat /proc/sys/net/ipv4/ip_local_port_range |cut -f 2 command to obtain the value of the end port. The total number of temporary ports is the value of the end port minus the value of the start port. If the total number of temporary ports is smaller than 28,232, the random port range of the OS is narrow. Contact the system administrator to increase the port range.
- Run the ss -ant 2>/dev/null | grep -v LISTEN | awk 'NR > 2 {print $4}'|cut -d ':' -f 2 | awk '$1 >"Value of the start port" {print $1}' | sort -u | wc -l command to calculate the number of used temporary ports.
- The formula for calculating the usage of the temporary ports is: Usage of the temporary ports = (Number of used temporary ports/Total number of temporary ports) x 100%. Check whether the temporary port usage exceeds the threshold.
- If yes, go to 7.
- If no, go to 6.
- Wait for 5 minutes, and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 7.
Check whether the system environment is abnormal.
@@ -86,7 +86,7 @@ tcp 0 0 10-120-85-154:45435 10-120-85-154:9866 CLOSE_WAIT 94237/java
- After obtaining the administrator's approval, clear the processes that occupy a large number of ports. Wait for 5 minutes, and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 10.
Collect fault information.
-
- On the FusionInsight Manager home page of the active cluster, choose O&M > Log > Download.
- Select OMS from the Service and click OK.
- Set Host to the node for which the alarm is generated and the active OMS node.
- Click
in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download. - Contact the O&M personnel and send the collected log information and files port_result.txt and ps_result.txt. Then, delete the two residual temporary files from the environment.
+
- On the MRS Manager home page of the active cluster, choose O&M > Log > Download.
- Select OMS from the Service and click OK.
- Set Host to the node for which the alarm is generated and the active OMS node.
- Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact the O&M personnel and send the collected log information and files port_result.txt and ps_result.txt. Then, delete the two residual temporary files from the environment.
Alarm Clearing
After the fault is rectified, the system automatically clears this alarm.
diff --git a/docs/mrs/umn/ALM-12053.html b/docs/mrs/umn/ALM-12053.html
index f363ac07..3d8821d5 100644
--- a/docs/mrs/umn/ALM-12053.html
+++ b/docs/mrs/umn/ALM-12053.html
@@ -66,11 +66,11 @@
Possible Causes
- The application process is abnormal. For example, the opened file or socket is not closed.
- The number of file handles cannot meet the current service requirements.
- The system is abnormal.
Procedure
Check information about files opened in processes.
-
- On FusionInsight Manager, click
in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host for which the alarm is generated. - Log in to the host for which the alarm is generated as user root.
- Run the lsof -n|awk '{print $2}'|sort|uniq -c|sort -nr|more command to check the process that occupies excessive file handles.
- Check whether the processes in which a large number of files are opened are normal. For example, check whether there are files or sockets not closed.
- If yes, go to 5.
- If no, go to 7.
+- On MRS Manager, click in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host for which the alarm is generated.
- Log in to the host for which the alarm is generated as user root.
- Run the lsof -n|awk '{print $2}'|sort|uniq -c|sort -nr|more command to check the process that occupies excessive file handles.
- Check whether the processes in which a large number of files are opened are normal. For example, check whether there are files or sockets not closed.
- If yes, go to 5.
- If no, go to 7.
- Release the abnormal processes that occupy too many file handles.
- Five minutes later, check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 7.
Increase the number of file handles.
-- On FusionInsight Manager, click
in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host for which the alarm is generated. - Log in to the host for which the alarm is generated as user root.
- Contact the system administrator to increase the number of system file handles.
- Run the cat /proc/sys/fs/file-nr command to view the used handles and the maximum number of file handles. The first value is the number of used handles, the third value is the maximum number. Please check whether the usage exceeds the threshold.
- If yes, go to 9.
- If no, go to 11.
# cat /proc/sys/fs/file-nr
+- On MRS Manager, click in the row where the alarm is located in the real-time alarm list and obtain the IP address of the host for which the alarm is generated.
- Log in to the host for which the alarm is generated as user root.
- Contact the system administrator to increase the number of system file handles.
- Run the cat /proc/sys/fs/file-nr command to view the used handles and the maximum number of file handles. The first value is the number of used handles, the third value is the maximum number. Please check whether the usage exceeds the threshold.
- Wait for 5 minutes, and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 12.
@@ -80,7 +80,7 @@
- Wait for 5 minutes, and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 14.
Collect fault information.
-- On the FusionInsight Manager home page of the active cluster, choose O&M > Log > Download.
- Select OMS from the Service and click OK.
- Set Host to the node for which the alarm is generated and the active OMS node.
- Click
in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download. - Contact the O&M personnel and send the collected log information.
+- On the MRS Manager home page of the active cluster, choose O&M > Log > Download.
- Select OMS from the Service and click OK.
- Set Host to the node for which the alarm is generated and the active OMS node.
- Click in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
After the fault is rectified, the system automatically clears this alarm.
diff --git a/docs/mrs/umn/ALM-12054.html b/docs/mrs/umn/ALM-12054.html
index 9abfe9e3..537cbac8 100644
--- a/docs/mrs/umn/ALM-12054.html
+++ b/docs/mrs/umn/ALM-12054.html
@@ -68,7 +68,7 @@
Possible Causes
No certificate (CA certificate, HA root certificate, HA user certificate, Gaussdb root certificate, or Gaussdb user certificate) is imported to the system, the certificate fails to be imported, or the certificate file is invalid.
Procedure
Check the alarm cause.
-
- On FusionInsight Manager, locate the target alarm in the real-time alarm list and click
.View Additional Information to obtain the additional information about the alarm.
+- On MRS Manager, locate the target alarm in the real-time alarm list and click .
View Additional Information to obtain the additional information about the alarm.
- If CA Certificate is displayed in the additional alarm information, log in to the active OMS management node as user omm and go to 2.
- If HA root Certificate is displayed in the additional information, view Location to obtain the name of the host involved in this alarm. Then, log in to the host as user omm and go to 3.
- If HA server Certificate is displayed in the additional information, view Location to obtain the name of the host involved in this alarm. Then, log in to the host as user omm and go to 4.
- If Certificate has expired is displayed in the additional information, view Location to obtain the name of the host for which the alarm is generated. Then, log in to the host as user omm and perform 2 to 4 in sequence to check whether the certificates have expired. If these certificates have not expired, check whether other certificates have been imported. If yes, import the certificate files again.
Check the validity period of the certificate files in the system.
@@ -97,7 +97,7 @@
- If yes, go to 7.
- If no, no further action is required.
Collect the fault information.
-
- On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- In the Services area, select Controller, OmmServer, OmmCore, and Tomcat, and click OK.
- Click
in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download. - Contact O&M personnel and provide the collected logs.
+
- On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- In the Services area, select Controller, OmmServer, OmmCore, and Tomcat, and click OK.
- Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact O&M personnel and provide the collected logs.
Alarm Clearing
This alarm is automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12055.html b/docs/mrs/umn/ALM-12055.html
index d41f04d6..0c5e637e 100644
--- a/docs/mrs/umn/ALM-12055.html
+++ b/docs/mrs/umn/ALM-12055.html
@@ -68,7 +68,7 @@
Possible Causes
The remaining validity period of a system certificate (CA certificate, HA root certificate, HA user certificate, Gaussdb root certificate, or Gaussdb user certificate) is less than 30 days.
Procedure
Check the alarm cause.
-
- On FusionInsight Manager, locate the target alarm in the real-time alarm list and click .
View Additional Information to obtain the additional information about the alarm.
+- On MRS Manager, locate the target alarm in the real-time alarm list and click .
View Additional Information to obtain the additional information about the alarm.
- If CA Certificate is displayed in the additional alarm information, log in to the active OMS management node as user omm and go to 2.
- If HA root Certificate is displayed in the additional information, view Location to obtain the name of the host involved in this alarm. Then, log in to the host as user omm and go to 3.
- If HA server Certificate is displayed in the additional information, view Location to obtain the name of the host involved in this alarm. Then, log in to the host as user omm and go to 4.
Check the validity period of the certificate files in the system.
@@ -97,7 +97,7 @@
- If yes, go to 7.
- If no, no further action is required.
Collect the fault information.
-
- On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- In the Services area, select Controller, OmmServer, OmmCore, and Tomcat, and click OK.
- Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact O&M personnel and provide the collected logs.
+
- On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- In the Services area, select Controller, OmmServer, OmmCore, and Tomcat, and click OK.
- Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact O&M personnel and provide the collected logs.
Alarm Clearing
This alarm is automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12057.html b/docs/mrs/umn/ALM-12057.html
index 2af662f5..af01f559 100644
--- a/docs/mrs/umn/ALM-12057.html
+++ b/docs/mrs/umn/ALM-12057.html
@@ -59,10 +59,10 @@
Possible Causes
Metadata is not configured with the task to periodically back up data to a third-party server.
Procedure
- On the FusionInsight Manager portal choose O&M > Alarm > Alarms.
- In the alarm list, click
in the row where the alarm is located and identify the data module from which the alarm is generated based on Additional Information. - Choose O&M > Backup and Restoration > Backup Management > Create.
- Configure a backup task. The backup data to be configured is consistent with the data in Additional Information of the alarm.
- After the backup task is created successfully, wait for two minutes and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 6.
+Procedure
- On the MRS Manager portal choose O&M > Alarm > Alarms.
- In the alarm list, click in the row where the alarm is located and identify the data module from which the alarm is generated based on Additional Information.
- Choose O&M > Backup and Restoration > Backup Management > Create.
- Configure a backup task. The backup data to be configured is consistent with the data in Additional Information of the alarm.
- After the backup task is created successfully, wait for two minutes and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 6.
Collect fault information
-
- On FusionInsight Manager, choose O&M > Log > Download.
- In the Service area, select Controller and click OK.
- Click
in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download. - Contact the O&M personnel and send the collected log information.
+
- On MRS Manager, choose O&M > Log > Download.
- In the Service area, select Controller and click OK.
- Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
After the fault is rectified, the system automatically clears this alarm.
Possible Causes
- The alarm threshold is improperly configured.
- The maximum number of processes (including threads) that can be concurrently opened by user omm is inappropriate.
- An excessive number of threads are opened at the same time.
Procedure
Check whether the alarm threshold or alarm hit number is properly configured.
-
- On the FusionInsight Manager, change the alarm threshold and Trigger Count based on the actual CPU usage.
Specifically, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host> Process > omm Process Usage to change Trigger Count.
+- On the MRS Manager, change the alarm threshold and Trigger Count based on the actual CPU usage.
Specifically, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host> Process > omm Process Usage to change Trigger Count.
The alarm is generated when the process usage exceeds the threshold for the times specified by Trigger Count.
Set the alarm threshold based on the actual process usage. To check the process usage, choose O&M > Alarm > Thresholds > Name of the desired cluster > Host> Process > omm Process Usage, as shown in Figure 1.
@@ -73,14 +73,14 @@
- 2 minutes later, check whether the alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 3.
Check whether the maximum number of processes (including threads) opened by user omm is appropriate.
-- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
- Log in to the host where the alarm is generated as user root.
- Run the su - omm command to switch to user omm.
- Run the ulimit -u command to obtain the maximum number of threads that can be concurrently opened by user omm and check whether the number is greater than or equal to 60000.
- If it is, go to 8.
- If it is not, go to 7.
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
- Log in to the host where the alarm is generated as user root.
- Run the su - omm command to switch to user omm.
- Run the ulimit -u command to obtain the maximum number of threads that can be concurrently opened by user omm and check whether the number is greater than or equal to 60000.
- If it is, go to 8.
- If it is not, go to 7.
- Run the ulimit -u 60000 command to change the maximum number to 60000. Two minutes later, check whether the alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 12.
Check whether an excessive number of processes are opened at the same time.
-- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
- Log in to the host where the alarm is generated as user root.
- Run the ps -o nlwp, pid, lwp, args, -u omm|sort -n command to check the numbers of threads used by the system. The result is sorted based on the thread number. Analyze the top 5 thread numbers and check whether the threads are incorrectly used. If they are, contact maintenance personnel to rectify the fault. If they are not, run the ulimit -u command to change the maximum number to be greater than 60000.
- Five minutes later, check whether the alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 12.
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
- Log in to the host where the alarm is generated as user root.
- Run the ps -o nlwp, pid, lwp, args, -u omm|sort -n command to check the numbers of threads used by the system. The result is sorted based on the thread number. Analyze the top 5 thread numbers and check whether the threads are incorrectly used. If they are, contact maintenance personnel to rectify the fault. If they are not, run the ulimit -u command to change the maximum number to be greater than 60000.
- Five minutes later, check whether the alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 12.
Collect fault information.
-- On the FusionInsight Manager home page of the active clusters, choose O&M > Log > Download.
- Select OmmServer and NodeAgent from the Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+- On the MRS Manager home page of the active clusters, choose O&M > Log > Download.
- Select OmmServer and NodeAgent from the Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
Possible Causes
The OMS parameter configurations mismatch with the cluster scale.
Procedure
Check whether the OMS parameter configurations match with the cluster scale.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
- Log in to the host where the alarm is generated as user root.
- Run the su - omm command to switch to user omm.
- Run the vi $BIGDATA_LOG_HOME/controller/scriptlog/modify_manager_param.log command to open the log file and search for the log file containing the following information: Current oms configurations cannot support xx nodes. In the information, xx indicates the number of nodes in the cluster.
- Optimize the current cluster configuration by following the instructions in Optimizing Manager Configurations Based on the Number of Cluster Nodes.
- One hour later, check whether the alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 7.
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
- Log in to the host where the alarm is generated as user root.
- Run the su - omm command to switch to user omm.
- Run the vi $BIGDATA_LOG_HOME/controller/scriptlog/modify_manager_param.log command to open the log file and search for the log file containing the following information: Current oms configurations cannot support xx nodes. In the information, xx indicates the number of nodes in the cluster.
- Optimize the current cluster configuration by following the instructions in Optimizing Manager Configurations Based on the Number of Cluster Nodes.
- One hour later, check whether the alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 7.
Collect fault information.
-- On FusionInsight Manager, choose O&M > Log > Download.
- Select Controller from the Service and click OK.
- Click
in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download. - Contact the O&M personnel and send the collected log information.
+- On MRS Manager, choose O&M > Log > Download.
- Select Controller from the Service and click OK.
- Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
After the fault is rectified, the system automatically clears this alarm.
Possible Causes
- The permission of the disk mount directory is abnormal.
- There are disk bad sectors.
Procedure
Check whether the permission of the disk mount directory is normal.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the IP address of the host and DiskName for the disk for which the alarm is generated.
- Log in to the host where the alarm is generated as user root.
- Run the df -h |grep DiskName command to obtain the mount point and check whether the permission of the mount directory is unwritable or unreadable.
- If it is, go to 4.
- If it is not, go to 8.
If the permission of the mount directory is 000 or the owner is root, the mount directory is unreadable and unwritable.
+
- In the alarm list on MRS Manager, locate the row that contains the alarm, and view the IP address of the host and DiskName for the disk for which the alarm is generated.
- Log in to the host where the alarm is generated as user root.
- Run the df -h |grep DiskName command to obtain the mount point and check whether the permission of the mount directory is unwritable or unreadable.
- If it is, go to 4.
- If it is not, go to 8.
If the permission of the mount directory is 000 or the owner is root, the mount directory is unreadable and unwritable.
- Modify the directory permission.
- One hour later, check whether this alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 6.
- Contact hardware engineers to rectify the disk.
- One hour later, check whether this alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 8.
Collect fault information.
-
- On FusionInsight Manager, choose O&M > Log > Download.
- Select NodeAgent from the Service and click OK.
- Click
in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download. - Contact the O&M personnel and send the collected log information.
+
- On MRS Manager, choose O&M > Log > Download.
- Select NodeAgent from the Service and click OK.
- Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
After the fault is rectified, the system automatically clears this alarm.
diff --git a/docs/mrs/umn/ALM-12064.html b/docs/mrs/umn/ALM-12064.html
index ab97f4d0..4296e46a 100644
--- a/docs/mrs/umn/ALM-12064.html
+++ b/docs/mrs/umn/ALM-12064.html
@@ -59,11 +59,11 @@
Possible Causes
The random port range configuration is modified.
Procedure
Check the random port range of the system.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
- Log in to the host where the alarm is generated as user root.
- Run the cat /proc/sys/net/ipv4/ip_local_port_range command to obtain the random port range of the host and check whether the minimum value is smaller than 32768.
- If it is, go to 4.
- If it is not, goto 7.
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and view the IP address of the host for which the alarm is generated.
- Log in to the host where the alarm is generated as user root.
- Run the cat /proc/sys/net/ipv4/ip_local_port_range command to obtain the random port range of the host and check whether the minimum value is smaller than 32768.
- If it is, go to 4.
- If it is not, goto 7.
- Run the vim /etc/sysctl.conf command to change the value of net.ipv4.ip_local_port_range to 32768 61000. If this parameter does not exist, add the following configuration: net.ipv4.ip_local_port_range = 32768 61000.
- Run the sysctl -p /etc/sysctl.conf command for the modification to take effect.
- One hour later, check whether the alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 7.
Collect fault information.
-- On FusionInsight Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click
in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download. - Contact the O&M personnel and send the collected log information.
+- On MRS Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
After the fault is rectified, the system automatically clears this alarm.
diff --git a/docs/mrs/umn/ALM-12066.html b/docs/mrs/umn/ALM-12066.html
index 5c660d68..08a59211 100644
--- a/docs/mrs/umn/ALM-12066.html
+++ b/docs/mrs/umn/ALM-12066.html
@@ -59,7 +59,7 @@
Possible Causes
- The /etc/ssh/sshd_config configuration file is damaged.
- The password of user omm has expired.
Procedure
Check the status of the /etc/ssh/sshd_config configuration file.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm and click
to view the host list in the alarm details. - Log in to the active OMS node as user omm.
- Run the ssh command, for example, ssh host2, on each node in the alarm details to check whether the connection fails. (host2 is a node other than the OMS node in the alarm details.)
- If yes, go to 4.
- If no, go to 6.
+- In the alarm list on MRS Manager, locate the row that contains the alarm and click to view the host list in the alarm details.
- Log in to the active OMS node as user omm.
- Run the ssh command, for example, ssh host2, on each node in the alarm details to check whether the connection fails. (host2 is a node other than the OMS node in the alarm details.)
- If yes, go to 4.
- If no, go to 6.
- Open the /etc/ssh/sshd_config configuration file on host2 and check whether AllowUsers or DenyUsers is configured for other nodes.
- If yes, go to 5.
- If no, contact OS experts.
- Modify the whitelist or blacklist to ensure that user omm is in the whitelist or not in the blacklist. Check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 6.
@@ -69,7 +69,7 @@
- Add the public key of user omm of the peer host to the trust list of the local host. Run the ssh command, for example, ssh host2, on each node in the alarm details to check whether the connection fails. (host2 is a node other than the OMS node in the alarm details.)
- If yes, go to 9.
- If no, check whether the alarm is cleared. If the alarm is cleared, no further action is required; otherwise, go to 9.
Collect the fault information.
-
- On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- Select Controller for Service and click OK.
- Click
in the upper right corner to set the log collection time range. Generally, the time range is 10 minutes before and after the alarm generation time. Click Download. - Contact O&M personnel and provide the collected logs.
+
- On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- Select Controller for Service and click OK.
- Click in the upper right corner to set the log collection time range. Generally, the time range is 10 minutes before and after the alarm generation time. Click Download.
- Contact O&M personnel and provide the collected logs.
Alarm Clearing
This alarm is automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12067.html b/docs/mrs/umn/ALM-12067.html
index 41e1b008..bc2ddb06 100644
--- a/docs/mrs/umn/ALM-12067.html
+++ b/docs/mrs/umn/ALM-12067.html
@@ -61,10 +61,10 @@
Possible Causes
- The Tomcat directory permission is abnormal, and the Tomcat process is abnormal.
Procedure
Check whether the permission on the Tomcat directory is normal.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click
to view the IP address of the host for which the alarm is generated. - Log in to the alarm host as user root.
- Run the su - omm command to switch to user omm.
- Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/tomcat.log command to check whether the Tomcat resource log contains keyword Cannot find XXX and rectify the file permission based on the keyword.
- After 5 minutes, check whether the alarm is automatically cleared.
- If yes, no further action is required.
- If no, go to 6.
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and click to view the IP address of the host for which the alarm is generated.
- Log in to the alarm host as user root.
- Run the su - omm command to switch to user omm.
- Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/tomcat.log command to check whether the Tomcat resource log contains keyword Cannot find XXX and rectify the file permission based on the keyword.
- After 5 minutes, check whether the alarm is automatically cleared.
- If yes, no further action is required.
- If no, go to 6.
Collect the fault information.
-- On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- In the Services area, select OmmServer and Tomcat, and click OK.
- Click
in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download. - Contact O&M personnel and provide the collected logs.
+- On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- In the Services area, select OmmServer and Tomcat, and click OK.
- Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact O&M personnel and provide the collected logs.
Alarm Clearing
This alarm is automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12068.html b/docs/mrs/umn/ALM-12068.html
index cef06028..58abc0dc 100644
--- a/docs/mrs/umn/ALM-12068.html
+++ b/docs/mrs/umn/ALM-12068.html
@@ -56,16 +56,16 @@
Impact on the System
- The active/standby Manager switchover occurs.
- The ACS process repeatedly restarts, which may cause the FusionInsight Manager login failure.
+
Impact on the System
- The active/standby Manager switchover occurs.
- The ACS process repeatedly restarts, which may cause the MRS Manager login failure.
Possible Causes
The ACS process is abnormal.
Procedure
Check whether the ACS process is normal.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click
to view the name of the host for which the alarm is generated. - Log in to the alarm host as user root.
- Run the su - omm command and then sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh to check whether the status of the ACS resources managed by the HA is normal. In the single-node system, the ACS resource is in the normal state. In the dual-node system, the ACS resource is in the normal state on the active node and in the stopped state on the standby node.
- If yes, go to 6.
- If no, go to 4.
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated.
- Log in to the alarm host as user root.
- Run the su - omm command and then sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh to check whether the status of the ACS resources managed by the HA is normal. In the single-node system, the ACS resource is in the normal state. In the dual-node system, the ACS resource is in the normal state on the active node and in the stopped state on the standby node.
- If yes, go to 6.
- If no, go to 4.
- Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/acs.log command to check whether the ACS resource log of HA contains the keyword ERROR. If yes, analyze the logs to locate the resource exception cause and fix the exception.
- After 5 minutes, check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 6.
Collect the fault information.
-- On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- In the Services area, select Controller and OmmServer, and click OK.
- Click
in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download. - Contact O&M personnel and provide the collected logs.
+- On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- In the Services area, select Controller and OmmServer, and click OK.
- Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact O&M personnel and provide the collected logs.
Alarm Clearing
This alarm is automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12069.html b/docs/mrs/umn/ALM-12069.html
index cea673d1..6c3bbc3c 100644
--- a/docs/mrs/umn/ALM-12069.html
+++ b/docs/mrs/umn/ALM-12069.html
@@ -56,16 +56,16 @@
Impact on the System
- The active/standby Manager switchover occurs.
- The AOS process repeatedly restarts, which may cause the FusionInsight Manager login failure.
+
Impact on the System
- The active/standby Manager switchover occurs.
- The AOS process repeatedly restarts, which may cause the MRS Manager login failure.
Possible Causes
The AOS process is abnormal.
Procedure
Check whether the AOS process is normal.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click
to view the name of the host for which the alarm is generated. - Log in to the alarm host as user root.
- Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the AOS resources managed by the HA is normal. In the single-node system, the AOS resource is in the normal state. In the dual-node system, the AOS resource is in the normal state on the active node and in the stopped state on the standby node.
- If yes, go to 6.
- If no, go to 4.
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated.
- Log in to the alarm host as user root.
- Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the AOS resources managed by the HA is normal. In the single-node system, the AOS resource is in the normal state. In the dual-node system, the AOS resource is in the normal state on the active node and in the stopped state on the standby node.
- If yes, go to 6.
- If no, go to 4.
- Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/aos.log command to check whether the AOS resource log of HA contains the keyword ERROR. If yes, analyze the logs to locate the resource exception cause and fix the exception.
- After 5 minutes, check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 6.
Collect the fault information.
-- On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- In the Services area, select Controller and OmmServer, and click OK.
- Click
in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download. - Contact O&M personnel and provide the collected logs.
+- On MRS Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- In the Services area, select Controller and OmmServer, and click OK.
- Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact O&M personnel and provide the collected logs.
Alarm Clearing
This alarm is automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12070.html b/docs/mrs/umn/ALM-12070.html
index c8a56a10..8e02cff7 100644
--- a/docs/mrs/umn/ALM-12070.html
+++ b/docs/mrs/umn/ALM-12070.html
@@ -3,7 +3,7 @@
ALM-12070 Controller Resource Is Abnormal
Alarm Description
HA checks the controller resources of Manager every 80 seconds. This alarm is generated when HA detects that the controller resources are abnormal for 2 consecutive times.
This alarm is cleared when the Controller resource is normal.
-
Resource Type of Controller is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new Controller resources have been enabled on the new active FusionInsight Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.
+
Resource Type of Controller is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new Controller resources have been enabled on the new active MRS Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.
Attribute
Alarm ID
@@ -56,16 +56,16 @@
|
|---|
-
Impact on the System
- The active/standby FusionInsight Manager switchover occurs.
- The Controller process repeatedly restarts, which may cause the FusionInsight Manager login failure.
+
Impact on the System
- The active/standby MRS Manager switchover occurs.
- The Controller process repeatedly restarts, which may cause the MRS Manager login failure.
Possible Causes
The Controller process is abnormal.
Procedure
Check whether the controller process is normal.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
- Log in to the host for which the alarm is generated as user root.
- Run the su - omm command to switch to user omm.Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the Controller resources managed by the HA is normal. In the single-node system, the Controller resource is in the normal state. In the dual-node system, the Controller resource is in the normal state on the active node and in the stopped state on the standby node.
- If it is, go to 6.
- If it is not, go to 4.
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
- Log in to the host for which the alarm is generated as user root.
- Run the su - omm command to switch to user omm.Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the Controller resources managed by the HA is normal. In the single-node system, the Controller resource is in the normal state. In the dual-node system, the Controller resource is in the normal state on the active node and in the stopped state on the standby node.
- If it is, go to 6.
- If it is not, go to 4.
- Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/controller.log command to view the Controller resource logs, and run the vi $BIGDATA_LOG_HOME/controller/controller.log command to view the Controller running logs, check whether the keyword ERROR exists. Analyze the logs to locate and rectify the fault.
- Five minutes later, check whether this alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 6.
Collect fault information.
-- On FusionInsight Manager, choose O&M > Log > Download.
- Select Controller and OmmServe for Service and click OK.
- Click
in the upper right corner, and set Start Date and End Date for log collection to 1 hour before and after the alarm generation time, respectively. Then, click Download. - Contact the O&M personnel and send the collected log information.
+- On MRS Manager, choose O&M > Log > Download.
- Select Controller and OmmServe for Service and click OK.
- Click in the upper right corner, and set Start Date and End Date for log collection to 1 hour before and after the alarm generation time, respectively. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
After the fault is rectified, the system automatically clears this alarm.
diff --git a/docs/mrs/umn/ALM-12071.html b/docs/mrs/umn/ALM-12071.html
index 3d96f959..a4f6e926 100644
--- a/docs/mrs/umn/ALM-12071.html
+++ b/docs/mrs/umn/ALM-12071.html
@@ -3,7 +3,7 @@
ALM-12071 Httpd Resource Is Abnormal
Description
HA checks the httpd resources of Manager every 120 seconds. This alarm is generated when HA detects that the httpd resources are abnormal for 10 consecutive times.
This alarm is cleared when the httpd resource is normal.
-
Resource Type of httpd is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new httpd resources have been enabled on the new active FusionInsight Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.
+
Resource Type of httpd is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new httpd resources have been enabled on the new active MRS Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.
Attribute
Alarm ID
@@ -56,16 +56,16 @@
|
|---|
-
Impact on the System
- The active/standby FusionInsight Manager switchover occurs.
- The httpd process is repeatedly restarts, which may lead to the failure to visit the native service UI.
+
Impact on the System
- The active/standby MRS Manager switchover occurs.
- The httpd process is repeatedly restarts, which may lead to the failure to visit the native service UI.
Possible Causes
The httpd process is abnormal.
Procedure
Check whether the httpd process is abnormal.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
- Log in to the host for which the alarm is generated as user root.
- Run the su - omm command to switch to user omm.
- Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the httpd resources managed by the HA is normal. In the single-node system, the httpd resource is in the normal state. In the dual-node system, the httpd resource is in the normal state on the active node and in the stopped state on the standby node.
- If it is, go to 7.
- If it is not, go to 5.
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
- Log in to the host for which the alarm is generated as user root.
- Run the su - omm command to switch to user omm.
- Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the httpd resources managed by the HA is normal. In the single-node system, the httpd resource is in the normal state. In the dual-node system, the httpd resource is in the normal state on the active node and in the stopped state on the standby node.
- If it is, go to 7.
- If it is not, go to 5.
- Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/httpd.log command to view the httpd resource logs, check whether the keyword ERROR exists. Analyze the logs to locate and rectify the fault.
- Five minutes later, check whether this alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 7.
Collect fault information.
-- On FusionInsight Manager, choose O&M > Log > Download.
- Select Controller and OmmServer for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+- On MRS Manager, choose O&M > Log > Download.
- Select Controller and OmmServer for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12072.html b/docs/mrs/umn/ALM-12072.html
index 64ccb756..68e16509 100644
--- a/docs/mrs/umn/ALM-12072.html
+++ b/docs/mrs/umn/ALM-12072.html
@@ -3,7 +3,7 @@
ALM-12072 FloatIP Resource Is Abnormal
Description
HA checks the floatip resources of Manager every 9 seconds. This alarm is generated when HA detects that the floatip resources are abnormal for 3 consecutive times.
This alarm is cleared when the FloatIP resource is normal.
-
Resource Type of FloatIP is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new FloatIP resources have been enabled on the new active FusionInsight Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.
+
Resource Type of FloatIP is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new FloatIP resources have been enabled on the new active MRS Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.
Attribute
Alarm ID
@@ -56,21 +56,21 @@
|
|---|
-
Impact on the System
- The active/standby FusionInsight Manager switchover occurs.
- The FloatIP process is repeatedly restarts, which may lead to the failure to visit the native service UI.
+
Impact on the System
- The active/standby MRS Manager switchover occurs.
- The FloatIP process is repeatedly restarts, which may lead to the failure to visit the native service UI.
Possible Causes
- The floating IP address is abnormal.
Procedure
Check the floating IP address status of the active management node.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the address of the host for which the alarm is generated and the resource name.
- Log in to the active management node as user root.
- Run the following command, go to the ${BIGDATA_HOME}/om-server/om/sbin/ directory.
su - omm
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and view the address of the host for which the alarm is generated and the resource name.
- Log in to the active management node as user root.
- Run the following command, go to the ${BIGDATA_HOME}/om-server/om/sbin/ directory.
su - omm
cd ${BIGDATA_HOME}/om-server/om/sbin/
- - Run the sh status-oms.sh command, and execute the status-oms.sh script to check whether the floating IP address of the active FusionInsight Manager is normal. View the command output, locate the row where ResName is floatip, and check whether the following information is displayed.
For example:
+ - Run the sh status-oms.sh command, and execute the status-oms.sh script to check whether the floating IP address of the active MRS Manager is normal. View the command output, locate the row where ResName is floatip, and check whether the following information is displayed.
For example:
10-10-10-160 floatip Normal Normal Single_active
- If it is, go to 8.
- If it is not, go to 5.
- Run the ifconfig command to check whether the NIC with the floating IP address exists.
- If it does, go to 8.
- If it does not, go to 6.
- Run the ifconfig NIC name Floating IPaddress netmask Subnet mask command to reconfigure the NIC with the floating IP address. (For example, ifconfig eth0 10.10.10.102 netmask 255.255.255.0).
- Five minutes later, check whether the alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 8.
Collect fault information.
-- On FusionInsight Manager, choose O&M > Log > Download.
- Select Controller and OmmServer for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+- On MRS Manager, choose O&M > Log > Download.
- Select Controller and OmmServer for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12073.html b/docs/mrs/umn/ALM-12073.html
index 406d74f4..d96a9359 100644
--- a/docs/mrs/umn/ALM-12073.html
+++ b/docs/mrs/umn/ALM-12073.html
@@ -3,7 +3,7 @@
ALM-12073 CEP Resource Is Abnormal
Description
HA checks the cep resources of Manager every 60 seconds. This alarm is generated when HA detects that the cep resources are abnormal for 2 consecutive times.
This alarm is cleared when the CEP resource is normal.
-
Resource Type of CEP is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new CEP resources have been enabled on the new active FusionInsight Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.
+
Resource Type of CEP is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new CEP resources have been enabled on the new active MRS Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.
Attribute
Alarm ID
@@ -56,16 +56,16 @@
|
|---|
-
Impact on the System
- The active/standby FusionInsight Manager switchover occurs.
- The CEP process repeatedly restarts, causing monitoring data to be abnormal.
+
Impact on the System
- The active/standby MRS Manager switchover occurs.
- The CEP process repeatedly restarts, causing monitoring data to be abnormal.
Possible Causes
The CEP process is abnormal.
Procedure
Check whether the CEP process is abnormal.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
- Log in to the host for which the alarm is generated as user root.
- Run the su -omm command and then the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the CEP resources managed by the HA is normal. In the single-node system, the CEP resource is in the normal state. In the dual-node system, the CEP resource is in the normal state on the active node and in the stopped state on the standby node.
- If it is, go to 6.
- If it is not, go to 4.
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
- Log in to the host for which the alarm is generated as user root.
- Run the su -omm command and then the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the CEP resources managed by the HA is normal. In the single-node system, the CEP resource is in the normal state. In the dual-node system, the CEP resource is in the normal state on the active node and in the stopped state on the standby node.
- If it is, go to 6.
- If it is not, go to 4.
- Run the vi $BIGDATA_LOG_HOME/omm/oms/cep/cep.log and vi $BIGDATA_LOG_HOME/omm/oms/cep/scriptlog/cep_ha.log commands to view the CEP resource logs, check whether the keyword ERROR exists. Analyze the logs to locate and rectify the fault.
- Five minutes later, check whether this alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 6.
Collect fault information.
-- On FusionInsight Manager, choose O&M > Log > Download.
- Select Controller and OmmServer for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+- On MRS Manager, choose O&M > Log > Download.
- Select Controller and OmmServer for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12074.html b/docs/mrs/umn/ALM-12074.html
index 661d29ed..1398b042 100644
--- a/docs/mrs/umn/ALM-12074.html
+++ b/docs/mrs/umn/ALM-12074.html
@@ -3,7 +3,7 @@
ALM-12074 FMS Resource Is Abnormal
Description
HA checks the fms resources of Manager every 60 seconds. This alarm is generated when HA detects that the fms resources are abnormal for 2 consecutive times.
This alarm is cleared when the FMS resource is normal.
-
Resource Type of FMS is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new FMS resources have been enabled on the new active FusionInsight Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.
+
Resource Type of FMS is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new FMS resources have been enabled on the new active MRS Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.
Attribute
Alarm ID
@@ -56,16 +56,16 @@
|
|---|
-
Impact on the System
- The active/standby FusionInsight Manager switchover occurs.
- The FMS process repeatedly restarts. As a result, alarm information may fail to be reported.
+
Impact on the System
- The active/standby MRS Manager switchover occurs.
- The FMS process repeatedly restarts. As a result, alarm information may fail to be reported.
Possible Causes
The FMS process is abnormal.
Procedure
Check whether the FMS process is abnormal.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
- Log in to the host for which the alarm is generated as user root.
- Run the su -omm command and then the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the FMS resources managed by the HA is normal. In the single-node system, the FMS resource is in the normal state. In the dual-node system, the FMS resource is in the normal state on the active node and in the stopped state on the standby node.
- If it is, go to 6.
- If it is not, go to 4.
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
- Log in to the host for which the alarm is generated as user root.
- Run the su -omm command and then the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the FMS resources managed by the HA is normal. In the single-node system, the FMS resource is in the normal state. In the dual-node system, the FMS resource is in the normal state on the active node and in the stopped state on the standby node.
- If it is, go to 6.
- If it is not, go to 4.
- Run the vi $BIGDATA_LOG_HOME/omm/oms/fms/fms.log and vi $BIGDATA_LOG_HOME/omm/oms/fms/scriptlog/fms_ha.log commands to view the FMS resource logs, check whether the keyword ERROR exists. Analyze the logs to locate and rectify the fault.
- 5 minutes later, check whether this alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 6.
Collect fault information.
-- On FusionInsight Manager, choose O&M> Log > Download.
- Select Controller and OmmServer for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+- On MRS Manager, choose O&M> Log > Download.
- Select Controller and OmmServer for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12075.html b/docs/mrs/umn/ALM-12075.html
index 3d916ff6..5a11c05e 100644
--- a/docs/mrs/umn/ALM-12075.html
+++ b/docs/mrs/umn/ALM-12075.html
@@ -3,7 +3,7 @@
ALM-12075 PMS Resource Is Abnormal
Description
HA checks the pms resources of Manager every 55 seconds. This alarm is generated when HA detects that the pms resources are abnormal for three consecutive times.
This alarm is cleared when the PMS resource is normal.
-
Resource Type of PMS is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new PMS resources have been enabled on the new active FusionInsight Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.
+
Resource Type of PMS is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new PMS resources have been enabled on the new active MRS Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby switchover.
Attribute
Alarm ID
@@ -56,16 +56,16 @@
|
|---|
-
Impact on the System
- The active/standby FusionInsight Manager switchover occurs.
- The PMS process repeatedly restarts, causing monitoring information to be abnormal.
+
Impact on the System
- The active/standby MRS Manager switchover occurs.
- The PMS process repeatedly restarts, causing monitoring information to be abnormal.
Possible Causes
The PMS process is abnormal.
Procedure
Check whether the PMS process is abnormal.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
- Log in to the host for which the alarm is generated as user root.
- Run the su -omm command and then the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the PMS resources managed by the HA is normal. In the single-node system, the PMS resource is in the normal state. In the dual-node system, the PMS resource is in the normal state on the active node and in the stopped state on the standby node.
- If it is, go to 6.
- If it is not, go to 4.
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and view the name of the host for which the alarm is generated.
- Log in to the host for which the alarm is generated as user root.
- Run the su -omm command and then the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/status_ha.sh command to check whether the status of the PMS resources managed by the HA is normal. In the single-node system, the PMS resource is in the normal state. In the dual-node system, the PMS resource is in the normal state on the active node and in the stopped state on the standby node.
- If it is, go to 6.
- If it is not, go to 4.
- Run the vi $BIGDATA_LOG_HOME/omm/oms/pms/pms.log and vi $BIGDATA_LOG_HOME/omm/oms/pms/scriptlog/pms_ha.log commands to view the PMS resource logs, check whether the keyword ERROR exists. Analyze the logs to locate and rectify the fault.
- Five minutes later, check whether this alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 6.
Collect fault information.
-- On FusionInsight Manager, choose O&M> Log > Download.
- Select Controller and OmmServer for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+- On MRS Manager, choose O&M> Log > Download.
- Select Controller and OmmServer for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 1 hour before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12076.html b/docs/mrs/umn/ALM-12076.html
index ad5bef2e..d1c47d93 100644
--- a/docs/mrs/umn/ALM-12076.html
+++ b/docs/mrs/umn/ALM-12076.html
@@ -83,11 +83,11 @@
- If it is, go to 3.
- If it is not, go to 2.
- Contact the network administrator to check whether the network is faulty.
- If it is, go to 3.
- If it is not, go to 5.
- Five minutes later, check whether the alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 4.
- - Log in to the active and standby management nodes, run the su -omm command to switch to user omm, go to the ${BIGDATA_HOME} /om-server/om/sbin/ directory, and run the status-oms.sh script to check whether the floating IP addresses and GaussDB resources of the active and standby FusionInsight Managers are in the status shown in the following figure.
+ - Log in to the active and standby management nodes, run the su -omm command to switch to user omm, go to the ${BIGDATA_HOME} /om-server/om/sbin/ directory, and run the status-oms.sh script to check whether the floating IP addresses and GaussDB resources of the active and standby MRS Managers are in the status shown in the following figure.
- If they are, find the alarm in the alarm list and manually clear the alarm.
- If they are not, go to 5.
Collect fault information.
-
- On FusionInsight Manager, choose O&M > Log > Download.
- Select OmmServer for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+
- On MRS Manager, choose O&M > Log > Download.
- Select OmmServer for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12077.html b/docs/mrs/umn/ALM-12077.html
index e5ecc3e7..cbb3f5e4 100644
--- a/docs/mrs/umn/ALM-12077.html
+++ b/docs/mrs/umn/ALM-12077.html
@@ -55,7 +55,7 @@
-
Impact on the System
User omm has expired. The node trust relationship is unavailable, and FusionInsight Manager cannot manage the services.
+
Impact on the System
User omm has expired. The node trust relationship is unavailable, and MRS Manager cannot manage the services.
Possible Causes
User omm has expired.
@@ -67,7 +67,7 @@
- Run the chage -E 'yyyy-MM-dd' omm command to set the expiration time of user omm. Eight hours later, check whether the alarm is automatically cleared.
- If it is, no further action is required.
- If it is not, go to 4.
Collect fault information.
-
- On FusionInsight Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+
- On MRS Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12078.html b/docs/mrs/umn/ALM-12078.html
index ce4a479f..2925713e 100644
--- a/docs/mrs/umn/ALM-12078.html
+++ b/docs/mrs/umn/ALM-12078.html
@@ -55,7 +55,7 @@
-
Impact on the System
The password of user omm has expired. The node trust relationship is unavailable, and FusionInsight Manager cannot manage the services.
+
Impact on the System
The password of user omm has expired. The node trust relationship is unavailable, and MRS Manager cannot manage the services.
Possible Causes
The password of user omm has expired.
@@ -67,7 +67,7 @@
- Run the chage -M 'days' omm command to set the validity period of the password for user omm. Eight hours later, check whether the alarm is automatically cleared.
- If it is, no further action is required.
- If it is not, go to 4.
Collect fault information.
-
- On FusionInsight Manager, choose O&M> Log > Download.
- Select NodeAgent for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+
- On MRS Manager, choose O&M> Log > Download.
- Select NodeAgent for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12079.html b/docs/mrs/umn/ALM-12079.html
index fcbc2fa4..94dd6b8b 100644
--- a/docs/mrs/umn/ALM-12079.html
+++ b/docs/mrs/umn/ALM-12079.html
@@ -55,7 +55,7 @@
-
Impact on the System
User omm has expired. The node trust relationship is unavailable, and FusionInsight Manager cannot manage the services.
+
Impact on the System
User omm has expired. The node trust relationship is unavailable, and MRS Manager cannot manage the services.
Possible Causes
The account of user omm is about to expire.
@@ -67,7 +67,7 @@
- Run the chage -E 'yyyy-MM-dd' omm command to set the validity period of user omm. Eight hours later, check whether the alarm is automatically cleared.
- If it is, no further action is required.
- If it is not, go to 4.
Collect fault information.
-
- On FusionInsight Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+
- On MRS Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12080.html b/docs/mrs/umn/ALM-12080.html
index 13cf3908..d9cf6ac4 100644
--- a/docs/mrs/umn/ALM-12080.html
+++ b/docs/mrs/umn/ALM-12080.html
@@ -55,7 +55,7 @@
-
Impact on the System
The password of user omm has expired. The node trust relationship is unavailable, and FusionInsight Manager cannot manage the services.
+
Impact on the System
The password of user omm has expired. The node trust relationship is unavailable, and MRS Manager cannot manage the services.
Possible Causes
The password of user omm is about to expire.
@@ -67,7 +67,7 @@
- Run the chage -M 'days' omm command to set the validity period of the password for user omm. Eight hours later, check whether the alarm is automatically cleared.
- If it is, no further action is required.
- If it is not, go to 4.
Collect fault information.
-
- On FusionInsight Manager, choose O&M> Log > Download.
- Select NodeAgent for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+
- On MRS Manager, choose O&M> Log > Download.
- Select NodeAgent for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12081.html b/docs/mrs/umn/ALM-12081.html
index a76170aa..f9631705 100644
--- a/docs/mrs/umn/ALM-12081.html
+++ b/docs/mrs/umn/ALM-12081.html
@@ -1,6 +1,6 @@
-
ALM-12081 User ommdba Expired
+
ALM-12081 User ommdba Expired
Description
The system starts at 00:00 every day to check whether user ommdba has expired every 8 hours. This alarm is generated if the user account has expired.
This alarm is cleared when the expiration time of user ommdba is reset and the user account status becomes normal.
@@ -67,7 +67,7 @@
- Run the chage -E 'yyyy-MM-dd' omm command to set the validity period of user ommdba. Eight hours later, check whether the alarm is automatically cleared.
- If it is, no further action is required.
- If it is not, go to 4.
Collect fault information.
-
- On FusionInsight Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+
- On MRS Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12082.html b/docs/mrs/umn/ALM-12082.html
index a02f0a50..edb89b53 100644
--- a/docs/mrs/umn/ALM-12082.html
+++ b/docs/mrs/umn/ALM-12082.html
@@ -67,7 +67,7 @@
- Run the chage -E 'yyyy-MM-dd' ommdba command to set the validity period of user ommdba. Eight hours later, check whether the alarm is automatically cleared.
- If it is, no further action is required.
- If it is not, go to 4.
Collect fault information.
-
- On FusionInsight Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+
- On MRS Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12083.html b/docs/mrs/umn/ALM-12083.html
index 593f5edf..82dd7a2f 100644
--- a/docs/mrs/umn/ALM-12083.html
+++ b/docs/mrs/umn/ALM-12083.html
@@ -67,7 +67,7 @@
- Run the chage -M 'days' ommdba command to set the validity period of the password for user ommdba. Eight hours later, check whether the alarm is automatically cleared.
- If it is, no further action is required.
- If it is not, go to 4.
Collect fault information.
-
- On FusionInsight Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+
- On MRS Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
diff --git a/docs/mrs/umn/ALM-12084.html b/docs/mrs/umn/ALM-12084.html
index a66079f1..17cfe0f1 100644
--- a/docs/mrs/umn/ALM-12084.html
+++ b/docs/mrs/umn/ALM-12084.html
@@ -55,7 +55,7 @@
Impact on the System
The password of user ommdba has expired. The node trust relationship is unavailable, and FusionInsight Manager cannot manage the services.
+
Impact on the System
The password of user ommdba has expired. The node trust relationship is unavailable, and MRS Manager cannot manage the services.
Possible Causes
The password of user ommdba for the host has expired.
@@ -67,7 +67,7 @@
- Run the chage -M 'days' ommdba command to set the validity period of the password for user ommdba. Eight hours later, check whether the alarm is automatically cleared.
- If it is, no further action is required.
- If it is not, go to 4.
Collect fault information.
-
- On FusionInsight Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+
- On MRS Manager, choose O&M > Log > Download.
- Select NodeAgent for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
Possible Causes
- The service audit logs are oversized.
- The OMS backup storage space is insufficient.
- The storage space of a host where the service is located is insufficient.
Procedure
Check whether the service audit logs are oversized.
-
- In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the IP address of the host and additional information for which the alarm is generated.
- Log in to the host where the alarm is generated as user root.
- Run the vi ${BIGDATA_LOG_HOME}/controller/scriptlog/getLogs.log command to check whether the keyword "LOG SIZE is more than 5000MB" can be searched.
- If it can, go to 4.
- If it cannot, go to 5.
+- In the alarm list on MRS Manager, locate the row that contains the alarm, and view the IP address of the host and additional information for which the alarm is generated.
- Log in to the host where the alarm is generated as user root.
- Run the vi ${BIGDATA_LOG_HOME}/controller/scriptlog/getLogs.log command to check whether the keyword "LOG SIZE is more than 5000MB" can be searched.
- If it can, go to 4.
- If it cannot, go to 5.
- Check whether the oversized service audit logs are caused by exceptions.
The OMS backup storage space is insufficient.
- Run the vi ${BIGDATA_LOG_HOME}/controller/scriptlog/getLogs.log command to check whether the keyword "Collect log failed, too many logs on" can be searched.
- If it can, obtain the host IP address following the keyword "Collect log failed, too many logs on", and go to 6.
- If it cannot, go to 11.
@@ -75,7 +75,7 @@
- Expand the capacity of the node
- In the next execution period, 03:00, check whether the alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 15.
Collect fault information.
-- On FusionInsight Manager, choose O&M> Log > Download.
- Select Controller for Service and click OK.
- Click
in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download. - Contact the O&M personnel and send the collected log information.
+- On MRS Manager, choose O&M> Log > Download.
- Select Controller for Service and click OK.
- Click in the upper right corner. In the displayed dialog box, set Start Date and End Date to 10 minutes before and after the alarm generation time respectively and click OK. Then, click Download.
- Contact the O&M personnel and send the collected log information.
Alarm Clearing
This alarm will be automatically cleared after the fault is rectified.
- In the early morning of the next day, check whether this alarm is cleared.
- If it is, no further action is required.
- If it is not, go to 6.
Collect fault information.
-- On the FusionInsight Manager portal, choose O&M > Log > Download.
- Select Controller from the Service and click OK.
- Click
in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download. - Contact the O&M personnel and send the collected log information.
+- On the MRS Manager portal, choose O&M > Log > Download.
- Select Controller from the Service and click OK.
- Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
- Contact the O&M personnel and send the collected log information.
in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.
in the row containing the alarm, click the host name, and view the IP address of the host for which the alarm is generated.
in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
in the row where the alarm is located , and click the host name to view the host address for which the alarm is generated
in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
in the row containing the alarm and view the IP address of the standby Manager (Peer Manager) server in the alarm details.
in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
in the row where the alarm is located and obtain the standby Manager server IP address (Peer Manager IP address) in the alarm details.
in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
