View instance system logs and screenshots

更新时间:
复制 MD 格式

Because Elastic Compute Service (ECS) is a virtualized cloud service, you cannot connect a display device or take manual screenshots. However, ECS caches the system log from the instance's last startup, restart, or shutdown and lets you retrieve real-time screenshots of the instance. You can use these features to analyze and troubleshoot instance failures, such as an unresponsive operating system, an abnormal restart, or a connection failure.

Prerequisites

The instance must be in the Running (Running) state to retrieve system logs and screenshots.

Background information

System logs for an ECS instance are an important part of diagnostics. To diagnose and analyze failures, you can retrieve log information about the instance's startup and other issues. Logs that the system outputs through the serial port contain two types of information: log content from system startup and log content from a system kernel failure or error. For more information, see the Yunqi Community blog post Troubleshooting operating system issues with diagnostic logs.

Limits

Note the following limits when you use this feature:

  • You can retrieve screenshots but not system logs for Windows instances.

  • You cannot retrieve system logs and screenshots for retired instance types. For more information, see Retired instance types.

  • You cannot retrieve system logs and screenshots for instances created before January 1, 2018.

Procedure

  1. Go to ECS console - Instances.

  2. In the top navigation bar, select the region and resource group of the resource that you want to manage. Region

  3. Find the instance to troubleshoot and click its ID. On the instance details page, click All Operations. Then, search for and click Obtain Instance Screenshot or Obtain Instance System Logs.

  4. View the instance screenshot or system log.

    • Example of a Windows instance screenshot:

    • Example of a Linux instance screenshot:

    • Example of a Linux instance system log:

What to do next

Troubleshoot the following issues: