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-1005008 ads_console Process Does Not Exist

ALM-1005008 ads_console Process Does Not Exist

Description

This alarm is generated when service processes of the ADS Console are faulty.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1005008

Critical

Yes

Parameters

Name

Meaning

PROCESS

Service process

Impact on the System

Services are unavailable.

Possible Causes

  1. The server is faulty.
  2. The server network is abnormal.
  3. The service is not started.

Procedure

  1. Use the IP addresses of the EIS_PublicVM-Console1 and EIS_PublicVM-Console2 nodes to check whether the network is normal. Specifically, run the following command on the console:

    ping Node IP address

    • If yes, go to 2.
    • If no, contact technical support for assistance.

  2. Use PuTTY to log in to EIS_PublicVM-Console1 and EIS_PublicVM-Console2 to manage VMs.

    Default account: ads; default password: Cloud12#$

  3. Check whether the service is started.

    Run the following command on the console:

    ps -ef | grep tomcat

    The following is an example of the normal command output.

    If the Tomcat process cannot be found, the service is not started.

  4. Go to the /opt/dbs/ads-console/bin directory and run the following command to start the Tomcat:

    sh startup.sh

  5. Run the following command to check whether Tomcat is started:

    ps -ef | grep tomcat

    • If Tomcat is found, Tomcat is started successfully. The alarm is cleared and no further action is required.
    • If Tomcat fails to start, view the catalina.out file under /opt/dbs/ads-console/logs/ and identify the failure cause.

  6. If the preceding check results are normal but the alarm persists, contact technical support for assistance.

Alarm Clearing

After the fault is rectified, the system will automatically clear the alarm.

Reference

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 36351

Downloads: 31

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