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).
Restarting a Parent Microservice

Restarting a Parent Microservice

This section uses MODriverFrameworkService as an example to describe how to restart the child microservice and parent microservice.

Context

Multiple microservices of ManageOne share a process to save system resources and improve the running efficiency. Therefore, microservices are classified into parent microservices and child microservices.

When ManageOne is changed and a microservice needs to be restarted, if the microservice is a child microservice, you need to restart the corresponding parent microservice to make the process take effect and ensure the normal running of the system.

Procedure

  1. Use a browser to log in to the ManageOne deployment plane.

    URL: https://Floating IP address of the deployment plane:31943; default account: admin

  2. Query the nodes where the microservice is deployed.

    1. Choose Deployment > Microservice Deployment > Environments from the main menu.
    2. In the upper right corner, select All and Product from the search area, and enter MODriverFrameworkService in the search box.
    3. Click MODriverFrameworkService/OMGlobal/regionAlias in the Environment area.
    4. In the Node List area, view the nodes where MODriverFrameworkService is deployed.

  3. Perform the following operations to restart the MODriverFrameworkService service:

    1. Log in to all nodes where MODriverFrameworkService is deployed as user sopuser, and run the following command to switch to user ossadm:

      su - ossadm

    2. Run the following commands to restart the MODriverFrameworkService service:

      . /opt/oss/manager/bin/engr_profile.sh

      ipmc_adm -cmd stopapp -app MODriverFrameworkService

      ipmc_adm -cmd startapp -app MODriverFrameworkService

  4. Use PuTTY to log in to a node obtained in 2.d as user sopuser.

    The default password of user sopuser is D4I$awOD7k.

  5. Run the following command to switch to user ossuser:

    su - ossuser

    Enter the password of user ossuser as prompted. The default password of the ossuser user is 79y52unx@R.

  6. Run the following commands to query the parent microservice of MODriverFrameworkService:

    cd /opt/oss/envs

    find -name start.sh 2>/dev/null| xargs grep MODriverFrameworkService | awk -F'-' '{print $2}' | awk -F'/' '{print $1}'

    Replace MODriverFrameworkService in the preceding command with the actual microservice name. Information similar to the following is displayed:

    MOAccessMgmtService
    MOAccessMgmtService
    MODriverFrameworkService
    MODriverFrameworkService
    • If the microservice in the command and the other microservice are included in the displayed information, the other microservice is the parent microservice of the microservice in the command. Go to 7 to restart the parent microservice.

      For example, the preceding command output indicates that the parent microservice of MODriverFrameworkService is MOAccessMgmtService.

    • If no information is displayed or the command output does not contain any microservices except the queried microservice, the queried microservice is the parent microservice. No further action is required.

  7. Query the nodes where the parent microservice is deployed.

    1. Choose Deployment > Microservice Deployment > Environments from the main menu.
    2. In the upper right corner, select All and Product from the search area, and enter MOAccessMgmtService in the search box.
    3. Click MOAccessMgmtService/OMGlobal/regionAlias in the Environment column.
    4. In the Node List area, view the nodes where MODriverFrameworkService is deployed.

  8. Perform the following operations to restart the MOAccessMgmtService service:

    1. Log in to all nodes where MOAccessMgmtService is deployed as user sopuser, and run the following command to switch to user ossadm:

      su - ossadm

    2. Run the following commands to restart the MOAccessMgmtService service:

      . /opt/oss/manager/bin/engr_profile.sh

      ipmc_adm -cmd stopapp -app MOAccessMgmtService

      ipmc_adm -cmd startapp -app MOAccessMgmtService

Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 23140

Downloads: 37

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