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-2000401 Tomcat Process Does Not Exist

ALM-2000401 Tomcat Process Does Not Exist

Description

The SMN service uses Tomcat as the web container for the SMN console. This alarm is generated when the Tomcat process is not running on a Tomcat node.

Attribute

Alarm ID

Alarm Severity

Auto Clear

2000401

Critical

Yes

Parameters

Parameter

Description

Resource name

Name of the device for which the alarm is generated

Resource type

MONITOR

Monitor type

Tomcat process monitoring

Host IP address

IP address of the host

Details

Data in recent periods

Threshold

Threshold for generating an alarm

Impact on the System

The alarmed node cannot provide services.

Possible Causes

  • The crontab job is abnormal.
  • The Tomcat configuration file is incorrect.

Procedure

  1. Log in to ManageOne Maintenance Portal using a browser.

    • URL: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943
    • Default username: admin; default password: Huawei12#$

  2. On the menu bar in the upper part of the page, choose Alarms > Current Alarms.
  3. In the alarm list, locate the alarm to be handled, and click on the left of the alarm. The Details page is displayed.
  4. Choose Location Info, obtain the host IP address, that is, the IP address of the node where the alarm is generated.
  5. Use PuTTY to log in to the node for which the alarm is generated. Ensure that the management IP address of the node obtained in 4 is used to establish the connection.

    The default username is hermes. The default password is Hermes@123.

  6. Run the following command to disable user logout upon system timeout:

    TMOUT=0

  7. Run the following command to switch to the root user:

    sudo su - root

    The default password is Cloud12#$.

  8. Run the following command to check whether the crontab job is disabled:

    cat /etc/crontab |grep tomcat

    */1 * * * * root su hermes -c "/opt/hermes/smn_home/bin/tomcat_monitor.sh check" >/dev/null 2>&1

    If # is displayed at the beginning of the command output, the crontab job is disabled.

    • If yes, delete # to enable the crontab job.
    • If no, go to 9.

  9. Run the following commands to switch to user hermes and manually restart the Tomcat process:

    su - hermes

    sh /opt/hermes/smn_home/bin/tomcat_monitor.sh restart

  10. Run the following command to check whether the Tomcat process is running properly:

    ps -ef|grep tomcat |grep hermes

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

  11. Ten minutes later, check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Reference

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 45726

Downloads: 33

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