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).
Service Node Faults

Service Node Faults

The SIS Console is Blank

Symptom

On ManageOne Operation Portal, the SIS Console is blank.

Possible Causes

When the Tomcat process of the SCC-Console node exits abnormally, it is not automatically started or the Daemon process is abnormal. As a result, multiple Tomcat processes are started at the same time.

Procedure
  1. Use PuTTY to log in to the FusionGuard-Console-FusionGuard01 management VM using the IP address corresponding to SCC-Console01.

    Default username: sccadmin; default password: Scloud12#$

  2. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

    sudo su - root

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

    TMOUT=0

  4. Run the following command to check whether the Tomcat process information and status are normal:

    ps -ef | grep tomcat

    If the following information is displayed, the process information and status are normal.

    root      7711  7179  0 11:36 pts/0    00:00:00 grep --color=auto tomcat
    root     22530  6466  0 09:28 pts/8    00:00:00 tailf /opt/tomcat/logs/catalina.     out
    tomcat   30609     1  0 10:29 ?        00:00:32 /usr/java/jdk1.8.0_181/bin/java      -Djava.util.logging.config.file=/opt/tomcat/conf/logging.properties -Djava.util.     logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySi     ze=2048 -Dignore.endorsed.dirs= -classpath /opt/tomcat/bin/bootstrap.jar:/opt/to     mcat/bin/tomcat-juli.jar -Dcatalina.base=/opt/tomcat -Dcatalina.home=/opt/tomca       -Djava.io.tmpdir=/opt/tomcat/temp org.apache.catalina.startup.Bootstrap start
    • If yes, contact technical support for assistance.
    • If no, go to 5.

  5. Run the following command to forcibly stop the Tomcat process:

    kill -9 {Process ID}

  6. Run the following command to restart the Tomcat process:

    systemctl restart systemd-tomcat

  7. Log in to ManageOne as a VDC administrator or a VDC operator using a browser.

    URL in the non-B2B scenario: https://Address for accessing ManageOne Operation Portal, for example, https://console.demo.com

    URL in the B2B scenario: https://Address for accessing ManageOne Tenant Portal, for example, https://tenant.demo.com

  8. Select your region and then project from the drop-down list on the top menu bar.
  9. Check whether the SIS service can be accessed.

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

The "Background maintenance is in progress. Please try again later." Message Is Displayed on the SIS Console

Symptom

On ManageOne Operation Portal, the "Background maintenance is in progress. Please try again later." message is displayed on the SIS Console.

Possible Causes
  • The Nginx process of SCC-LB is abnormal.
  • The Tomcat process of SCC-Service is abnormal.
  • The SCC-DB GaussDB process is abnormal.
