Help Center > > User Guide> MRS Manager Operation Guide> Alarm Reference (Applicable to MRS 2.x or Earlier)> ALM-27001 DBService Is Unavailable

ALM-27001 DBService Is Unavailable

Updated at: Mar 25, 2021 GMT+08:00

Description

The alarm module checks the DBService status every 30 seconds. This alarm is generated when the system detects that DBService is unavailable.

This alarm is cleared when DBService recovers.

Attribute

Alarm ID

Alarm Severity

Auto Clear

27001

Critical

Yes

Parameters

Parameter

Description

ServiceName

Specifies the service for which the alarm is generated.

RoleName

Specifies the role for which the alarm is generated.

HostName

Specifies the host for which the alarm is generated.

Impact on the System

The database service is unavailable and cannot provide data import and query functions for upper-layer services, which results in service exceptions.

Possible Causes

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

Procedure

  1. Check whether the floating IP address exists in the cluster environment.

    1. Go to the MRS cluster details page and click Components.

      For MRS 1.8.10 or earlier, log in to MRS Manager and click Services.

    2. Choose DBService > Instances.
    3. Check whether the active instance exists.
      • If yes, go to 1.d.
      • If no, go to 2.a.
    4. Select the active DBServer instance and record the IP address.
    5. Log in to the host with the preceding IP address and run the ifconfig command to check whether the DBService floating IP address exists on the node.
      • If yes, go to 1.f.
      • If no, go to 2.a.
    6. Run the ping floating IP address command to check whether the DBService floating IP address can be pinged.
      • If yes, go to 1.g.
      • If no, go to 2.a.
    7. Log in to the host where the DBService floating IP address is located and run the ifconfig interface down command to delete the floating IP address.
    8. Choose Components > DBService > More > Restart Service to restart DBService and check whether DBService is started successfully.
      • If yes, go to 1.i.
      • If no, go to 2.a.
    9. 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 Step 13.

  2. Check the status of the active DBServer instance.

    1. Select the DBServer instance whose role status is abnormal and record the IP address.
    2. On the Alarms page, check whether ALM-12007 Process Fault occurs in the DBServer instance on the host that corresponds to the IP address.
      • If yes, go to 2.c.
      • If no, go to 4.
    3. Rectify the fault by following steps provided in ALM-12007 Process Fault.
    4. Wait about 5 minutes and check whether the alarm is cleared in the alarm list.
      • If yes, no further action is required.
      • If no, go to 4.

  3. Check the status of the active and standby DBServers.

    1. Log in to the host where the DBService floating IP address is located, run the sudo su - root and su - omm commands to switch to user omm, and run the cd ${BIGDATA_HOME}/FusionInsight/dbservice/ command to go to the DBService installation directory.
    2. Run the sh sbin/status-dbserver.sh command to view the status of the active and standby HA processes of DBService. Determine whether the status can be viewed successfully.
      • If yes, go to 3.c.
      • If no, go to 4.
    3. Check whether the active and standby HA processes are abnormal.
      • If yes, go to 3.d.
      • If no, go to 4.
    4. Choose Components > DBService > More > Restart Service to restart DBService and check whether DBService is started successfully.
      • If yes, go to 3.e.
      • If no, go to 4.
    5. 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 4.

  4. Collect fault information.

    1. On MRS Manager, choose System > Export Log.
    2. Contact the O&M personnel and send the collected logs.

Reference

None

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel