ALM-25004 Abnormal LdapServer Data Synchronization

Description

The system checks the LdapServer data every 30 seconds. This alarm is generated when the data on the active and standby LdapServers of Manager is inconsistent for 12 consecutive times. This alarm is cleared when the data on the active and standby LdapServers is consistent.

The system checks the LdapServer data every 30 seconds. This alarm is generated when the LdapServer data in the cluster is inconsistent with that on Manager for 12 consecutive times. This alarm is cleared when the data is consistent.

Attribute

Parameters

Impact on the System

LdapServer data inconsistency occurs because the LdapServer data in Manager is damaged or the LdapServer data 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.
• The amount of Oldap data exceeds the threshold (10 MB by default).

Procedure

Check whether the network where the LdapServer nodes reside is faulty.

1. On MRS Manager, choose O&M > Alarm > Alarms. Record the IP address of HostName in the alarm locating information as IP1 (if multiple alarms exist, record the IP addresses as IP1, IP2, and IP3 respectively).

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

2. Log in to the IP1 node and run the ping command to check whether the IP address of the management plane of the active OMS node is reachable.
   • If yes, go to Step 4.
   • If no, go to Step 3.

3. Contact the O&M personnel engineers to recover the network and check whether the Abnormal LdapServer Data Synchronization alarm is cleared.
   • If yes, no further action is required.
   • If no, go to Step 4.

Check whether the LdapServer processes are normal.

4. On the Alarms page of Manager, check whether there is the OLdap Resource Abnormal alarm.
   • If yes, go to Step 5.
   • If no, go to Step 7.

5. Clear the alarm by following the steps provided in ALM-12004 OLdap Resource Abnormal.
6. Check whether Abnormal LdapServer Data Synchronization is cleared in the alarm list.
   • If yes, no further action is required.
   • If no, go to Step 7.

7. On the Alarms page of Manager, check whether the Process Fault alarm is generated for the LdapServer service.
   • If yes, go to Step 8.
   • If no, go to Step 10.

8. Handle the alarm according to ALM-12007 Process Fault.
9. Check whether Abnormal LdapServer Data Synchronization is cleared.
   • If yes, no further action is required.
   • If no, go to Step 10.

Check whether the LdapServer processes are normal.

10. Choose Cluster > Services > LdapServer > Configurations and record the port number of the LdapServer service. If the IP address in the alarm location information is the IP address of the standby management node, choose System > OMS > oldap > Modify Configuration and record the port number of the LdapServer service.
11. Log in to the IP1 node as user root and run the following command to switch to user omm:

    su - omm

12. Run the following command to check whether errors are displayed in the queried information.

    ldapsearch -H ldaps://IP1:PORT -LLL -x -D cn=root,dc=hadoop,dc=com -W -b ou=Peoples,dc=hadoop,dc=com

    After running the command, enter the LDAP administrator password. The password can be obtained from the MRS cluster administrator.

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

13. Recover the LdapServer and OMS nodes using data backed up before the alarm is generated.

    For details about how to restore Manager data, see Restoring Manager Data.

    

    Use the OMS data and LdapServer data backed up at the same point in time to recover the 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.

14. Check whether alarm Abnormal LdapServer Data Synchronization is cleared.
    • If yes, no further action is required.
    • If no, go to Step 15.

Check whether the data volume of the Oldap exceeds the threshold (10 MB by default). (This step applies only to versions earlier than MRS 3.3.0. For MRS 3.3.0 and later versions, go to Step 18.)

15. Log in to the active management node of the cluster as user omm.

    To view the active and standby management nodes in an MRS cluster, see Checking Active/Standby MRS Management Nodes.

16. Run the following command to check whether the directory contains .mdb files.

    ll /srv/BigData/ldapData/oldap/data/

    • If yes, check and record the size of the .mdb file and go to Step 17.
    • If no, go to Step 18.

17. Run the following command to view the Oldap configuration and record the value of Map size (the default value is 10485760 bytes, that is, 10 MB)

    mdb_stat -e /srv/BigData/ldapData/oldap/data/

    Check whether the size of the .mdb file with Step 16 records reaches the value of Map size.

    • If yes, contact O&M personnel engineers.
    • If no, go to Step 18.

Collect fault information.

18. On Manager, choose O&M > Log > Download.
19. Expand the Service drop-down list, and select LdapServer and OmsLdapServer for the target cluster.
20. 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.
21. Contact the O&M personnel and send the collected logs.

Alarm Clearing

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

Related Information

None