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

Service Node Faults

The SIS Console Is Blank

Symptom

On the ManageOne operation plane, the Security Index Service (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 is normal.

    • 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. Use a browser to log in to the ManageOne operation plane as a VDC administrator or VDC operator.

    Login address: https://Domain name for accessing the console home page. Example: https://console.type.com.

  8. Select a region and a project from the drop-down box in the upper left corner of the page.
  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 the ManageOne operation plane, 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 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.

      • 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. Use a browser to log in to the ManageOne operation plane as a VDC administrator or VDC operator.

      Login address: https://Domain name for accessing the console home page. Example: https://console.type.com.

    7. Select a region and a project from the drop-down box in the upper left corner of the page.
    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.

      • 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. Use a browser to log in to the ManageOne operation plane as a VDC administrator or VDC operator.

      Login address: https://Domain name for accessing the console home page. Example: https://console.type.com.

    7. Select a region and a project from the drop-down box in the upper left corner of the page.
    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.

      • 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. Use a browser to log in to the ManageOne operation plane as a VDC administrator or VDC operator.

      Login address: https://Domain name for accessing the console home page. Example: https://console.type.com.

    8. Select a region and a project from the drop-down box in the upper left corner of the page.
    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-10

Document ID: EDOC1100063248

Views: 23103

Downloads: 37

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