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

FusionCloud 6.3.1.1 Troubleshooting Guide 02

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).
ECS_UI Troubleshooting

ECS_UI Troubleshooting

Symptom

An alarm reported to the ManageOne OM plane indicates that the Tomcat process on an ECS UI node fails and needs to be restored.

Possible Causes

The Tomcat process encounters an exception.

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. Click Log In. In the navigation tree, choose Alarms > Current Alarms. In the alarm location information, obtain the IP address of the node where the faulty process resides.
  3. Use PuTTY to log in to the CONSOLE01 or CONSOLE02 VM corresponding to the IP address of the faulty node.

    The default username is ecm, and the default password is Huawei12#$.

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

    TMOUT=0

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

    ps -ef|grep tomcat

    • If yes, the Tomcat process has recovered. Then, go to 9.
    • If no, go to 6.

    If the following information is displayed, the Tomcat process is available.

    [ecm@CONSOLE01 controllers]$ ps -ef|grep tomcat
    ecm       5453     1  4 02:07 ?        00:00:32 /opt/common/jre/bin/java -Dnop -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -server -Xms2048m -Xmx2048m -Djdk.tls.ephemeralDHKeySize=2048 -Dorg.apache.catalina.security.SecurityListener.UMASK=0077 -Djava.endorsed.dirs=/opt/ecm/tomcat/endorsed -classpath /opt/ecm/tomcat/bin/bootstrap.jar:/opt/ecm/tomcat/bin/tomcat-juli.jar -Dcatalina.base=/opt/ecm/tomcat -Dcatalina.home=/opt/ecm/tomcat -Djava.io.tmpdir=/opt/ecm/tomcat/temp org.apache.catalina.startup.Bootstrap start
    ecm      16023 18643  0 02:19 pts/3    00:00:00 grep --color=auto tomcat
    [ecm@CONSOLE01 controllers]$ 

  6. Check Tomcat startup logs and search the keyword Exception. Ensure that no exception logs exist. Otherwise, contact technical support for assistance.

    tailf /opt/ecm/tomcat/logs/catalina.YYYY-MM-DD.log

  7. Run the following command to start the Tomcat process:

    sh /opt/ecm/tomcat/bin/startup.sh

  8. Run the following command to check whether the Tomcat process is available:

    ps -ef|grep tomcat

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

  9. After 10 minutes, check whether the alarm is cleared.

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

Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 22836

Downloads: 37

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