ALM-45736 Guardian Service Unavailable

Alarm Description

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

This alarm is cleared after Guardian recovers.

Alarm Attributes

Alarm Parameters

Impact on the System

Guardian cannot work properly, and OBS cannot be accessed.

Possible Causes

• The HDFS service on which the Guardian service depends is abnormal.
• The TokenServer role instance is abnormal.

Handling Procedure

Check the HDFS service status.

1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. On the page that is displayed, check whether ALM-14000 HDFS Service Unavailable is reported.
   • If yes, go to Step 2.
   • If no, go to Step 3.

2. Clear this alarm according to the alarm help provided for ALM-14000 HDFS Service Unavailable.
   After the alarm is cleared, wait a few minutes and check whether the Guardian Service Unavailable alarm is cleared.

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

Check all TokenServer instances.

3. Log in to the node where the TokenServer instance resides as user omm and run the ps -ef|grep "guardian.token.server.Server" command to check whether the TokenServer process exists on the node.
   • If yes, go to Step 5.
   • If no, restart the faulty TokenServer instance and go to Step 4.

4. In the alarm list, check whether the Guardian Service Unavailable alarm is cleared.
   • If yes, no further action is required.
   • If no, go to Step 5.

Collect fault information.

5. On FusionInsight Manager, choose O&M > Log > Download.
6. Expand the Service drop-down list, and select Guardian for the destination cluster.
7. 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.
8. Send the collected fault logs to O&M personnel for help.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None