Help Center/ MapReduce Service/ User Guide/ MRS Cluster O&M/ MRS Cluster Alarm Handling Reference/ ALM-12004 OLdap Resource Abnormal
Updated on 2024-11-13 GMT+08:00
View PDF
Share

ALM-12004 OLdap Resource Abnormal

Description

The system checks LDAP resources every 60 seconds. This alarm is generated when the system detects that the LDAP resources in Manager are abnormal for six consecutive times.

This alarm is cleared when the Ldap resource in the Manager recovers and the alarm handling is complete.

In MRS 3.3.1 and later versions, the alarm name is changed from "OLdap Resource Abnormal" to "Manager OLdap Resource Abnormal".

Attribute

Alarm ID

Alarm Severity

Auto Clear

12004

Major

Yes

Parameters

Name

Meaning

Source

Specifies the cluster or system for which the alarm is generated.

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

Manager active/standby switchover may occur. The Manager and WebUI authentication service of components is unavailable. Security authentication and user management functions cannot be provided for upper-layer web services. As a result, you may fail to log in to the Manager and WebUI of components.

Possible Causes

The LdapServer process in the Manager is abnormal.

Procedure

Check whether the LdapServer process in the Manager is normal.

  1. Log in the Manager node in the cluster as user omm.

    Log in to FusionInsight Manager using the floating IP address, and run the sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh command to check the information about the current Manager two-node cluster.

  2. Run ps -ef | grep slapd command to check whether the LdapServer resource process in the ${BIGDATA_HOME}/om-server/om/ in the process configuration file is running properly.

    You can determine that the resource is normal by checking the following information:

    1. After the sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh command runs, ResHAStatus of the OLdap is Normal.
    2. After the ps -ef | grep slapd command runs, the slapd process of port 21750 can be viewed.
      • If yes, go to 3.
      • If no, go to 4.

  3. Run the kill -2 ldap pid command to restart the LdapServer process and wait for 20 seconds. The HA starts the OLdap process automatically. Check whether the current OLdap resource is in normal state.

    • If yes, the operation is complete.
    • If no, go to 4.

Collect fault information.

  1. On the FusionInsight Manager home page, choose O&M > Log > Download.
  2. Select OmsLdapServer and OmmServer from the Service and click OK.
  3. 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.
  4. Contact the O&M personnel and send the collected log information.

Alarm Clearing

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

Related Information

None