ALM-24015 Flume MonitorServer Certificate File Has Expired¶
This section applies to MRS 3.2.0-LTS.2 or later.
Description¶
MonitorServer checks whether its certificate file in the system has expired every hour. This alarm is generated when the server certificate has expired. This alarm is automatically cleared when the MonitorServer certificate file becomes valid again.
Attribute¶
Alarm ID | Alarm Severity | Auto Clear |
|---|---|---|
24015 | Major | Yes |
Parameters¶
Name | Meaning |
|---|---|
Source | Specifies the cluster for which the alarm is generated. |
ServiceName | Specifies the service for which the alarm is generated. |
RoleName | Specifies the role for which the alarm is generated. |
HostName | Specifies the host for which the alarm is generated. |
Impact on the System¶
The Flume client cannot access the Flume server.
Possible Causes¶
The MonitorServer certificate file has expired.
Procedure¶
View alarm information.
Log in to FusionInsight Manager and choose O&M. In the navigation pane on the left, choose Alarm > Alarms. On the page that is displayed, locate the row containing ALM-24015 MonitorServer Certificate Has Expired, and view the Location information. View the IP address of the instance for which the alarm is generated.
Check whether the certificate file in the system is valid. If it is not, generate a new one.
Log in to the node for which the alarm is generated as user root and run the su - omm command to switch to user omm.
Run the following command to go to the MonitorServer certificate file directory:
cd ${BIGDATA_HOME}/FusionInsight_Porter_*/install/FusionInsight-Flume-*/flume/conf
Run the following command to check the effective time and expiration time of the user certificate to determine whether the certificate file is still in the validity period:
openssl x509 -noout -text -in ms_sChat.crt
Run the following command to go to the Flume script directory:
cd ${BIGDATA_HOME}/FusionInsight_Porter_*/install/FusionInsight-Flume-*/flume/bin
Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later.
sh geneJKS.sh -m Custom password of the MonitorServer certificate on the server -n Custom password of the MonitorServer certificate on the client
If yes, go to 8.
If no, go to 7.
Note
The custom certificate passwords must meet the following complexity requirements:
Contain at least four types of uppercase letters, lowercase letters, digits, and special characters.
Contain 8 to 64 characters.
Be changed periodically (for example, every three months), and certificates and trust lists are generated again to ensure security.
Log in to the Flume node for which the alarm is generated as user omm and repeat 5 to 6. Then, check whether the alarm is automatically cleared one hour later.
Check whether this alarm is generated again during periodic system check.
If yes, go to 9.
If no, no further action is required.
Collect the fault information.
On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
Select MonitorServer in the required cluster for Service.
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 O&M personnel and provide the collected logs.
Alarm Clearing¶
This alarm is automatically cleared after the fault is rectified.