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 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).
Console Faults

Console Faults

404 Error Is Displayed on the HDCS Console

Symptom

The HDCS console is not displayed and error 404 is reported when you choose Console > Big Data > Hadoop Cluster Service after logging in to ManageOne Operation Portal as a VDC administrator.

Possible Causes
  • Tomcat is not running properly. (The HDCS Console fails to be started or Tomcat is not started after the system is restarted.)
  • A component of the HDCS Console is faulty.
  • An upstream component (for example, Nginx) of the HDCS Console is faulty.
Troubleshooting Process
  1. Verify that the Tomcat process is running properly.
  2. View the /var/log/bigdata/console/console.log file to locate the fault cause.
  3. Check whether upstream components (for example, Nginx) are normal.
Procedure
  1. Check whether the Tomcat process is running properly.

    • Use PuTTY to log in to the HDCS Console node as the datasight user with the IP address of the HDCS Console node.

      Default account: datasight; default password: Cloud12#$

    • Run the ps -ef |grep tomcat command to check whether the Tomcat process exists.
    • If the Tomcat process does not exist, run the bash /opt/mrs/tomcat/bin/startup.sh command to start the process. After the Tomcat process is started successfully, the following Tomcat information is displayed:
      datasig+  19541  19332  0 10:25 pts/2    00:00:00 grep --color=auto tomcat
      datasig+  68065      1  0 Nov28 ?        00:06:40 /usr/local/java/jdk1.8.0_77/jre/bin/java -Dnop -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Xms4096m -Xmx4096m -Djava.endorsed.dirs=/opt/huawei/tomcat/endorsed -classpath /opt/huawei/tomcat/bin/bootstrap.jar:/opt/huawei/tomcat/bin/tomcat-juli.jar -Dcatalina.base=/opt/huawei/tomcat -Dcatalina.home=/opt/huawei/tomcat -Djava.io.tmpdir=/opt/huawei/tomcat/temp org.apache.catalina.startup.Bootstrap start
    • If the Tomcat process is displayed after you run the ps -ef |grep tomcat command, check the Tomcat log file /opt/mrs/tomcat/logs/catalina.out to check whether the Console is started properly.
    • If a Console startup exception exists and is caused by common problems (for example, a port is occupied), check the environment information of the HDCS Console node; if the exception is caused by other configuration problems, check whether the component information is correctly configured.

  2. Check the Console log file /var/log/bigdata/console/console.log if Tomcat is properly running as shown in 1. If the log file contains error information, rectify the fault based on the error information.
  3. If the Console logs in 2 does not contain error information, check whether upstream components, such as Nginx, are normal. Contact relevant personnel to verify that the access request has been delivered to the upstream components and been transmitted to the Console component.

    If the error persists after the preceding operations, contact technical support for assistance.

Console Does Not Display Cluster Information

Symptom

The HDCS console is displayed, but no cluster information is displayed, and requests sent to the background are not responded when you choose Console > Big Data > Hadoop Cluster Service after logging in to ManageOne Operation Portal as a VDC administrator.

Possible Causes
  • The pass-through file of the Console is incorrectly configured. As a result, requests are not sent to downstream components.
  • A downstream component, such as Service, Deploy, or Database, is faulty and cannot properly process the requests from the Console.
Troubleshooting Process
  1. Query the Console log. If the Console does not receive the requests, an upstream component is faulty.
  2. Query the Service log. If Service receives the requests, a downstream component is faulty.
  3. If the Console receives the requests but Service does not receive the requests, check whether the pass-through file of the Console is correctly configured.
Procedure
  1. To monitor Console logs, use PuTTY to log in to the HDCS Console node as the datasight user using the IP address of the HDCS Console node.

    Default account: datasight; default password: Cloud12#$

  2. Run the tailf /var/log/bigdata/console/console.log command to view logs of the Console node.
  3. To monitor Service logs, use PuTTY to log in to the HDCS Console node as the datasight user using the IP address of the HDCS Console node.

    Default account: datasight; default password: Cloud12#$

  4. Run the tailf /var/log/bigdata/apigateway/api-gateway.log command to view the logs of the Service node.
  5. Log in to ManageOne Operation Portal and select Hadoop Cluster Service on the homepage to trigger an access request for HDCS Console page. Then, check whether request information is recorded in logs of the Console and Service nodes.
  6. If the console node does not receive the request or the service node receives the request, locate the fault on the upstream or downstream components. If the console node receives the request but the service node does not receive the request, check whether items in /opt/mrs/tomcat/webapps/hcs/WEB-INF/classes/config/directrouters/rest_api_gateway.xml, the pass-through file of the console node, are correctly configured. For example, check whether the IP address and port number of the host and the mapping of the API tag are correct.

    If the error persists after the preceding operations, contact technical support for assistance.

Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 1195

Downloads: 12

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