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


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


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

ALM-1110017 Tomcat Process Does Not Exist


This alarm is generated when a zombie tomcat process exists on an AS node.


Alarm ID

Alarm Severity

Auto Clear







Alarm Name

Alarm name.

Source System

Name of the source system where the alarm is generated.

IP Address

IP address of the ECS where the alarm is generated.

Last Occurred At

Time when the alarm was generated for the last time.

Additional Information

Supplementary information about the alarm.

Impact on the System

An AS service exception may occur.

Possible Causes

The child process exits before the parent process but the parent process does not invoke the wait or waitpid command. In this case, the child process becomes a zombie process.


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

    • URL: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example,
    • 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 VM identified in 4.

    Default username: admin; default password: IaaS@OS-CLOUD9!

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


  7. Run the following command to check whether the tomcat process exists:

    ps -ef|grep autoscaling

    If the following information is displayed, the process exists:

    admin     5637     1 26 10:11 pts/0    00:02:40 /opt/autoscaling/jre1.8/bin/java -Dnop -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Djava.endorsed.dirs=/opt/autoscaling/tomcat/endorsed -classpath /opt/autoscaling/tomcat/bin/bootstrap.jar:/opt/autoscaling/tomcat/bin/tomcat-juli.jar -Dcatalina.base=/opt/autoscaling/tomcat -Dcatalina.home=/opt/autoscaling/tomcat org.apache.catalina.startup.Bootstrap start
    admin    31140  4836  0 10:21 pts/0    00:00:00 grep --color=auto autoscaling
    • If yes, go to 8.
    • If no, go to 9.

  8. Run the following command to stop the tomcat process:

    sh /opt/autoscaling/autoscaling-api/ stop

  9. Run the following command to restart the tomcat process:

    sh /opt/autoscaling/autoscaling-api/ restart

    If the following information is displayed, the tomcat process is restarted successfully:

    stop autoscaling-api succeed.
    start autoscaling-api succeed.

  10. If the alarm persists, contact technical support for assistance.

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 35772

Downloads: 31

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