El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Obtaining ECS Console Logs

Updated on 2024-11-27 GMT+08:00

Scenarios

When an ECS cannot start or run properly, you can download and view ECS console logs for troubleshooting, for example, checking whether the kernel and service configuration are correct.

The ECS console logs record ECS operations, such as ECS starting, stopping, restarting, or forcibly restarting. Through the management console, you can obtain the ECS logs within one hour.

Notes

  • The system does not record the logs for forcible ECS stopping.
  • The system supports viewing console logs for the ECSs running the following OSs:
    • Red Hat Enterprise Linux 6.x series
    • Red Hat Enterprise Linux 7.x series
    • CentOS 6.x series
    • CentOS 7.x series
    • Ubuntu 14.x series
    • Ubuntu 16.x series
    • SUSE 11.x series
    • SUSE 12.x series
    • OpenSUSE 13.x series
    • OpenSUSE 42.x series
    • Debian 16.x series
    • Fedora series
    • Freebsd series
    • CoreOS series
  • The ECSs running Windows do not support console logs.
  • The system can save up to 100 KB log files.

Procedure

  1. Log in to the ECS.
  2. Check and modify the grub file.

    The configuration method varies depending on the OS.
    NOTE:

    To prevent impact on the start of the recovery mode, you are advised to modify only the item used for the default start.

    • For CentOS 6 and Red Hat 6, perform the following steps:
      1. Run the following command to open the configuration file:

        vi /boot/grub/menu.lst

      2. Locate the row that contains linux, linux16, or kernel (depending on the system), add console=ttyS0 to its end, and delete parameter rhgb quiet. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
    • For CentOS 7, Red Hat 7, and Ubuntu 14, perform the following steps:
      1. Run the following command to open the configuration file:

        vi /boot/grub2/grub.cfg

      2. Locate the row that contains linux, linux16, or kernel (depending on the system), add console=ttyS0 to its end, and delete parameter rhgb quiet. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
    • For SUSE Linux 11, perform the following steps:
      1. Run the following command to open the configuration file:

        vi /boot/grub/menu.1st

      2. Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
    • For SUSE Linux 12, openSUSE 13, and openSUSE 42, perform the following steps:
      1. Run the following command to open the configuration file:

        vi /boot/grub2/grub.cfg

      2. Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
    • For Debian and Ubuntu 16, perform the following steps:
      1. Run the following command to open the configuration file:

        vi /boot/grub/grub.cfg

      2. Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
    • For Fedora, perform the following steps:
      1. Run the following command to open the configuration file:

        vi /boot/grub2/grub.cfg

      2. Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
    • For FreeBSD, perform the following steps:
      1. Run the following command to open the configuration file:

        vi /boot/loader.conf

      2. Add console="comconsole". If console="comconsole" already exists, you do not need to add it. Save the change and exit.
    • For CoreOS, perform the following steps:
      1. Run the following command to check whether ttyS0 has been configured:

        cat /proc/cmdline | grep ttyS0

        • If yes, ttyS0 has been configured.
        • If no, ttyS0 has not been configured. Go to 2.b.
      2. Run the following command to open the configuration file to be edited:

        vi /usr/share/oem/grub.cfg

        NOTE:

        If the /usr/share/oem/grub.cfg configuration file does not exist, manually create the file.

      3. Add set linux_append="console=ttyS0". If set linux_append="console=ttyS0" already exists, you do not need to add it. Save the change and exit.

  3. On the Elastic Cloud Server page, click Restart.
  4. Obtain ECS console logs.

    1. Log in to the management console.
    2. Under Computing, click Elastic Cloud Server.
    3. On the Elastic Cloud Server page, click the name of the target ECS.
    4. On the page providing details about the ECS, click the Console Logs tab.
    5. Choose the number of lines to be displayed for a log from the Displayed Lines drop-down list.
    6. Click Query.

      View details of the displayed log.

      NOTE:

      After you click Query, the system will not automatically update the displayed log. To view the latest log, click Query again.

    7. (Optional) Click Download to download the information of the displayed log.

      Downloaded log files are in .txt format.

Utilizamos cookies para mejorar nuestro sitio y tu experiencia. Al continuar navegando en nuestro sitio, tú aceptas nuestra política de cookies. Descubre más

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback