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


To have a better experience, please upgrade your IE browser.


HUAWEI CLOUD Stack 6.5.0 Backup and Restoration Guide 03

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).
Checking the Microservice Running Status

Checking the Microservice Running Status


  1. Check the microservice status on the deployment system node.

    1. Log in to the active node on Deployment Portal as user sopuser and run the following command to switch to user ossadm:

      su - ossadm

    2. Run the following commands to check the microservice status:

      . /opt/oss/manager/bin/

      ipmc_adm -cmd statusapp

      The command output is as follows:

      Process Name         Process Type     App Name                 Tenant Name  Process Mode  IP               PID     Status  
      febservice-1-0       febservice       FEBService               manager      cluster     13129   RUNNING 
      auditlog-1-0         auditlog         AuditService             manager      cluster     13175   RUNNING 
      deploycore-1-0       deploycore       DeployCoreService        manager      cluster     13242   RUNNING  
      • App Name indicates the microservice name.
      • Status indicates the microservice running status. RUNNING indicates that the microservice is running. STOPPED indicates that the microservice is stopped.

  2. (Optional) If the microservice has been deployed on other nodes, repeat the previous steps to check the microservice status on other nodes.
Updated: 2019-06-14

Document ID: EDOC1100062366

Views: 755

Downloads: 9

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