ALM-46001 MOTService Unavailable

Alarm Description

The system checks the MOTService status every 30 seconds. This alarm is generated when the MOTService service is unavailable.

This alarm is automatically cleared when the MOTService service recovers.

Alarm Attributes

Alarm Parameters

Impact on the System

The MOTService database service is unavailable and cannot provide functions such as data import and query for upper-layer services.

Possible Causes

• There is no active MOTServer instance.
• The floating IP address of MOTService does not exist.
• The active and standby MOTServer processes are abnormal.

Handling Procedure

Check whether the active MOTServer instance exists in the cluster.

1. On FusionInsight Manager, choose Cluster > Services > MOTService, and click the Instance tab.
2. Check whether the MOTServer(Active) instance exists.
   • If yes, go to 4.
   • If no, go to 3.

3. Return to the Dashboard tab, click More, and select Restart Service. Then enter the user password to restart the MOTService service. After the service is restarted, check whether the MOTServer(Active) instance exists.
   • If yes, check whether the alarm is cleared. If it is, no further action is required. If it is not, go to 4.
   • If no, go to 15.

Check whether the floating IP address of MOTService exists in the cluster.

4. On FusionInsight Manager, choose Cluster > Services > MOTService, and click the Instance tab.
5. Locate the MOTServer(Active) instance and record the service IP address.
6. Log in to the host obtained in 5 as user omm and run the ifconfig command to check whether the floating IP address of MOTService exists.
   • If yes, record the network port name (for example, eth0:MOT) and go to 7.
   • If no, go to 15.

7. Run the ping Floating IP address command to check whether the floating IP address of MOTService can be pinged.
   • If yes, go to 8.
   • If no, go to 15.

8. Log in to the host where the MOTService floating IP address is located as user root and run the following command:

   ifconfig Network port name down

   Example: ifconfig eth0:MOT down

9. On FusionInsight Manager, choose Cluster > Services > MOTService, click More, and select Restart Service. In the dialog box that is displayed, enter the password to restart the MOTService service.
10. After the service is restarted, check whether this alarm is cleared in the alarm list.
    • If yes, no further action is required.
    • If no, go to 11.

Check the status of the active and standby MOTServer database processes.

11. Log in to the host where the floating IP address of MOTService is located as user omm and run the following command to go to the installation directory of MOTService:

    cd ${MOTSERVER_HOME}

12. Run the following command to check whether the active and standby HA processes of MOTService are in the abnormal state:

    sh sbin/status-motserver.sh

    • If yes, go to 13.
    • If no, go to 15.

13. On FusionInsight Manager, choose Cluster > Services > MOTService, click More, and select Restart Service. In the dialog box that is displayed, enter the password to restart the MOTService service.

14. Wait about 2 minutes and check whether the alarm is cleared in the alarm list.
    • If yes, no further action is required.
    • If no, go to 15.

Collect fault information.

15. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
16. Expand the Service drop-down list, select MOTService for the target cluster, and click OK.
17. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs.
18. Click the edit icon 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.
19. Contact O&M personnel/Technical support and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None