On this page

Show all

Help Center/ ServiceStage/ User Guide (ME-Abu Dhabi Region)/ FAQs/ What Should I Do If a VM Component Fails to Be Deployed or Updated?

What Should I Do If a VM Component Fails to Be Deployed or Updated?

Updated on 2022-12-05 GMT+08:00

View PDF

If a component fails to be deployed or upgraded on a VM, perform the following steps to locate and rectify the fault.

Log in to ServiceStage and choose Application Management > Application List.
Click the application name. The Overview page is displayed.
On the Environment View tab, select an environment to view the application components that have been deployed in the environment.
Click the name of a component that is not ready. On the Overview page of the component instance that is displayed, obtain the name of the component instance.
Choose Update. On the Update page, obtain the version number of the component instance.
Choose Instance and click before the instance which fails to be started or installed.
Click the Events tab to view the error information. If the system displays a message indicating that the port is occupied, you can deploy a port again.
If the log information obtained in 6 is not clear, obtain the logs of the component instance from the ECS.
1. Click the node where the instance resides to go to the host details page. If an EIP has been bound to the node, click the EIPs tab to obtain the EIP of the node and use the SSH client tool to connect to the node. Alternatively, click Remote Login in the upper-left corner to log in to the node and run the following command:
```
cd /var/log/application/{component_instance_name}/{version}
```
  Replace {component_instance_name} with the component instance name obtained in 4 and {version} with the version number obtained in 5.
  
  Run the ls command, and then run the cd command to access the sub-directory displayed after the ls command is run.
2. Obtain the detailed error logs from the sub-directory.
  If the component is a Tomcat8 component, view the catalina.out log to check the errors reported during Tomcat startup.
  
  For other types of applications, view the start_app.log file to check the errors reported during the startup.

Parent topic: FAQs

Previous topic: How Do I View the Causes for Application Component Deployment Failures?

Next topic: What Are the Constraints on Packaging a Node.js 8 Software Package?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot