ALM-25004 Abnormal LdapServer Data Synchronization

Description

This alarm is generated when LdapServer data on Manager is inconsistent. This alarm is cleared when the data becomes consistent.

This alarm is generated when LdapServer data in the cluster is inconsistent with LdapServer data on Manager. This alarm is cleared when the data becomes consistent.

Attribute

Parameters

Impact on the System

LdapServer data inconsistency occurs because LdapServer data on Manager or in the cluster is damaged. The LdapServer process with damaged data cannot provide services externally, and the authentication functions of Manager and the cluster are affected.

Possible Causes

• The network of the node where the LdapServer process locates is faulty.
• The LdapServer process is abnormal.
• The OS restart damages data on LdapServer.

Procedure

1. Check whether the network where the LdapServer nodes reside is faulty.
   1. Go to the cluster details page and choose Alarms.
   2. Record the IP address of HostName in Location of the alarm as IP1 (if multiple alarms exist, record the IP addresses as IP1, IP2, and IP3 respectively).
   3. Contact O&M personnel and use PuTTY to log in to the node corresponding to IP1. Run the ping command on the node to check whether the IP address of the management plane of the active OMS node can be pinged.
      • If yes, go to 1.d.
      • If no, go to 2.a.
   4. Contact O&M personnel to recover the network and check whether the alarm ALM-25004 Abnormal LdapServer Data Synchronization is cleared.
      • If yes, no further action is required.
      • If no, go to 2.a.

2. Check whether the LdapServer process is in normal state.
   1. Go to the cluster details page and choose Alarms.
   2. Check whether ALM-12004 OLdap Resource Is Abnormal is generated for LdapServer.
      • If yes, go to 2.c.
      • If no, go to 2.e.
   3. Rectify the fault by following steps provided in ALM-12004 OLdap Resource Is Abnormal.
   4. Check whether the alarm ALM-25004 Abnormal LdapServer Data Synchronization is cleared.
      • If yes, no further action is required.
      • If no, go to 2.e.
   5. On the Alarms page of MRS Manager, check whether the alarm ALM-12007 Process Fault of LdapServer is generated.
      • If yes, go to 2.f.
      • If no, go to 3.a.
   6. Rectify the fault by following steps provided in ALM-12007 Process Fault.
   7. Check whether the alarm ALM-25004 Abnormal LdapServer Data Synchronization is cleared.
      • If yes, no further action is required.
      • If no, go to 3.a.

3. Check whether the OS restart damages data on LdapServer.
   1. Go to the cluster details page and choose Alarms.
   2. Record the IP address of HostName in Location of the alarm as IP1 (if multiple alarms exist, record the IP addresses as IP1, IP2, and IP3 respectively). Choose Services > LdapServer > Service Configuration and record the LdapServer port number as PORT. (If the IP address in the alarm location information is the IP address of the standby OMS node, the default port number is 21750.)
   3. Log in to node IP1 as user omm and run the ldapsearch -H ldaps://IP1:PORT -x -LLL -b dc=hadoop,dc=com command (if the IP address is the IP address of the standby OMS node, run the ldapsearch -H ldaps://IP1:PORT -x -LLL -b dc=hadoop,dc=com command before running this command). Check whether error information is displayed in the command output.
      • If yes, go to 3.d.
      • If no, go to 4.
   4. Recover the LdapServer and OMS nodes using backup data before the alarm is generated. For details, see section "Recovering Manager Data" in the Administrator Guide.
      

      Use the OMS data and LdapServer data backed up at the same time to restore data. Otherwise, the service and operation may fail. To recover data when services run properly, you are advised to manually back up the latest management data and then recover the data. Otherwise, Manager data produced between the backup point in time and the recovery point in time will be lost.

   5. Check whether the alarm ALM-25004 Abnormal LdapServer Data Synchronization is cleared.
      • 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 technical support engineers for help. For details, see technical support.

Reference

None