Help Center/ MapReduce Service/ User Guide/ MRS Cluster O&M/ MRS Cluster Alarm Handling Reference/ ALM-45293 Ranger User Synchronization Exception
Updated on 2024-11-13 GMT+08:00
View PDF
Share

ALM-45293 Ranger User Synchronization Exception

This section is available for MRS 3.3.1 or later version only.

Alarm Description

The system checks synchronization status of the UserSync process every 5 minutes. This alarm is generated when a synchronization exception occurs. This alarm is cleared when user synchronization becomes normal.

Alarm Attributes

Alarm ID

Alarm Severity

Auto Cleared

45293

Major

Yes

Alarm Parameters

Type

Parameter

Description

Location Information

Source

Specifies the cluster for which the alarm was 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.

Additional Information

Trigger Condition

Specifies the trigger condition, that is, an exception occurs during Ranger user synchronization.

Impact on the System

Unsynchronized users cannot access the native Ranger page and set permission policies for other users. As a result, some users may fail to access services that require Ranger permissions.

Possible Causes

The RangerAdmin instance is abnormal.

The UserSync instance is abnormal.

The LDAP service is abnormal.

Handling Procedure

Check whether the UserSync is abnormal.

  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms > ALM-45293 Ranger User Synchronization Exception. Check the location information of the alarm and view the host name of the instance for which the alarm is generated.
  2. On FusionInsight Manager, choose Cluster > Services > Ranger > Instance, select the UserSync instance on the host for which the alarm is generated, and check whether the instance status is abnormal.

    • If yes, go to 3.
    • If no, go to 5.

  3. On FusionInsight Manager, choose Cluster > Services > Ranger, click Instances, and click UserSync. On the displayed page, click More > Restart Instance, or restart the Ranger service.
  4. Check whether the alarm is cleared in 5 to 10 minutes.

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

Check whether the RangerAdmin is abnormal.

  1. On FusionInsight Manager, choose O&M > Alarm > Alarms to check whether alarm "ALM-45276 Abnormal RangerAdmin Status" is reported.

    • If yes, go to 6.
    • If no, go to 8.

  1. Rectify the fault by following the handling procedure of "ALM-45276 Abnormal RangerAdmin Status".
  2. Check whether the alarm is cleared in 5 to 10 minutes.

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

Check whether the LDAP service is abnormal.

  1. On FusionInsight Manager, choose O&M > Alarm > Alarms to check whether alarm "ALM-25000 LdapServer Service Unavailable" is reported.

    • If yes, go to 9.
    • If no, go to 11.

  1. Clear the alarm according to the handling procedure of "ALM-25000 LdapServer Service Unavailable".
  2. Check whether the alarm is cleared in 5 to 10 minutes.

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

Collect fault information.

  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
  2. Expand the Service drop-down list, and select Ranger for the target cluster.
  3. Click the edit icon 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.
  4. Contact O&M engineers and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.