ALM-12041 Incorrect Permission on Key Files

Alarm Description

The system checks whether the permission, user, and user group information about critical directories or files is normal every 5 minutes. This alarm is generated when the information is abnormal.

This alarm is cleared when the information becomes normal.

Alarm Attributes

Alarm Parameters

Impact on the System

System functions are unavailable.

• If the permission of key files okerberos and oldap is abnormal, the authentication fails and the job may fail to run.
• If the permission of key files controller and pms is abnormal, the process becomes faulty, which may affect the elastic scaling performance.
• If the permission on key Tomcat files is abnormal, the login and viewing functions of FusionInsight Manager are affected.

Possible Causes

The file permission is abnormal or the file is lost due to a user manually modified information such as the file permission, user, and user group, or the system is powered off unexpectedly.

Handling Procedure

Check whether the abnormal file exists and whether the permission on the abnormal file is correct.

1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms.
2. Check the value of HostName to obtain the host name involved in this alarm. Check the value of PathName to obtain the path or name of the abnormal file.
3. Log in to the node for which the alarm is generated as user root.

   For details about how to log in to a cluster node, see Logging In to an MRS Cluster Node.

4. Run the following command to check the current user, permissions, and user group information of the file or directory on the host:

   ll Path name

   The path name is the abnormal file path obtained in Step 2.

5. Go to ${BIGDATA_HOME}/om-agent/nodeagent/etc/agent/autocheck directory. Then search for the name of the abnormal file and check the due permissions on the file.

   cd ${BIGDATA_HOME}/om-agent/nodeagent/etc/agent/autocheck

   vi keyfile

   

   To ensure proper configuration synchronization between the active and standby OMS servers, files, directories, and files and sub-directories in the directories configured in $OMS_RUN_PATH/workspace/ha/module/hasync/plugin/conf/filesync.xml will also be monitored except files and directories in keyfile. User omm must have read and write permissions of files and read and execute permissions of directories.

6. Compare the real-world permission of the file with the due permission obtained in Step 5 and correct the permission, user, and user group information for the file.
7. Wait an hour and check whether the alarm is cleared.
   • If yes, no further action is required.
   • If no, go to Step 8.

   If the disk partition where the cluster installation directory resides is used up, some temporary files will be generated in the program installation directory when running the sed command fails. Users do not have the read, write, and execute permissions of these temporary files. The system reports an alarm indicating that permissions of temporary files are abnormal if these files are within the monitoring range of the alarm. Perform the preceding alarm handling processes to clear the alarm. Alternatively, you can directly delete the temporary files after confirming that the files with abnormal permissions are temporary. The following is an example temporary file generated after a sed command execution failure.

   

Collect fault information.

8. On the FusionInsight Manager portal, choose O&M > Log > Download.
9. Expand the Service drop-down list, select NodeAgent, and click OK.
10. Click 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.
11. Contact the O&M personnel and send the collected log information.

Alarm Clearance

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

Related Information

None