ALM-12042 Incorrect Configuration of Key Files

Updated on 2024-11-29 GMT+08:00

View PDF

The system checks whether critical configurations are correct every 5 minutes. This alarm is generated when the configurations are abnormal.

This alarm is cleared when the configurations become normal.

Alarm ID	Alarm Severity	Alarm Type	Service Type	Auto Cleared
12042	Major	Quality of service	FusionInsight Manager	Yes

Type	Parameter	Description
Location Information	Source	Specifies the cluster or system for which the alarm is generated.
	ServiceName	Specifies the service name for which the alarm is generated.
	RoleName	Specifies the role name for which the alarm is generated.
	HostName	Specifies the object (host ID) for which the alarm is generated.
	PathName	Specifies the path or name of the abnormal file.

Functions related to the file are abnormal.

If the permission on the okerberos and oldap key files is abnormal, authentication fails and jobs may fail.
If the permission on the controller and pms key files is abnormal, the process may be 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.

The file configuration is modified manually or the system is powered off unexpectedly.

Check abnormal file configuration.

On the FusionInsight Manager portal, choose O&M > Alarm > Alarms.
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.
Log in to the node for which the alarm is generated as user root.
View the ${BIGDATA_LOG_HOME}/nodeagent/scriptlog/checkfileconfig.log file and analyze the cause based on the error log. Locate the check standards of the file in the Related Information and manually check and modify the file based on the standards.

Run the vi file name command to enter the editing mode, and then press Insert to start editing.

After the modification is complete, press Esc to exit the editing mode and enter :wq to save the settings and exit.

For example:

vi /etc/ssh/sshd_config
Wait a hour and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 6.

Collect fault information.

On the FusionInsight Manager portal, choose O&M > Log > Download.
Select NodeAgent from the Service and click OK.
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.
Contact the O&M engineers and send the collected log information.

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

Check standards of /etc/fstab
Check whether the partitions configured in the /etc/fstab file can be found in /proc/mounts.

Check whether the swap partitions configured in fstab correspond to those in /proc/swaps.
Check the /etc/hosts configuration file.
Run cat /ect/hosts. If any of the following situations occurs, the /etc/hosts configuration file is abnormal:
1. The /etc/hosts file does not exist.
2. The host name is not configured in the file.
3. The host name maps to multiple IP addresses in the file.
4. The IP address corresponding to the host name does not exist in the command output of the ifconfig command.
5. One IP address maps to multiple host names in the file.
Check standards of /etc/ssh/sshd_config
Run the vi /etc/ssh/sshd_config command to check whether configuration items are configured as follows:
1. The value of UseDNS must be set to no.
2. The value of MaxStartups must be greater than or equal to 1000.
3. At least one of the PasswordAuthentication and ChallengeResponseAuthentication parameters must be left blank or at least one of the parameters be set to yes.