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).
Resource Template Service Troubleshooting

Resource Template Service Troubleshooting

Description

An RTS service node exception is detected on the ManageOne OM plane and needs to be rectified.

Possible Causes

  • The VM is faulty.
  • The RTS service process is abnormal.
  • The database is abnormal.

Troubleshooting

Figure 24-16 shows the troubleshooting process.

Figure 24-16 Troubleshooting process on nodes

Fault Rectification

  1. Obtain the IP address of the faulty node from the ManageOne OM plane alarm email.
  2. Check whether you can use PuTTY to log in to the faulty node.

    The default username is rts, and the default password is IaaS@SERVICE-CLOUD8!.
    • If yes, go to 3.
    • If no, the VM is faulty. Contact technical support for assistance.

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

    TMOUT=0

  4. Run the following command to check whether the Heat processes exist, including heat-api, heat-api-cfn, heat-engine, and groupwatch.

    ps -ef | grep heat

    • If yes, go to 5.
    • If no, go to 9 to restart the process. If the restart fails, go to 5.

      The heat process exists if information similar to the following is displayed:

      [root@RTS-SERVICE01 rts]# ps -ef | grep heat
      root     11129  4204  0 22:59 pts/0    00:00:00 grep --color=auto heat
      opensta+ 26332     1  0 Apr04 ?        00:00:01 /usr/bin/python2.7 /usr/bin/heat-api --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/heat-api
      opensta+ 26348     1  0 Apr04 ?        00:00:01 /usr/bin/python2.7 /usr/bin/heat-api-cfn --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/heat-api-cfn
      opensta+ 26364     1  0 Apr04 ?        00:00:01 /usr/bin/python2.7 /usr/bin/groupwatch --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/groupwatch
      opensta+ 26365 26332  2 Apr04 ?        03:24:33 /usr/bin/python2.7 /usr/bin/heat-api --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/heat-api
      opensta+ 26366 26332  2 Apr04 ?        03:24:57 /usr/bin/python2.7 /usr/bin/heat-api --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/heat-api
      opensta+ 26367 26332  2 Apr04 ?        03:25:14 /usr/bin/python2.7 /usr/bin/heat-api --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/heat-api
      opensta+ 26376 26348  0 Apr04 ?        00:00:34 /usr/bin/python2.7 /usr/bin/heat-api-cfn --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/heat-api-cfn
      opensta+ 26377 26348  0 Apr04 ?        00:00:34 /usr/bin/python2.7 /usr/bin/heat-api-cfn --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/heat-api-cfn
      opensta+ 26378 26348  0 Apr04 ?        00:00:33 /usr/bin/python2.7 /usr/bin/heat-api-cfn --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/heat-api-cfn
      opensta+ 26380     1  1 Apr04 ?        02:06:45 /usr/bin/python2.7 /usr/bin/heat-engine --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/heat-engine
      opensta+ 26389 26364  0 Apr04 ?        00:00:34 /usr/bin/python2.7 /usr/bin/groupwatch --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/groupwatch
      opensta+ 26390 26364  0 Apr04 ?        00:00:34 /usr/bin/python2.7 /usr/bin/groupwatch --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/groupwatch
      opensta+ 26392 26364  0 Apr04 ?        00:00:34 /usr/bin/python2.7 /usr/bin/groupwatch --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/groupwatch
      opensta+ 26469 26380  2 Apr04 ?        03:22:24 /usr/bin/python2.7 /usr/bin/heat-engine --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/heat-engine
      opensta+ 26470 26380  2 Apr04 ?        03:22:59 /usr/bin/python2.7 /usr/bin/heat-engine --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/heat-engine
      opensta+ 26471 26380  2 Apr04 ?        03:21:43 /usr/bin/python2.7 /usr/bin/heat-engine --config-file /etc/heat/heat.conf --log-dir /var/log/RTS/heat-engine

  5. Run the vi /var/log/RTS/heat-engine/heat-engine.log command to check the logs of the RTS node and ensure that no Exception log exists.

    If "(psycopg2.OperationalError) could not connect to server" is displayed, the database connection is abnormal. In this case, check the database status.

  6. Use PuTTY to log in to the database node as user rts.

    The default password of user rts is IaaS@SERVICE-CLOUD8!.

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

    TMOUT=0

  8. Run the sudo su - root command to switch to user root and run the service had query command to check whether the database status is normal.

    • If yes, go to 9.
    • If no, contact technical support for assistance.
    [root@I-RTS-DB01 rts]# service had query
    NODE                         ROLE           PHASE           RESS            VER             START
    I-RTS-DB01(I-RTS-DB01)       active         Actived         normal          V100R001C01     2018-03-23 08:18:00
    I-RTS-DB02(I-RTS-DB02)       standby        Deactived       normal          V100R001C01     2018-03-23 08:18:01
    
    --------------------------------------------------------------------------------------------------------
                                 ID    RES                      STAT            RET             TYPE
    I-RTS-DB01(I-RTS-DB01):      1     exfloatip                Normal          Normal          Single_active
                                 2     gaussDB                  Normal          Active_normal   Active_standby
    
    I-RTS-DB02(I-RTS-DB02):      1     exfloatip                Normal          Abnormal        Single_active
                                 2     gaussDB                  Normal          Standby_normal  Active_standby

  9. Run the following command on the RTS node to start the RTS process:

    sh /etc/heat/heat/start_heat_service.sh

  10. Contact technical support for assistance if RTS still cannot provide services after the preceding operations are complete.
Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 23168

Downloads: 37

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