ALM-45275 Ranger Service Unavailable

Alarm Description

The alarm module checks the Ranger service status every 180 seconds. This alarm is generated if the Ranger service is abnormal.

This alarm is cleared after the Ranger service recovers.

Alarm Attributes

Alarm Parameters

Impact on the System

The native UI of Ranger cannot be accessed, and policies cannot be created, modified, or deleted.

Possible Causes

• The DBService service on which Ranger depends is abnormal.
• The KrbServer service on which Ranger depends is abnormal.
• The LdapServer service on which Ranger depends is abnormal.
• The RangerAdmin role instance is abnormal.

Handling Procedure

Check the DBService process status.

1. On FusionInsight Manager, choose O&M > Alarm > Alarms. On the displayed page, check whether the ALM-27001 DBService Service Unavailable alarm is reported.
   • If yes, go to 2.
   • If no, go to 3.

2. Rectify the DBService service fault by following the handling procedure of ALM-27001 DBService Service Unavailable. After the DBService alarm is cleared, check whether the Ranger Service Unavailable alarm is cleared.
   • If yes, no further action is required.
   • If no, go to 3.

Check the KrbServer status.

3. On FusionInsight Manager, choose O&M > Alarm > Alarms. On the page that is displayed, check whether ALM-25500 KrbServer Service Unavailable is reported.
   • If yes, go to 4.
   • If no, go to 5.

4. Rectify the KrbServer service fault by following the handling procedure of ALM-25500 KrbServer Service Unavailable. After the KrbServer alarm is cleared, check whether the Ranger Service Unavailable alarm is cleared.
   • If yes, no further action is required.
   • If no, go to 5.

Check the LdapServer status.

5. On FusionInsight Manager, choose O&M > Alarm > Alarms. On the page that is displayed, check whether ALM-12004 OLdap Resource Abnormal is reported.
   • If yes, go to 6.
   • If no, go to 7.

6. Rectify the LdapServer service fault by following the handling procedure of ALM-12004 OLdap Resource Abnormal. After the LdapServer alarm is cleared, check whether the Ranger Service Unavailable alarm is cleared.
   • If yes, no further action is required.
   • If no, go to 7.

Check all RangerAdmin instances.

7. Log in to the node where the RangerAdmin instance is located as user omm and run the ps -ef|grep "proc_rangeradmin" command to check whether the RangerAdmin process exists on the current node.
   • If yes, go to 8.
   • If no, restart the faulty RangerAdmin instance or Ranger service and go to 7.

8. In the alarm list, check whether the Ranger Service Unavailable alarm is cleared.
   • If yes, no further action is required.
   • If no, go to 9.

Collect the fault information.

9. On FusionInsight Manager, choose O&M > Log > Download.
10. Expand the Service drop-down list, and select Ranger for the target cluster.
11. 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.
12. Contact O&M engineers and provide the collected logs.

Alarm Clearance

After the fault that triggers the alarm is rectified, the alarm is automatically cleared.

Related Information

None.