Procedure
  1. Log in to the SCC-LB node and check whether the Nginx process is not running properly or whether there is a process scheduling exception in the operating system.

    1. Use PuTTY to log in to the SCC-LB-FusionGuard01 management VM using the IP address corresponding to SCC-LB01.

      Default username: sccadmin; default password: Scloud12#$

    2. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

      sudo su - root

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

      TMOUT=0

    4. Run the following command to check whether the Nginx process information and status are normal:

      ps -ef | grep nginx

      If the following information is displayed, the process information and status are normal.

      nginx     1524     1  0 Oct18 ?        00:00:00 nginx: master process /usr/sbin nginx
      root      8877  8417  0 11:49 pts/0    00:00:00 grep --color=auto nginx
      nginx    26499  1524  0 Oct23 ?        00:03:24 nginx: worker process
      nginx    26500  1524  0 Oct23 ?        00:01:36 nginx: worker process
      • If yes, go to 2.
      • If no, go to 1.e.
    5. Run the following command to restart the Nginx process:

      systemctl restart nginx

    6. Log in to ManageOne as a VDC administrator or a VDC operator using a browser.

      URL in the non-B2B scenario: https://Address for accessing ManageOne Operation Portal, for example, https://console.demo.com

      URL in the B2B scenario: https://Address for accessing ManageOne Tenant Portal, for example, https://tenant.demo.com

    7. Select your region and then project from the drop-down list on the top menu bar.
    8. Check whether the SIS service can be accessed.
      • If yes, no further action is required.
      • If no, go to 2.

  2. Log in to the SCC-Service node and check whether the Tomcat process is normal.

    1. Use PuTTY to log in to the SCC-Service-FusionGuard01 management VM using the IP address corresponding to SCC-Service01.

      Default username: sccadmin; default password: Scloud12#$

    2. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

      sudo su - root

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

      TMOUT=0

    4. Run the following command to check whether the Tomcat process information and status are normal:

      ps -ef | grep tomcat

      If the following information is displayed, the process information and status are normal.

      root      5181  4839  0 11:52 pts/0    00:00:00 grep --color=auto tomcat
      cloud    12843     1  0 Oct18 ?        00:36:23 /usr/java/default/jre/bin/java -    Dnop -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls    .ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webres    ources -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Xms1024m -Xmx    4096m -XX:MaxPermSize=256m -XX:-UseGCOverheadLimit -XX:+UseConcMarkSweepGC -clas    spath /opt/software/tomcat/secas-tomcat/bin/bootstrap.jar:/opt/software/tomcat/s    ecas-tomcat/bin/tomcat-juli.jar -Dcatalina.base=/opt/software/tomcat/secas-tomca    t -Dcatalina.home=/opt/software/tomcat/secas-tomcat -Djava.io.tmpdir=/opt/softwa    re/tomcat/secas-tomcat/temp org.apache.catalina.startup.Bootstrap start
      • If yes, go to 3.
      • If no, go to 2.e.
    5. Run the following command to restart the Tomcat process:

      systemctl restart systemd-tomcat

    6. Log in to ManageOne as a VDC administrator or a VDC operator using a browser.

      URL in the non-B2B scenario: https://Address for accessing ManageOne Operation Portal, for example, https://console.demo.com

      URL in the B2B scenario: https://Address for accessing ManageOne Tenant Portal, for example, https://tenant.demo.com

    7. Select your region and then project from the drop-down list on the top menu bar.
    8. Check whether the SIS service can be accessed.
      • If yes, no further action is required.
      • If no, go to 3.

  3. Log in to the SCC-DB node and check whether the database is abnormal.

    1. Use PuTTY to log in to the SCC-GuassDB-FusionGuard01 management VM using the IP address corresponding to SCC-DB01.

      Default username: sccadmin; default password: Scloud12#$

    2. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

      sudo su - root

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

      TMOUT=0

    4. Run the following command to check whether the database resources monitored by OMMHA are normal:

      service had query

      If the following information is displayed, the resources are normal.

      NODE                 ROLE           PHASE           RESS            VER                                                                                                                                            START
      APPDB01(db_h1)       standby        Deactived       normal          V100R001C01                                                                                                                                    2018-10-22 19:16:00
      APPDB02(db_h2)       active         Actived         normal          V100R001C01                                                                                                                                    2018-10-18 19:49:36
      
      --------------------------------------------------------------------------------                                                                                                                               ------------------------
                           ID    RES                      STAT            RET                                                                                                                                            TYPE
      APPDB01(db_h1):      1     exfloatip                Normal          Abnormal                                                                                                                                       Single_active
                           2     gaussDB                  Normal          Standby_norm                                                                                                                               al  Active_standby
                           3     redis                    Normal          Standby_norm                                                                                                                               al  Active_standby
      
      APPDB02(db_h2):      1     exfloatip                Normal          Normal                                                                                                                                         Single_active
                           2     gaussDB                  Normal          Active_norma                                                                                                                               l   Active_standby
                           3     redis                    Normal          Active_norma                                                                                                                               l   Active_standby
      • If yes, contact technical support for assistance.
      • If no, go to 3.e.
    5. Log in to the faulty node and run the following command to switch to the dbadmin user:

      su dbadmin

    6. Run the following command to restart the DB node:

      gs_ctl restart

    7. Log in to ManageOne as a VDC administrator or a VDC operator using a browser.

      URL in the non-B2B scenario: https://Address for accessing ManageOne Operation Portal, for example, https://console.demo.com

      URL in the B2B scenario: https://Address for accessing ManageOne Tenant Portal, for example, https://tenant.demo.com

    8. Select your region and then project from the drop-down list on the top menu bar.
    9. Check whether the SIS service can be accessed.
      • If yes, no further action is required.
      • If no, contact technical support for assistance.

Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 1196

Downloads: 12

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