Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ MapReduce Service/ User Guide/ MRS Cluster O&M/ MRS Cluster Alarm Handling Reference/ ALM-25004 Abnormal LdapServer Data Synchronization (For MRS 2.x or Earlier)

ALM-25004 Abnormal LdapServer Data Synchronization (For MRS 2.x or Earlier)

Updated on 2024-09-23 GMT+08:00

Description

This alarm is generated when LdapServer data on Manager is inconsistent. This alarm is cleared when the data becomes consistent.

This alarm is generated when LdapServer data in the cluster is inconsistent with LdapServer data on Manager. This alarm is cleared when the data becomes consistent.

Attribute

Alarm ID

Alarm Severity

Auto Clear

25004

Critical

Yes

Parameters

Parameter

Description

ServiceName

Specifies the service for which the alarm is generated.

RoleName

Specifies the role for which the alarm is generated.

HostName

Host for which the alarm is generated.

Impact on the System

LdapServer data inconsistency occurs because LdapServer data on Manager or in the cluster is damaged. The LdapServer process with damaged data cannot provide services externally, and the authentication functions of Manager and the cluster are affected.

Possible Causes

  • The network of the node where the LdapServer process locates is faulty.
  • The LdapServer process is abnormal.
  • The OS restart damages data on LdapServer.

Procedure

  1. Check whether the network where the LdapServer nodes reside is faulty.

    1. Go to the cluster details page and choose Alarms.
    2. Record the IP address of HostName in Location of the alarm as IP1 (if multiple alarms exist, record the IP addresses as IP1, IP2, and IP3 respectively).
    3. Contact O&M personnel and use PuTTY to log in to the node corresponding to IP1. Run the ping command on the node to check whether the IP address of the management plane of the active OMS node can be pinged.
      • If yes, go to 1.d.
      • If no, go to 2.a.
    4. Contact O&M personnel to recover the network and check whether the alarm ALM-25004 Abnormal LdapServer Data Synchronization is cleared.
      • If yes, no further action is required.
      • If no, go to 2.a.

  2. Check whether the LdapServer process is in normal state.

    1. Go to the cluster details page and choose Alarms.
    2. Check whether ALM-12004 OLdap Resource Is Abnormal is generated for LdapServer.
      • If yes, go to 2.c.
      • If no, go to 2.e.
    3. Rectify the fault by following steps provided in ALM-12004 OLdap Resource Is Abnormal.
    4. Check whether the alarm ALM-25004 Abnormal LdapServer Data Synchronization is cleared.
      • If yes, no further action is required.
      • If no, go to 2.e.
    5. On the Alarms page of MRS Manager, check whether the alarm ALM-12007 Process Fault of LdapServer is generated.
      • If yes, go to 2.f.
      • If no, go to 3.a.
    6. Rectify the fault by following steps provided in ALM-12007 Process Fault.
    7. Check whether the alarm ALM-25004 Abnormal LdapServer Data Synchronization is cleared.
      • If yes, no further action is required.
      • If no, go to 3.a.

  3. Check whether the OS restart damages data on LdapServer.

    1. Go to the cluster details page and choose Alarms.
    2. Record the IP address of HostName in Location of the alarm as IP1 (if multiple alarms exist, record the IP addresses as IP1, IP2, and IP3 respectively). Choose Services > LdapServer > Service Configuration and record the LdapServer port number as PORT. (If the IP address in the alarm location information is the IP address of the standby OMS node, the default port number is 21750.)
    3. Log in to node IP1 as user omm and run the ldapsearch -H ldaps://IP1:PORT -x -LLL -b dc=hadoop,dc=com command (if the IP address is the IP address of the standby OMS node, run the ldapsearch -H ldaps://IP1:PORT -x -LLL -b dc=hadoop,dc=com command before running this command). Check whether error information is displayed in the command output.
      • If yes, go to 3.d.
      • If no, go to 4.
    4. Recover the LdapServer and OMS nodes using backup data before the alarm is generated. For details, see section "Recovering Manager Data" in the Administrator Guide.
      NOTE:

      Use the OMS data and LdapServer data backed up at the same time to restore data. Otherwise, the service and operation may fail. To recover data when services run properly, you are advised to manually back up the latest management data and then recover the data. Otherwise, Manager data produced between the backup point in time and the recovery point in time will be lost.

    5. Check whether the alarm ALM-25004 Abnormal LdapServer Data Synchronization is cleared.
      • If yes, no further action is required.
      • If no, go to 4.

  4. Collect fault information.

    1. On MRS Manager, choose System > Export Log.
    2. Contact the O&M engineers and send the collected logs.

Reference

None

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback