No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-37014 Lock File of the GaussDB Process Already Exists

ALM-37014 Lock File of the GaussDB Process Already Exists

Description

This alarm is generated when a Coordinator instance or the lock file of a Coordinator instance fails to be created.

Attribute

Alarm ID

Alarm Severity

Auto Clear

37014

Major

Yes

Parameters

Name

Meaning

ServiceName

Identifies the service for which the alarm is generated.

RoleName

Identifies the role for which the alarm is generated.

HostName

Identifies the host for which the alarm is generated.

Instance

Identifies the instance for which the alarm is generated.

Impact on the System

The instance whose lock file fails to be created cannot be started, and the cluster cannot be started accordingly.

Possible Causes

System instances are terminated abnormally, leaving residual lock files in the system.

Procedure

  1. Log in to the FusionInsight Manager.

    1. Log in to the ManageOne OM plane using a browser, then choose Alarms.
      • Login address: https://URL for the homepage of the ManageOne OM plane:31943. Example: https://oc.type.com:31943.
      • Default username: admin, default password: Huawei12#$.
    2. In the alarm list, locate and click the target alarm name in the Name column. The Alarm Details and Handling Recommendations dialog box is displayed.
    3. Locate the value in the IP Address/URL/Domain Name column, which is the float IP address of the FusionInsight Manager.
    4. Log in to the FusionInsight Manager using a browser.
      • Login address: https://float IP address of the FusionInsight Manager:28443/web. Example: https://10.10.192.100:28443/web.
      • Default username: admin, default password: obtain it from the system administrator.

  2. On FusionInsight Manager, click Alarms. On the alarm list, locate the alarm and obtain the information about the node and instance for which the alarm is generated from Location in the Alarm Details area.
  3. Log in to the node where the alarm is generated as the omm user.

    Default user: omm, default password: Bigdata123@.

  4. Run the source ${BIGDATA_HOME}/mppdb/.mppdbgs_profile command to initialize the environment variables.
  5. Run the following command to obtain the node where the alarm is generated as well as the data directory of the corresponding instances: (In the following example, the node is 10.252.153.218 and the data directory is /srv/BigData/mppdb/data1/coordinator.)

    gs_om -t status --detail
    [  CMServer State   ]
    
    node               node_ip         instance                                    state
    --------------------------------------------------------------------------------------
    1  lfgphicprb09394 10.252.153.218  2    /opt/huawei/Bigdata/mppdb/cm/cm_server Primary
    3  lfgphicprb09396 10.252.153.81   1    /opt/huawei/Bigdata/mppdb/cm/cm_server Standby
    
    [   Cluster State   ]
    
    cluster_state   : Normal
    redistributing  : No
    balanced        : No
    
    [ Coordinator State ]
    
    node               node_ip         instance                                  state
    ------------------------------------------------------------------------------------
    1  lfgphicprb09394 10.252.153.218  5001 /srv/BigData/mppdb/data1/coordinator Down
    2  lfgphicprb09395 10.252.153.234  5002 /srv/BigData/mppdb/data1/coordinator Normal
    3  lfgphicprb09396 10.252.153.81   5003 /srv/BigData/mppdb/data1/coordinator Normal
    

  6. Log in to the node in SSH mode, and run the following command to go to the data directory and check whether there is a postmaster.pid file:

    cd /srv/BigData/mppdb/data1/coordinator

    ll

    • If there is, go to 7.
    • If there is not, go to 10.

  7. Run the following command to obtain the PID in the first line of the postmaster.pid file:

    cat postmaster.pid

    42883
    /srv/BigData/mppdb/data1/coordinator
    1541404937
    25308
    /opt/huawei/Bigdata/mppdb/mppdb_tmp
    localhost
     25308001    131076

  8. Run the following command to check whether there is a process corresponding to the PID:

    ps -ef |grep 42883

    omm       42883      1  4 Nov05 ?        17:25:59 /opt/huawei/Bigdata/mppdb/core/bin/gaussdb --coordinator -D /srv/BigData/mppdb/data1/coordinator
    omm      125791  55322  0 15:10 pts/0    00:00:00 grep --color=auto 42883
    • If there is, go to 9.
    • If there is not, go to 10.

  9. Run the following commands to stop the process and remove the postmaster.pid file, respectively. Then, check whether the alarm is cleared.

    kill -9 42883

    rm -f postmaster.pid

    • If it is, no further action is required.
    • If it is not, go to 10.

  10. On FusionInsight Manager, choose System > Log Download.
  11. Select MPPDB from the Services drop-down list box and click OK.
  12. Set Start Time for log collection to 1 hour ahead of the alarm generation time and End Time to 1 hour after the alarm generation time, and click Download.
  13. Contact Technical Support and send the collected logs.

Alarm Clearing

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

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 37954

Downloads: 31

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next