Updated on 2026-09-24 GMT+08:00

ALM-12004 OLdap Resource Abnormal

Alarm 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 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".

Alarm Attributes

Alarm ID

Alarm Severity

Auto Cleared

12004

Major

Yes

Alarm Parameters

Parameter

Description

Source

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

ServiceName

Specifies the service for which the alarm was generated.

RoleName

Specifies the role for which the alarm was generated.

HostName

Specifies the host for which the alarm was generated.

Impact on the System

An active/standby Manager switchover may occur. This will render the authentication service unavailable for both Manager and component web UIs, thus unable to provide security authentication and user management for upper-layer web services. Consequently, you may fail to log in to the Manager and component web UIs.

Possible Causes

The LdapServer process in Manager is abnormal.

Handling Procedure

Check whether the LdapServer process in Manager is normal.

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

    You can log in to MRS Manager using the floating IP address and run the sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh command to check the current Manager HA information.

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

    You can determine that the resource is normal as follows:

    1. Run sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh and check whether ResHAStatus of OLdap is Normal.
    2. Run ps -ef | grep slapd to check whether there is the slapd process that uses port 21750.

  3. Run the kill -2 ldap pid command. After 20 seconds, the HA automatically starts the OLdap process. Check whether the status of the OLdap resource is normal.

    • If yes, no further action is required.
    • If no, go to Step 4.

Collect fault information.

  1. On MRS Manager, choose O&M > Log > Download.

    For details about how to log in to FusionInsight Manager, see Accessing MRS Manager.

  2. Expand the Service drop-down list, select OmsLdapServer and OmmServer, and click OK.
  3. Click in the upper right corner, set Start Date and End Date for log collection to 1 hour before and after the alarm generation time, respectively, and click Download.
  4. Send the collected fault logs to O&M personnel for help.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None