ALM-45276 Abnormal RangerAdmin Status

Alarm Description

The alarm module checks the RangerAdmin service status every 60 seconds. This alarm is generated if RangerAdmin is unavailable.

This alarm is automatically cleared after the RangerAdmin service recovers.

Alarm Attributes

Alarm Parameters

Impact on the System

If the status of a RangerAdmin is abnormal, access to the Ranger native UI is not affected. If there are two abnormal RangerAdmin instances, the Ranger native UI cannot be accessed and operations such as creating, modifying, and deleting policies are unavailable.

Possible Causes

The RangerAdmin port is not started.

Handling Procedure

Check the port process.

1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated.
2. Log in to the node where the RangerAdmin instance is located as user omm. Run the ps -ef|grep "proc_rangeradmin" | grep -v grep | awk -F ' ' '{print $2}' command to obtain pid of the RangerAdmin process, and run the netstat -anp|grep pid | grep LISTEN command to check whether the RangerAdmin process listens to port 21401 in the security mode and port 21400 in standard mode.
   • If yes, go to 4.
   • If no, restart the faulty RangerAdmin instance or Ranger service and go to 3.

3. In the alarm list, check whether the "Abnormal RangerAdmin Status" alarm is cleared.
   • If yes, no further action is required.
   • If no, go to 4.

Collect the fault information.

4. On FusionInsight Manager, choose O&M > Log > Download.
5. Expand the Service drop-down list, and select Ranger for the target cluster.
6. 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.
7. 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.