Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/compute/docs/troubleshooting/viewing-serial-port-output below:

Viewing serial port output | Compute Engine Documentation

Stay organized with collections Save and categorize content based on your preferences.

A virtual machine (VM) instance has four virtual serial ports. The instance's operating system, BIOS, and other system-level entities often write output to the serial ports, which makes serial port output useful for troubleshooting crashes, failed boots, startup issues, or shutdown issues.

This page describes methods to view serial port output, including using Cloud Logging to retain serial port output even after an instance is stopped or deleted. If you need to send commands to a serial port while an instance is running, see Interacting with the serial console.

Serial port output is accessible through the Google Cloud console, the gcloud CLI, and REST, but only while the VM instance is running. Logs are limited to the most recent 1 MB of output per port.

If you enable serial port output logging, Cloud Logging provides the first 50 gibibytes (GiB) per month of logging for free and retains logs for 30 days.

• If you want to log serial port output in Cloud Logging, familiarize yourself with Cloud Logging.
• If you haven't already, then set up authentication. Authentication is the process by which your identity is verified for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine by selecting one of the following options:

  Select the tab for how you plan to use the samples on this page:

  Console

  When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.

  gcloud

  1. Install the Google Cloud CLI. After installation, initialize the Google Cloud CLI by running the following command:

     gcloud init

     If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.

     Note: If you installed the gcloud CLI previously, make sure you have the latest version by running gcloud components update.
  2. Set a default region and zone.
  REST

  To use the REST API samples on this page in a local development environment, you use the credentials you provide to the gcloud CLI.

  Install the Google Cloud CLI. After installation, initialize the Google Cloud CLI by running the following command:

  gcloud init

  If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.

  For more information, see Authenticate for using REST in the Google Cloud authentication documentation.

You can control whether your instances send serial port output to Cloud Logging by setting project- or instance-level metadata. You can also disable the feature for all of the users in your organization by setting an organization policy.

By default, serial port output logging to Cloud Logging is disabled. If serial port output logging to Cloud Logging is not constrained for your organization, then you can enable or disable it for projects and for individual VM instances by setting the serial-port-logging-enable metadata entry to true or false.

If you set a project-wide metadata entry, all VM instances in the project inherit that setting implicitly. If you set an instance metadata entry, the metadata entry is enabled for that VM only, regardless of the project setting.

You can set a metadata entry by using the Google Cloud console, the gcloud CLI, or the Compute Engine API. For more information, see Setting custom metadata.

For example, the following gcloud CLI command enables serial port output logging to Cloud Logging for your project:

gcloud compute project-info add-metadata \
    --metadata serial-port-logging-enable=true

Similarly, the following gcloud CLI command enables serial port output logging to Cloud Logging for a specific instance instead:

gcloud compute instances add-metadata INSTANCE_NAME \
    --metadata serial-port-logging-enable=true

To disable serial port output logging to Cloud Logging, set serial-port-logging-enable to false:

gcloud compute instances add-metadata INSTANCE_NAME \
    --metadata serial-port-logging-enable=false

From within Cloud Logging, you can create an exclusion filter to remove specific serial port entries from the Logs Explorer. For example, with a project-wide metadata entry that is set to serial-port-logging-enable=true, you can disable serial port output logging for specific VM instances by using an advanced filter:

logName = "projects/PROJECT_ID/logs/serialconsole.googleapis.com%2Fserial_port_1_output"
resource.type = "gce_instance"
resource.labels.instance_id != "INSTANCE_1_ID"
resource.labels.instance_id != "INSTANCE_2_ID"

You can disable serial port output logging to Cloud Logging for your entire organization by setting an Organization Policy, which constrains certain configurations of Google Cloud resources. Specifically, set the following boolean constraint: constraints/compute.disableSerialPortLogging. For more information, see Creating and managing organization policies.

Disabling serial port logging by setting constraints/compute.disableSerialPortLogging to true is not retroactive. Existing VM instances with a metadata entry that enables serial port logging to Cloud Logging continue to log to Cloud Logging unless you reset the metadata for those instances.

After setting this organization constraint to true, you cannot set instance or project metadata to enable serial port output logging to Cloud Logging for any instances within the organization.

1. In the Google Cloud console, go to the VM instances page.

   Go to the VM instances page

2. Select the VM instance for which you want to view serial port output.

3. Under Logs, click Serial port 1, 2, 3, or 4. System-level entities typically use the first serial port (port 1), which is also known as the serial console.

Use the gcloud compute instances get-serial-port-output command.

gcloud compute instances get-serial-port-output INSTANCE_NAME \
  --port PORT \
  --start START \
  --zone ZONE

Replace the following:

• INSTANCE_NAME: the name of the instance.
• PORT: the number of the port (1, 2, 3, or 4) for which you want to view output. System-level entities typically use the first serial port (port 1), which is also known as the serial console. By default, the output of the first serial port is returned.
• START: the byte index (zero-based) of the first byte you want returned. Use this flag if you want to continue getting the output from a previous request that was too long to return in one attempt.
• ZONE: the zone of your instance.

In the API, create a get request to the instances.getSerialPortOutput method.

GET https://compute.googleapis.com/compute/projects/PROJECT_ID/zones/ZONE/instances/INSTANCE_NAME/serialPort

1. Enable serial port logging to Cloud Logging.

2. Go to the VM instances page.

   Go to the VM instances page

3. Select the VM instance for which you want to view startup agent logs.

4. Under Logs, click Cloud Logging to view Cloud Logging logs.

For more information, including information about filtering, see Using the Logs Explorer.

Serial port output is escaped by using the open source Abseil C++ library's CHexEscape() method, so non-UTF8 characters are encoded as hex strings. You can use the corresponding CUnescape() method to get the exact output that was sent to the serial port.

The following are examples of common errors you might encounter in serial port output.

The following error might occur in OS journal logs when IPv6 isn't configured:

ERROR addresses.go:301 Error configuring IPv6: Internet Systems Consortium DHCP Client 4.2.5

Ignore this error. This error doesn't affect your VM.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-07 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["VM instances have four virtual serial ports that output data useful for troubleshooting crashes, failed boots, and other system-level issues."],["Serial port output can be viewed in real-time through the Google Cloud console, gcloud CLI, and REST, but is limited to the most recent 1 MB of output per port."],["Cloud Logging can be enabled to retain serial port output beyond instance runtime, providing the first 50 GiB per month for free, and logs are kept for 30 days."],["You can enable or disable serial port output logging for projects or individual VM instances using metadata settings, or disable the feature for an entire organization through organization policies."],["Non-UTF8 characters within the serial port output are encoded as hex strings and can be decoded to reveal their original form using the `CUnescape()` method."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4