ALM-25000 LdapServer Service Unavailable

Alarm Description

The system checks the LdapServer service status every 30 seconds. This alarm is generated when the system detects that both the active and standby LdapServer services are abnormal.

This alarm is cleared when the system detects that one or two LdapServer services are normal.

Alarm Attributes

Alarm Parameters

Impact on the System

The running status of the component that depends on the LdapServer becomes faulty. As a result, Kerberos authentication fails in the cluster or OS user cache synchronization is abnormal, and component services are abnormal.

Possible Causes

• The node where the LdapServer service locates is faulty.
• The LdapServer process is abnormal.

Handling Procedure

Check whether the nodes where the two SlapdServer instances of the LdapServer service are located are faulty.

1. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > LdapServer > Instance to go to the LdapServer instance page to obtain the host name of the node where the two SlapdServer instances locates.
2. Choose O&M > Alarm > Alarms. On the Alarm page of the FusionInsight Manager system, check whether any alarm of NodeAgent Process Is Abnormal exists.
   • If yes, go to 3.
   • If no, go to 6.

3. Check whether the host name in the alarm is consistent with the 1 host name.
   • If yes, go to 4.
   • If no, go to 6.

4. Handle the alarm according to "ALM-12006 NodeAgent Process Is Abnormal".
5. Check whether LdapServer Service Unavailable is cleared in the alarm list.
   • If yes, no further action is required.
   • If no, go to 10.

Check whether the LdapServer process is normal.

6. Choose O&M > Alarm > Alarms. On the Alarm page of the FusionInsight Manager system, check whether any alarm of Process Fault exists.
   • If yes, go to 7.
   • If no, go to 10.

7. Check whether the service and host name in the alarm are consistent with the LdapServer service and host name.
   • If yes, go to 8.
   • If no, go to 10.

8. Handle the alarm according to "ALM-12007 Process Fault".
9. Check whether LdapServer Service Unavailable is cleared in the alarm list.
   • If yes, no further action is required.
   • If no, go to 10.

Collect fault information.

10. On the FusionInsight Manager, choose O&M > Log > Download.
11. Select LdapServer in the required cluster from the Service.
12. Click the edit button in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
13. Contact the O&M engineers and send the collected logs.

Alarm Clearance

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

Related Information

None.