| <!DOCTYPE html> |
| <html lang="en"> |
| <head> |
| <meta charset="utf-8"> |
| <meta name="viewport" content="width=device-width,initial-scale=1"> |
| <title>Viewing Che workspaces logs :: Eclipse Che Documentation</title> |
| <link rel="canonical" href="https://www.eclipse.org/che/docs/stable/end-user-guide/viewing-che-workspaces-logs/"> |
| <meta name="description" content="Viewing Che workspaces logs"> |
| <meta name="keywords" content="administration-guide, viewing-che-workspaces-logs"> |
| <meta name="generator" content="Antora 3.0.2"> |
| <link rel="stylesheet" href="../../../../docs/_/css/site.css"> |
| <link rel="stylesheet" href="../../../../docs/_/css/extra.css"> |
| <link rel="stylesheet" href="../../../../docs/_/font-awesome-4.7.0/css/font-awesome.min.css"> |
| <link rel="icon" href="../../../../docs/_/img/favicon.ico" type="image/x-icon"> |
| <meta name="robots" content="noindex"> |
| <script>var uiRootPath = '../../../../docs/_'</script> |
| <script async src="https://www.googletagmanager.com/gtag/js?id=UA-37306001-2"></script> |
| <script>function gtag(){dataLayer.push(arguments)};window.dataLayer=window.dataLayer||[];gtag('js',new Date());gtag('config','UA-37306001-2')</script> |
| <script>var uiRootPath = '../../../../docs/_'</script> |
| </head> |
| <body class="article"> |
| <header class="header"> |
| <nav class="navbar"> |
| <div class="navbar-brand"> |
| <div class="navbar-item"> |
| <button class="navbar-burger" data-target="topbar-nav"> |
| <span></span> |
| <span></span> |
| <span></span> |
| </button> |
| <img src="../../../../docs/_/img/icon-eclipse-che.svg" class="navbar-logo" alt="Eclipse Che logo"> |
| <a href="https://www.eclipse.org/che/docs/index.html">Eclipse Che Documentation</a> |
| </div> |
| </div> |
| <div id="topbar-nav" class="navbar-menu"> |
| <div class="navbar-end"> |
| <div class="navbar-item search hide-for-print"> |
| <div id="search-field" class="field"> |
| <input id="search-input" type="text" placeholder="Search the docs"> |
| </div> |
| </div> |
| <a class="navbar-item" href="https://www.eclipse.org/che/">Home</a> |
| <a class="navbar-item" href="https://che.eclipseprojects.io/">Blog</a> |
| <a class="navbar-item" href="https://github.com/eclipse/che">Source Code</a> |
| </div> |
| </div> |
| </nav> |
| </header> |
| <div class="body"> |
| <div class="nav-container" data-component="docs" data-version="next"> |
| <aside class="nav"> |
| <div class="panels"> |
| <div class="nav-panel-menu is-active" data-panel="menu"> |
| <nav class="nav-menu"> |
| <h3 class="title"><a href="../../overview/introduction-to-eclipse-che/">Documentation</a></h3> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="0"> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="1"> |
| <a class="nav-link" href="../../overview/introduction-to-eclipse-che/">Introduction to Che</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="0"> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="1"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../hosted-che/hosted-che/">Eclipse Che hosted by Red Hat</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../../hosted-che/try-in-web-ide-github-action/">Try in Web IDE GitHub action</a> |
| </li> |
| </ul> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="0"> |
| <button class="nav-item-toggle"></button> |
| <span class="nav-text">User Guide</span> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="1"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../adopting-che/">Adopting Che</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../developer-workspaces/">Developer workspaces</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../first-time-contributors/">Badge for first-time contributors</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../benefits-of-pull-requests-review-in-che/">Reviewing pull and merge requests</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../supported-languages/">Supported languages</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="1"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../user-onboarding/">User onboarding</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../starting-a-new-workspace-with-a-clone-of-a-git-repository/">Starting a new workspace with a clone of a Git repository</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../optional-parameters-for-the-urls-for-starting-a-new-workspace/">Optional parameters for the URLs for starting a new workspace</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../url-parameter-concatenation/">URL parameter concatenation</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../url-parameter-for-the-workspace-ide/">URL parameter for the workspace IDE</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../url-parameter-for-starting-duplicate-workspaces/">URL parameter for starting duplicate workspaces</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../url-parameter-for-the-devfile-file-name/">URL parameter for the devfile file name</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../url-parameter-for-the-devfile-file-path/">URL parameter for the devfile file path</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../basic-actions-you-can-perform-on-a-workspace/">Basic actions you can perform on a workspace</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../authenticating-to-a-git-server-from-a-workspace/">Authenticating to a Git server from a workspace</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="1"> |
| <a class="nav-link" href="../customizing-workspace-components/">Customizing workspace components</a> |
| </li> |
| <li class="nav-item" data-depth="1"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../selecting-a-workspace-ide/">Selecting a workspace IDE</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../selecting-an-ide-by-using-a-url-parameter/">Selecting an in-browser IDE for a new workspace by using a URL parameter</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../specifying-an-in-browser-ide-for-a-git-repository-by-using-che-editor.yaml/">Specifying an in-browser IDE for a Git repository by using <code>che-editor.yaml</code></a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="1"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../using-credentials-and-configurations-in-workspaces/">Using credentials and configurations in workspaces</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../using-git-credentials/">Using Git credentials</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../enabling-artifact-repositories-in-a-restricted-environment/">Enabling artifact repositories in a restricted environment</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../enabling-maven-artifact-repositories/">Maven</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../enabling-gradle-artifact-repositories/">Gradle</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../enabling-npm-artifact-repositories/">npm</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../enabling-python-artifact-repositories/">Python</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../enabling-go-artifact-repositories/">Go</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../enabling-nuget-artifact-repositories/">NuGet</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../creating-image-pull-secrets/">Creating image pull Secrets</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../mounting-secrets/">Mounting Secrets</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../mounting-configmaps/">Mounting ConfigMaps</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="1"> |
| <a class="nav-link" href="../requesting-persistent-storage-for-workspaces/">Requesting persistent storage for workspaces</a> |
| </li> |
| <li class="nav-item" data-depth="1"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../integrating-with-kubernetes/">Integrating with Kubernetes</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../automatic-token-injection/">Automatic Kubernetes token injection</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../navigating-che-from-openshift-developer-perspective/">Navigating Che from OpenShift Developer Perspective</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../navigating-openshift-web-console-from-che/">Navigating OpenShift web console from Che</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="1"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../troubleshooting-che/">Troubleshooting Che</a> |
| <ul class="nav-list"> |
| <li class="nav-item is-current-page" data-depth="2"> |
| <a class="nav-link" href="./">Viewing Che workspaces logs</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../investigating-failures-at-a-workspace-start-using-the-verbose-mode/">Troubleshooting workspace start failures</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../troubleshooting-slow-workspaces/">Troubleshooting slow workspaces</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../troubleshooting-network-problems/">Troubleshooting network problems</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="1"> |
| <a class="nav-link" href="../adding-a-vscode-extension/">Adding a Visual Studio Code extension to a workspace</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="0"> |
| <button class="nav-item-toggle"></button> |
| <span class="nav-text">Administration Guide</span> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="1"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/preparing-the-installation/">Preparing the installation</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../../administration-guide/supported-platforms/">Supported platforms</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/architecture-overview/">Architecture</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/server-components/">Server components</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/che-operator/">Che operator</a> |
| </li> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/devworkspace-operator/">Dev Workspace operator</a> |
| </li> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/gateway/">Gateway</a> |
| </li> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/dashboard/">User dashboard</a> |
| </li> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/devfile-registries/">Devfile registries</a> |
| </li> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/che-server/">Che server</a> |
| </li> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/postgresql/">PostgreSQL</a> |
| </li> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/plug-in-registry/">Plug-in registry</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/user-workspaces/">User workspaces</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../../administration-guide/calculating-che-resource-requirements/">Calculating Che resource requirements</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="1"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/installing-che/">Installing Che</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../../administration-guide/installing-the-chectl-management-tool/">Installing the chectl management tool</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../../administration-guide/installing-che-on-openshift-using-cli/">Installing Che on OpenShift using CLI</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../../administration-guide/installing-che-on-openshift-using-the-web-console/">Installing Che on OpenShift using the web console</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../../administration-guide/installing-che-in-a-restricted-environment/">Installing Che in a restricted environment</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/installing-che-locally/">Installing Che locally</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/installing-che-on-red-hat-openshift-local/">Installing Che on Red Hat OpenShift Local</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/installing-che-on-minikube/">Installing Che on Minikube</a> |
| </li> |
| </ul> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="1"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/configuring-che/">Configuring Che</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/understanding-the-checluster-custom-resource/">Understanding the <code>CheCluster</code> Custom Resource</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/using-chectl-to-configure-the-checluster-custom-resource-during-installation/">Using chectl to configure the <code>CheCluster</code> Custom Resource during installation</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/using-the-cli-to-configure-the-checluster-custom-resource/">Using the CLI to configure the CheCluster Custom Resource</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/checluster-custom-resource-fields-reference/"><code>CheCluster</code> Custom Resource fields reference</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/configuring-namespace-provisioning/">Configuring namespaces</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/configuring-workspace-target-namespace/">Configuring namespace name</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/provisioning-namespaces-in-advance/">Provisioning namespaces in advance</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/configuring-server-components/">Configuring server components</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/mounting-a-secret-as-a-file-or-an-environment-variable-into-a-container/">Mounting a Secret or a ConfigMap as a file or an environment variable into a Eclipse Che container</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/advanced-configuration-options-for-the-che-server-component/">Advanced configuration options for Che server</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/configuring-workspaces-globally/">Configuring workspaces globally</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/configuring-the-number-of-workspaces-that-a-user-can-create/">Configuring the number of workspaces that a user can create</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/deploying-che-with-support-for-git-repositories-with-self-signed-certificates/">Git with self-signed certificates</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/configuring-workspaces-nodeselector/">Configuring workspaces nodeSelector</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/caching-images-for-faster-workspace-start/">Caching images for faster workspace start</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/defining-the-list-of-images-to-pull/">Defining the list of images</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/defining-the-memory-parameters-for-the-image-puller/">Defining the memory settings</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/installing-image-puller-on-openshift-using-the-web-console/">Installing Image Puller on OpenShift using the web console</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/installing-image-puller-on-openshift-using-cli/">Installing Image Puller on OpenShift using CLI</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/configuring-observability/">Configuring observability</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/che-theia-workspaces/">Che-Theia workspaces</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/the-woopra-telemetry-plugin/">The Woopra telemetry plug-in</a> |
| </li> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/creating-a-telemetry-plugin/">Creating a telemetry plug-in</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/configuring-server-logging/">Configuring server logging</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/collecting-logs-using-chectl/">Collecting logs using chectl</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/monitoring-with-prometheus-and-grafana/">Monitoring with Prometheus and Grafana</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/installing-prometheus-and-grafana/">Installing Prometheus and Grafana</a> |
| </li> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/monitoring-the-dev-workspace-operator/">Monitoring the Dev Workspace Operator</a> |
| </li> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/monitoring-che/">Monitoring Che Server</a> |
| </li> |
| </ul> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/configuring-networking/">Configuring networking</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/configuring-che-hostname/">Configuring Che hostname</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/importing-untrusted-tls-certificates/">Importing untrusted TLS certificates to Che</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/configuring-ingresses/">Configuring Kubernetes Ingress</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/configuring-routes/">Configuring OpenShift Route</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/configuring-storage/">Configuring storage</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/installing-che-using-storage-classes/">Installing Che using storage classes</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/branding/">Branding</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/branding-che-theia/">Branding Che-Theia</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/managing-identities-and-authorizations/">Managing identities and authorizations</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/oauth-for-github-gitlab-or-bitbucket/">OAuth for GitHub, GitLab, or Bitbucket</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/configuring-oauth-2-for-github/">Configuring OAuth 2.0 for GitHub</a> |
| </li> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/configuring-oauth-2-for-gitlab/">Configuring OAuth 2.0 for GitLab</a> |
| </li> |
| <li class="nav-item" data-depth="4"> |
| <a class="nav-link" href="../../administration-guide/configuring-oauth-1-for-bitbucket/">Configuring OAuth 1.0 for Bitbucket</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/configuring-the-administrative-user/">Configuring the administrative user</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../administration-guide/removing-user-data/">Removing user data</a> |
| </li> |
| </ul> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="1"> |
| <a class="nav-link" href="../../administration-guide/managing-workloads-using-the-che-server-api/">Using the Che server API</a> |
| </li> |
| <li class="nav-item" data-depth="1"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../administration-guide/upgrading-che/">Upgrading Che</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../../administration-guide/upgrading-the-chectl-management-tool/">Upgrading the chectl management tool</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../../administration-guide/upgrading-che-7-41-on-openshift/">Upgrading Che 7.41 on Red Hat OpenShift</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../../administration-guide/specifying-the-update-approval-strategy/">Specifying the update approval strategy</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../../administration-guide/upgrading-che-using-the-web-console/">Upgrading Che using the OpenShift web console</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../../administration-guide/upgrading-che-using-the-cli-management-tool/">Upgrading Che using the CLI management tool</a> |
| </li> |
| <li class="nav-item" data-depth="2"> |
| <a class="nav-link" href="../../administration-guide/upgrading-che-using-the-cli-management-tool-in-restricted-environment/">Upgrading Che in a restricted environment</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="1"> |
| <a class="nav-link" href="../../administration-guide/uninstalling-che/">Uninstalling Che</a> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="0"> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="1"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../extensions/extensions/">Extensions</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="2"> |
| <button class="nav-item-toggle"></button> |
| <a class="nav-link" href="../../extensions/openshift-connector-overview/">OpenShift Connector</a> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../extensions/features-of-openshift-connector/">Features of OpenShift Connector</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../extensions/installing-openshift-connector-in-che/">Installing OpenShift Connector in Eclipse Che</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../extensions/authenticating-with-openshift-connector-from-che/">Authenticating with OpenShift Connector from Eclipse Che</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../extensions/creating-components-with-openshift-connector-in-che/">Creating Components with OpenShift Connector in Eclipse Che</a> |
| </li> |
| <li class="nav-item" data-depth="3"> |
| <a class="nav-link" href="../../extensions/connecting-source-code-from-github-to-a-openshift-component-using-openshift-connector/">Connecting source code from GitHub to a OpenShift Component</a> |
| </li> |
| </ul> |
| </li> |
| </ul> |
| </li> |
| </ul> |
| </li> |
| <li class="nav-item" data-depth="0"> |
| <ul class="nav-list"> |
| <li class="nav-item" data-depth="1"> |
| <a class="nav-link" href="../../glossary/che-glossary/">Che glossary</a> |
| </li> |
| </ul> |
| </li> |
| </ul> |
| </nav> |
| </div> |
| <div class="nav-panel-explore" data-panel="explore"> |
| <div class="context"> |
| <span class="title">Documentation</span> |
| <span class="version">next</span> |
| </div> |
| <ul class="components"> |
| <li class="component is-current"> |
| <a class="title" href="../../../stable/overview/introduction-to-eclipse-che/">Documentation</a> |
| <ul class="versions"> |
| <li class="version is-current"> |
| <a href="../../overview/introduction-to-eclipse-che/">next</a> |
| </li> |
| <li class="version"> |
| <a href="../../../che-7/overview/introduction-to-eclipse-che/">old (7.41)</a> |
| </li> |
| <li class="version is-latest"> |
| <a href="../../../stable/overview/introduction-to-eclipse-che/">stable</a> |
| </li> |
| </ul> |
| </li> |
| </ul> |
| </div> |
| </div> |
| </aside> |
| </div> |
| <main class="article"> |
| <div class="toolbar" role="navigation"> |
| <button class="nav-toggle"></button> |
| <a href="../../../stable/overview/introduction-to-eclipse-che/" class="home-link"></a> |
| <nav class="breadcrumbs" aria-label="breadcrumbs"> |
| <ul> |
| <li><a href="../../overview/introduction-to-eclipse-che/">Documentation</a></li> |
| <li>User Guide</li> |
| <li><a href="../troubleshooting-che/">Troubleshooting Che</a></li> |
| <li><a href="./">Viewing Che workspaces logs</a></li> |
| </ul> |
| </nav> |
| <div class="page-versions"> |
| <button class="version-menu-toggle" title="Show other versions of page">next</button> |
| <div class="version-menu"> |
| <a class="version is-current" href="./">next</a> |
| <a class="version" href="../../../che-7/end-user-guide/viewing-che-workspaces-logs/">old (7.41)</a> |
| <a class="version" href="../../../stable/end-user-guide/viewing-che-workspaces-logs/">stable</a> |
| </div> |
| </div> |
| <div class="edit-this-page"><a href="https://github.com/eclipse/che-docs/edit/main/modules/end-user-guide/pages/viewing-che-workspaces-logs.adoc">Edit this Page</a></div> |
| </div> |
| <div class="content"> |
| <aside class="toc sidebar" data-title="Contents" data-levels="2"> |
| <div class="toc-menu"></div> |
| </aside> |
| <article class="doc"> |
| <h1 class="page">Viewing Che workspaces logs</h1> |
| <div id="preamble"> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>This section describes how to view Che workspaces logs.</p> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2 id="viewing-logs-from-language-servers-and-debug-adapters_che"><a class="anchor" href="#viewing-logs-from-language-servers-and-debug-adapters_che"></a>Viewing logs from language servers and debug adapters</h2> |
| <div class="sectionbody"> |
| <div class="sect2"> |
| <h3 id="checking-important-logs_che"><a class="anchor" href="#checking-important-logs_che"></a>Checking important logs</h3> |
| <div class="paragraph"> |
| <p>This section describes how to check important logs.</p> |
| </div> |
| <div class="olist arabic"> |
| <div class="title">Procedure</div> |
| <ol class="arabic"> |
| <li> |
| <p>In the OpenShift web console, click <strong>Applications</strong> → <strong>Pods</strong> to see a list of all the active workspaces.</p> |
| </li> |
| <li> |
| <p>Click on the name of the running Pod where the workspace is running. The Pod screen contains the list of all containers with additional information.</p> |
| </li> |
| <li> |
| <p>Choose a container and click the container name.</p> |
| <div class="admonitionblock note"> |
| <table> |
| <tr> |
| <td class="icon"> |
| <i class="fa icon-note" title="Note"></i> |
| </td> |
| <td class="content"> |
| <div class="paragraph"> |
| <p>The most important logs are the <code>theia-ide</code> container and the plug-ins container logs.</p> |
| </div> |
| </td> |
| </tr> |
| </table> |
| </div> |
| </li> |
| <li> |
| <p>On the container screen, navigate to the <strong>Logs</strong> section.</p> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="detecting-memory-problems_che"><a class="anchor" href="#detecting-memory-problems_che"></a>Detecting memory problems</h3> |
| <div class="paragraph"> |
| <p>This section describes how to detect memory problems related to a plug-in running out of memory. The following are the two most common problems related to a plug-in running out of memory:</p> |
| </div> |
| <div class="dlist"> |
| <dl> |
| <dt class="hdlist1">The plug-in container runs out of memory</dt> |
| <dd> |
| <p>This can happen during plug-in initialization when the container does not have enough RAM to execute the entrypoint of the image. The user can detect this in the logs of the plug-in container. In this case, the logs contain <code>OOMKilled</code>, which implies that the processes in the container requested more memory than is available in the container.</p> |
| </dd> |
| <dt class="hdlist1">A process inside the container runs out of memory without the container noticing this</dt> |
| <dd> |
| <p>For example, the Java language server (Eclipse JDT Language Server, started by the <code>vscode-java</code> extension) throws an <strong>OutOfMemoryException</strong>. This can happen any time after the container is initialized, for example, when a plug-in starts a language server or when a process runs out of memory because of the size of the project it has to handle.</p> |
| <div class="paragraph"> |
| <p>To detect this problem, check the logs of the primary process running in the container. For example, to check the log file of Eclipse JDT Language Server for details, see the relevant plug-in-specific sections.</p> |
| </div> |
| </dd> |
| </dl> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="logging-the-client-server-traffic-for-debug-adapters_che"><a class="anchor" href="#logging-the-client-server-traffic-for-debug-adapters_che"></a>Logging the client-server traffic for debug adapters</h3> |
| <div class="paragraph"> |
| <p>This section describes how to log the exchange between Che-Theia and a debug adapter into the <strong>Output</strong> view.</p> |
| </div> |
| <div class="ulist"> |
| <div class="title">Prerequisites</div> |
| <ul> |
| <li> |
| <p>A debug session must be started for the <strong>Debug adapters</strong> option to appear in the list.</p> |
| </li> |
| </ul> |
| </div> |
| <div class="olist arabic"> |
| <div class="title">Procedure</div> |
| <ol class="arabic"> |
| <li> |
| <p>Click <strong>File</strong> → <strong>Settings</strong> and then <strong>open Preferences</strong>.</p> |
| </li> |
| <li> |
| <p>Expand the <strong>Debug</strong> section in the <strong>Preferences</strong> view.</p> |
| </li> |
| <li> |
| <p>Set the <strong>trace</strong> preference value to <code>true</code> (default is <code>false</code>).</p> |
| <div class="paragraph"> |
| <p>All the communication events are logged.</p> |
| </div> |
| </li> |
| <li> |
| <p>To watch these events, click <strong>View → Output</strong> and select <strong>Debug adapters</strong> from the drop-down list at the upper right corner of the <strong>Output</strong> view.</p> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="viewing-logs-for-python_che"><a class="anchor" href="#viewing-logs-for-python_che"></a>Viewing logs for Python</h3> |
| <div class="paragraph"> |
| <p>This section describes how to view logs for the Python language server.</p> |
| </div> |
| <div class="ulist"> |
| <div class="title">Procedure</div> |
| <ul> |
| <li> |
| <p>Navigate to the <strong>Output</strong> view and select <strong>Python</strong> in the drop-down list.</p> |
| <div class="imageblock"> |
| <div class="content"> |
| <img src="../_images/logs/viewing-logs-for-python.png" alt="viewing logs for python"> |
| </div> |
| </div> |
| </li> |
| </ul> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="viewing-logs-for-go_che"><a class="anchor" href="#viewing-logs-for-go_che"></a>Viewing logs for Go</h3> |
| <div class="paragraph"> |
| <p>This section describes how to view logs for the Go language server.</p> |
| </div> |
| <div class="sect3"> |
| <h4 id="finding-the-go-path_che"><a class="anchor" href="#finding-the-go-path_che"></a>Finding the Go path</h4> |
| <div class="paragraph"> |
| <p>This section describes how to find where the <code>GOPATH</code> variable points to.</p> |
| </div> |
| <div class="ulist"> |
| <div class="title">Procedure</div> |
| <ul> |
| <li> |
| <p>Execute the <code>Go: Current GOPATH</code> command.</p> |
| <div class="imageblock"> |
| <div class="content"> |
| <img src="../_images/logs/finding-the-gopath.png" alt="Finding the Go path"> |
| </div> |
| </div> |
| <div class="imageblock"> |
| <div class="content"> |
| <img src="../_images/logs/viewing-gopath.png" alt="Viewing the Go path"> |
| </div> |
| </div> |
| </li> |
| </ul> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="viewing-debug-console-log-for-go_che"><a class="anchor" href="#viewing-debug-console-log-for-go_che"></a>Viewing the Debug Console log for Go</h4> |
| <div class="paragraph"> |
| <p>This section describes how to view the log output from the Go debugger.</p> |
| </div> |
| <div class="olist arabic"> |
| <div class="title">Procedure</div> |
| <ol class="arabic"> |
| <li> |
| <p>Set the <code>showLog</code> attribute to <code>true</code> in the debug configuration.</p> |
| <div class="listingblock"> |
| <div class="content"> |
| <pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{ |
| "version": "0.2.0", |
| "configurations": [ |
| { |
| "type": "go", |
| "showLog": true |
| .... |
| } |
| ] |
| }</code></pre> |
| </div> |
| </div> |
| </li> |
| <li> |
| <p>To enable debugging output for a component, add the package to the comma-separated list value of the <code>logOutput</code> attribute:</p> |
| <div class="listingblock"> |
| <div class="content"> |
| <pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{ |
| "version": "0.2.0", |
| "configurations": [ |
| { |
| "type": "go", |
| "showLog": true, |
| "logOutput": "debugger,rpc,gdbwire,lldbout,debuglineerr" |
| .... |
| } |
| ] |
| }</code></pre> |
| </div> |
| </div> |
| </li> |
| <li> |
| <p>The debug console prints the additional information in the debug console.</p> |
| <div class="imageblock"> |
| <div class="content"> |
| <img src="../_images/logs/viewing-debug-console-log-for-go.png" alt="viewing debug console log for go"> |
| </div> |
| </div> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="viewing-go-logs-output-in-the-output-panel_che"><a class="anchor" href="#viewing-go-logs-output-in-the-output-panel_che"></a>Viewing the Go logs output in the Output panel</h4> |
| <div class="paragraph"> |
| <p>This section describes how to view the Go logs output in the <strong>Output</strong> panel.</p> |
| </div> |
| <div class="olist arabic"> |
| <div class="title">Procedure</div> |
| <ol class="arabic"> |
| <li> |
| <p>Navigate to the <strong>Output</strong> view.</p> |
| </li> |
| <li> |
| <p>Select <strong>Go</strong> in the drop-down list.</p> |
| <div class="imageblock"> |
| <div class="content"> |
| <img src="../_images/logs/viewing-go-logs-output-in-the-output-panel.png" alt="viewing go logs output in the output panel"> |
| </div> |
| </div> |
| </li> |
| </ol> |
| </div> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="viewing-logs-for-the-nodedebug-nodedebug2-adapter_che"><a class="anchor" href="#viewing-logs-for-the-nodedebug-nodedebug2-adapter_che"></a>Viewing logs for the NodeDebug NodeDebug2 adapter</h3> |
| <div class="admonitionblock note"> |
| <table> |
| <tr> |
| <td class="icon"> |
| <i class="fa icon-note" title="Note"></i> |
| </td> |
| <td class="content"> |
| <div class="paragraph"> |
| <p>No specific diagnostics exist other than the general ones.</p> |
| </div> |
| </td> |
| </tr> |
| </table> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="viewing-logs-for-typescript_che"><a class="anchor" href="#viewing-logs-for-typescript_che"></a>Viewing logs for Typescript</h3> |
| <div class="sect3"> |
| <h4 id="enabling-the-label-switched-protocol-lsp-tracing_che"><a class="anchor" href="#enabling-the-label-switched-protocol-lsp-tracing_che"></a>Enabling the label switched protocol (LSP) tracing</h4> |
| <div class="olist arabic"> |
| <div class="title">Procedure</div> |
| <ol class="arabic"> |
| <li> |
| <p>To enable the tracing of messages sent to the Typescript (TS) server, in the <strong>Preferences</strong> view, set the <code>typescript.tsserver.trace</code> attribute to <code>verbose</code>. Use this to diagnose the TS server issues.</p> |
| </li> |
| <li> |
| <p>To enable logging of the TS server to a file, set the <code>typescript.tsserver.log</code> attribute to <code>verbose</code>. Use this log to diagnose the TS server issues. The log contains the file paths.</p> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="viewing-typescript-language-server-log_che"><a class="anchor" href="#viewing-typescript-language-server-log_che"></a>Viewing the Typescript language server log</h4> |
| <div class="paragraph"> |
| <p>This section describes how to view the Typescript language server log.</p> |
| </div> |
| <div class="olist arabic"> |
| <div class="title">Procedure</div> |
| <ol class="arabic"> |
| <li> |
| <p>To get the path to the log file, see the Typescript <strong>Output</strong> console:</p> |
| <div class="imageblock"> |
| <div class="content"> |
| <img src="../_images/logs/finding-the-typescript-language-server-log.png" alt="finding the typescript language server log"> |
| </div> |
| </div> |
| </li> |
| <li> |
| <p>To open log file, use the <strong>Open TS Server log</strong> command.</p> |
| <div class="imageblock"> |
| <div class="content"> |
| <img src="../_images/logs/viewing-typescript-language-server-log.png" alt="viewing typescript language server log"> |
| </div> |
| </div> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="viewing-typescript-logs-output-in-the-output-panel_che"><a class="anchor" href="#viewing-typescript-logs-output-in-the-output-panel_che"></a>Viewing the Typescript logs output in the Output panel</h4> |
| <div class="paragraph"> |
| <p>This section describes how to view the Typescript logs output in the <strong>Output</strong> panel.</p> |
| </div> |
| <div class="olist arabic"> |
| <div class="title">Procedure</div> |
| <ol class="arabic"> |
| <li> |
| <p>Navigate to the <strong>Output</strong> view</p> |
| </li> |
| <li> |
| <p>Select <strong>TypeScript</strong> in the drop-down list.</p> |
| <div class="imageblock"> |
| <div class="content"> |
| <img src="../_images/logs/viewing-typescript-logs-output-in-the-output-panel.png" alt="viewing typescript logs output in the output panel"> |
| </div> |
| </div> |
| </li> |
| </ol> |
| </div> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="viewing-logs-for-java_che"><a class="anchor" href="#viewing-logs-for-java_che"></a>Viewing logs for Java</h3> |
| <div class="paragraph"> |
| <p>Other than the general diagnostics, there are <a href="https://github.com/redhat-developer/vscode-java">Language Support for Java (Eclipse JDT Language Server)</a> plug-in actions that the user can perform.</p> |
| </div> |
| <div class="sect3"> |
| <h4 id="verifying-the-state-of-the-eclipse-jdt-language-server_che"><a class="anchor" href="#verifying-the-state-of-the-eclipse-jdt-language-server_che"></a>Verifying the state of the Eclipse JDT Language Server</h4> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>Check if the container that is running the Eclipse JDT Language Server plug-in is running the Eclipse JDT Language Server main process.</p> |
| </div> |
| <div class="olist arabic"> |
| <ol class="arabic"> |
| <li> |
| <p>Open a terminal in the container that is running the Eclipse JDT Language Server plug-in (an example name for the container: <code>vscode-javaxxx</code>).</p> |
| </li> |
| <li> |
| <p>Inside the terminal, run the <code>ps aux | grep jdt</code> command to check if the Eclipse JDT Language Server process is running in the container. If the process is running, the output is:</p> |
| <div class="listingblock"> |
| <div class="content"> |
| <pre>usr/lib/jvm/default-jvm/bin/java --add-modules=ALL-SYSTEM --add-opens java.base/java.util</pre> |
| </div> |
| </div> |
| <div class="paragraph"> |
| <p>This message also shows the Visual Studio Code Java extension used. If it is not running, the language server has not been started inside the container.</p> |
| </div> |
| </li> |
| <li> |
| <p>Check all logs described in <a href="./" class="xref page">Viewing Che workspaces logs</a>.</p> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="verifying-the-eclipse-jdt-language-server-features_che"><a class="anchor" href="#verifying-the-eclipse-jdt-language-server-features_che"></a>Verifying the Eclipse JDT Language Server features</h4> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>If the Eclipse JDT Language Server process is running, check if the language server features are working:</p> |
| </div> |
| <div class="olist arabic"> |
| <ol class="arabic"> |
| <li> |
| <p>Open a Java file and use the hover or autocomplete functionality. In case of an erroneous file, the user sees Java in the <strong>Outline</strong> view or in the <strong>Problems</strong> view.</p> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="viewing-java-language-server-log_che"><a class="anchor" href="#viewing-java-language-server-log_che"></a>Viewing the Java language server log</h4> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>The Eclipse JDT Language Server has its own workspace where it logs errors, information about executed commands, and events.</p> |
| </div> |
| <div class="olist arabic"> |
| <ol class="arabic"> |
| <li> |
| <p>To open this log file, open a terminal in the container that is running the Eclipse JDT Language Server plug-in. You can also view the log file by running the <strong>Java: Open Java Language Server log file</strong> command.</p> |
| </li> |
| <li> |
| <p>Run <code>cat <em><PATH_TO_LOG_FILE></em></code> where <code>PATH_TO_LOG_FILE</code> is |
| <code>/home/theia/.theia/workspace-storage/<em><workspace_name></em>/redhat.java/jdt_ws/.metadata/.log</code>.</p> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="logging-the-java-language-server-protocol-lsp-messages_che"><a class="anchor" href="#logging-the-java-language-server-protocol-lsp-messages_che"></a>Logging the Java language server protocol (LSP) messages</h4> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>To log the LSP messages to the Visual Studio Code <strong>Output</strong> view, enable tracing by setting the <code>java.trace.server</code> attribute to <code>verbose</code>.</p> |
| </div> |
| <div class="paragraph"> |
| <div class="title">Additional resources</div> |
| <p>For troubleshooting instructions, see the <a href="https://github.com/redhat-developer/vscode-java">Visual Studio Code Java GitHub repository</a>.</p> |
| </div> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="viewing-logs-for-intelephense_che"><a class="anchor" href="#viewing-logs-for-intelephense_che"></a>Viewing logs for Intelephense</h3> |
| <div class="sect3"> |
| <h4 id="logging-the-intelephense-client-server-communication_che"><a class="anchor" href="#logging-the-intelephense-client-server-communication_che"></a>Logging the Intelephense client-server communication</h4> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>To configure the PHP Intelephense language support to log the client-server communication in the <strong>Output</strong> view:</p> |
| </div> |
| <div class="olist arabic"> |
| <ol class="arabic"> |
| <li> |
| <p>Click <strong>File → Settings</strong>.</p> |
| </li> |
| <li> |
| <p>Open the <strong>Preferences</strong> view.</p> |
| </li> |
| <li> |
| <p>Expand the <strong>Intelephense</strong> section and set the <code>trace.server.verbose</code> preference value to <code>verbose</code> to see all the communication events (the default value is <code>off</code>).</p> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="viewing-intelephense-events-in-the-output-panel_che"><a class="anchor" href="#viewing-intelephense-events-in-the-output-panel_che"></a>Viewing Intelephense events in the Output panel</h4> |
| <div class="paragraph"> |
| <p>This procedure describes how to view Intelephense events in the <strong>Output</strong> panel.</p> |
| </div> |
| <div class="olist arabic"> |
| <div class="title">Procedure</div> |
| <ol class="arabic"> |
| <li> |
| <p>Click <strong>View → Output</strong></p> |
| </li> |
| <li> |
| <p>Select <strong>Intelephense</strong> in the drop-down list for the <strong>Output</strong> view.</p> |
| </li> |
| </ol> |
| </div> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="viewing-logs-for-php-debug_che"><a class="anchor" href="#viewing-logs-for-php-debug_che"></a>Viewing logs for PHP-Debug</h3> |
| <div class="paragraph"> |
| <p>This procedure describes how to configure the PHP Debug plug-in to log the PHP Debug plug-in diagnostic messages into the <strong>Debug Console</strong> view. Configure this before the start of the debug session.</p> |
| </div> |
| <div class="olist arabic"> |
| <div class="title">Procedure</div> |
| <ol class="arabic"> |
| <li> |
| <p>In the <code>launch.json</code> file, add the <code>"log": true</code> attribute to the <code>php</code> configuration.</p> |
| </li> |
| <li> |
| <p>Start the debug session.</p> |
| </li> |
| <li> |
| <p>The diagnostic messages are printed into the <strong>Debug Console</strong> view along with the application output.</p> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="viewing-logs-for-xml_che"><a class="anchor" href="#viewing-logs-for-xml_che"></a>Viewing logs for XML</h3> |
| <div class="paragraph"> |
| <p>Other than the general diagnostics, there are XML plug-in specific actions that the user can perform.</p> |
| </div> |
| <div class="sect3"> |
| <h4 id="verifying-the-state-of-the-xml-language-server_che"><a class="anchor" href="#verifying-the-state-of-the-xml-language-server_che"></a>Verifying the state of the XML language server</h4> |
| <div class="olist arabic"> |
| <div class="title">Procedure</div> |
| <ol class="arabic"> |
| <li> |
| <p>Open a terminal in the container named <code>vscode-xml-<em><xxx></em></code>.</p> |
| </li> |
| <li> |
| <p>Run <code>ps aux | grep java</code> to verify that the XML language server has started. If the process is running, the output is:</p> |
| <div class="listingblock"> |
| <div class="content"> |
| <pre>java ***/org.eclipse.ls4xml-uber.jar`</pre> |
| </div> |
| </div> |
| <div class="paragraph"> |
| <p>If is not, see the <a href="./" class="xref page">Viewing Che workspaces logs</a> chapter.</p> |
| </div> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="checking-xml-language-server-feature-flags_che"><a class="anchor" href="#checking-xml-language-server-feature-flags_che"></a>Checking XML language server feature flags</h4> |
| <div class="olist arabic"> |
| <div class="title">Procedure</div> |
| <ol class="arabic"> |
| <li> |
| <p>Check if the features are enabled. The XML plug-in provides multiple settings that can enable and disable features:</p> |
| <div class="ulist"> |
| <ul> |
| <li> |
| <p><code>xml.format.enabled</code>: Enable the formatter</p> |
| </li> |
| <li> |
| <p><code>xml.validation.enabled</code>: Enable the validation</p> |
| </li> |
| <li> |
| <p><code>xml.documentSymbols.enabled</code>: Enable the document symbols</p> |
| </li> |
| </ul> |
| </div> |
| </li> |
| <li> |
| <p>To diagnose whether the XML language server is working, create a simple XML element, such as <code><hello></hello></code>, and confirm that it appears in the <strong>Outline</strong> panel on the right.</p> |
| </li> |
| <li> |
| <p>If the document symbols do not show, ensure that the <code>xml.documentSymbols.enabled</code> attribute is set to <code>true</code>. If it is <code>true</code>, and there are no symbols, the language server may not be hooked to the editor. If there are document symbols, then the language server is connected to the editor.</p> |
| </li> |
| <li> |
| <p>Ensure that the features that the user needs, are set to <code>true</code> in the settings (they are set to <code>true</code> by default). If any of the features are not working, or not working as expected, file an issue against the |
| <a href="https://github.com/angelozerr/lsp4xml">Language Server</a>.</p> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="enabling-xml-language-server-protocol-lsp-tracing_che"><a class="anchor" href="#enabling-xml-language-server-protocol-lsp-tracing_che"></a>Enabling XML Language Server Protocol (LSP) tracing</h4> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>To log LSP messages to the Visual Studio Code <strong>Output</strong> view, enable tracing by setting the <code>xml.trace.server</code> attribute to <code>verbose</code>.</p> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="viewing-xml-language-server-log_che"><a class="anchor" href="#viewing-xml-language-server-log_che"></a>Viewing the XML language server log</h4> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>The log from the language server can be found in the plug-in sidecar at <code>/home/theia/.theia/workspace-storage/<workspace_name>/redhat.vscode-xml/lsp4xml.log</code>.</p> |
| </div> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="viewing-logs-for-yaml_che"><a class="anchor" href="#viewing-logs-for-yaml_che"></a>Viewing logs for YAML</h3> |
| <div class="paragraph"> |
| <p>This section describes the YAML plug-in specific actions that the user can perform, in addition to the general diagnostics ones.</p> |
| </div> |
| <div class="sect3"> |
| <h4 id="verifying-the-state-of-the-yaml-language-server_che"><a class="anchor" href="#verifying-the-state-of-the-yaml-language-server_che"></a>Verifying the state of the YAML language server</h4> |
| <div class="paragraph"> |
| <p>This section describes how to verify the state of the YAML language server.</p> |
| </div> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>Check if the container running the YAML plug-in is running the YAML language server.</p> |
| </div> |
| <div class="olist arabic"> |
| <ol class="arabic"> |
| <li> |
| <p>In the editor, open a terminal in the container that is running the YAML plug-in (an example name of the container: <code>vscode-yaml-<em><xxx></em></code>).</p> |
| </li> |
| <li> |
| <p>In the terminal, run the <code>ps aux | grep node</code> command. This command searches all the node processes running in the current container.</p> |
| </li> |
| <li> |
| <p>Verify that a command <code>node <strong><strong></strong></strong>**/server.js</code> is running.</p> |
| <div class="imageblock"> |
| <div class="content"> |
| <img src="../_images/logs/verifying-the-state-of-the-yaml-language-server.png" alt="Verifying the state of the YAML language server"> |
| </div> |
| </div> |
| </li> |
| </ol> |
| </div> |
| <div class="paragraph"> |
| <p>The <code>node <strong><strong></strong></strong>**/server.js</code> running in the container indicates that the language server is running. If it is not running, the language server has not started inside the container. In this case, see <a href="./" class="xref page">Viewing Che workspaces logs</a>.</p> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="checking-the-yaml-language-server-feature-flags_che"><a class="anchor" href="#checking-the-yaml-language-server-feature-flags_che"></a>Checking the YAML language server feature flags</h4> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>To check the feature flags:</p> |
| </div> |
| <div class="olist arabic"> |
| <ol class="arabic"> |
| <li> |
| <p>Check if the features are enabled. The YAML plug-in provides multiple settings that can enable and disable features, such as:</p> |
| <div class="ulist"> |
| <ul> |
| <li> |
| <p><code>yaml.format.enable</code>: Enables the formatter</p> |
| </li> |
| <li> |
| <p><code>yaml.validate</code>: Enables validation</p> |
| </li> |
| <li> |
| <p><code>yaml.hover</code>: Enables the hover function</p> |
| </li> |
| <li> |
| <p><code>yaml.completion</code>: Enables the completion function</p> |
| </li> |
| </ul> |
| </div> |
| </li> |
| <li> |
| <p>To check if the plug-in is working, type the simplest YAML, such as <code>hello: world</code>, and then open the <strong>Outline</strong> panel on the right side of the editor.</p> |
| </li> |
| <li> |
| <p>Verify if there are any document symbols. If yes, the language server is connected to the editor.</p> |
| </li> |
| <li> |
| <p>If any feature is not working, verify that the settings listed above are set to <code>true</code> (they are set to <code>true</code> by default). If a feature is not working, file an issue against the <a href="https://github.com/redhat-developer/yaml-language-server">Language Server</a>.</p> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="enabling-yaml-language-server-protocol-lsp-tracing_che"><a class="anchor" href="#enabling-yaml-language-server-protocol-lsp-tracing_che"></a>Enabling YAML Language Server Protocol (LSP) tracing</h4> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>To log LSP messages to the Visual Studio Code <strong>Output</strong> view, enable tracing by setting the <code>yaml.trace.server</code> attribute to <code>verbose</code>.</p> |
| </div> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="viewing-logs-for-dotnet-with-omnisharp-theia-plug-in_che"><a class="anchor" href="#viewing-logs-for-dotnet-with-omnisharp-theia-plug-in_che"></a>Viewing logs for .NET with OmniSharp-Theia plug-in</h3> |
| <div class="sect3"> |
| <h4 id="omnisharp-theia-plug-in_che"><a class="anchor" href="#omnisharp-theia-plug-in_che"></a>OmniSharp-Theia plug-in</h4> |
| <div class="paragraph"> |
| <p>Che uses the OmniSharp-Theia plug-in as a remote plug-in. It is located at |
| <a href="https://github.com/redhat-developer/omnisharp-theia-plugin">github.com/redhat-developer/omnisharp-theia-plugin</a>. In case of an issue, report it, or contribute your fix in the repository.</p> |
| </div> |
| <div class="paragraph"> |
| <p>This plug-in registers <a href="https://github.com/OmniSharp/omnisharp-roslyn">omnisharp-roslyn</a> as a language server and provides project dependencies and language syntax for C# applications.</p> |
| </div> |
| <div class="paragraph"> |
| <p>The language server runs on .NET SDK 2.2.105.</p> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="verifying-the-state-of-the-omnisharp-theia-plug-in-language-server_che"><a class="anchor" href="#verifying-the-state-of-the-omnisharp-theia-plug-in-language-server_che"></a>Verifying the state of the OmniSharp-Theia plug-in language server</h4> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>To check if the container running the OmniSharp-Theia plug-in is running OmniSharp, execute the <code>ps aux | grep OmniSharp.exe</code> command. If the process is running, the following is an example output:</p> |
| </div> |
| <div class="listingblock"> |
| <div class="content"> |
| <pre>/tmp/theia-unpacked/redhat-developer.che-omnisharp-plugin.0.0.1.zcpaqpczwb.omnisharp_theia_plugin.theia/server/bin/mono |
| /tmp/theia-unpacked/redhat-developer.che-omnisharp-plugin.0.0.1.zcpaqpczwb.omnisharp_theia_plugin.theia/server/omnisharp/OmniSharp.exe</pre> |
| </div> |
| </div> |
| <div class="paragraph"> |
| <p>If the output is different, the language server has not started inside the container. Check the logs described in <a href="./" class="xref page">Viewing Che workspaces logs</a>.</p> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="checking-omnisharp-theia-plug-in-language-server-features_che"><a class="anchor" href="#checking-omnisharp-theia-plug-in-language-server-features_che"></a>Checking OmniSharp Che-Theia plug-in language server features</h4> |
| <div class="ulist"> |
| <div class="title">Procedure</div> |
| <ul> |
| <li> |
| <p>If the OmniSharp.exe process is running, check if the language server features are working by opening a <code>.cs</code> file and trying the hover or completion features, or opening the <strong>Problems</strong> or <strong>Outline</strong> view.</p> |
| </li> |
| </ul> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="viewing-omnisharp-theia-plug-in-logs-in-the-output-panel_che"><a class="anchor" href="#viewing-omnisharp-theia-plug-in-logs-in-the-output-panel_che"></a>Viewing OmniSharp-Theia plug-in logs in the Output panel</h4> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>If <code>OmniSharp.exe</code> is running, it logs all information in the <strong>Output</strong> panel. To view the logs, open the <strong>Output</strong> view and select <strong>C#</strong> from the drop-down list.</p> |
| </div> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="viewing-logs-for-dotnet-with-netcoredebugoutput-plug-in_che"><a class="anchor" href="#viewing-logs-for-dotnet-with-netcoredebugoutput-plug-in_che"></a>Viewing logs for .NET with NetcoredebugOutput plug-in</h3> |
| <div class="sect3"> |
| <h4 id="netcoredebugoutput-plug-in_che"><a class="anchor" href="#netcoredebugoutput-plug-in_che"></a>NetcoredebugOutput plug-in</h4> |
| <div class="paragraph"> |
| <p>The NetcoredebugOutput plug-in provides the <a href="https://github.com/Samsung/netcoredbg"><code>netcoredbg</code></a> tool. |
| This tool implements the Visual Studio Code Debug Adapter protocol and allows users to debug .NET applications under the .NET Core runtime.</p> |
| </div> |
| <div class="paragraph"> |
| <p>The container where the NetcoredebugOutput plug-in is running contains .NET SDK v.2.2.105.</p> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="verifying-the-state-of-the-netcoredebugoutput-plug-in_che"><a class="anchor" href="#verifying-the-state-of-the-netcoredebugoutput-plug-in_che"></a>Verifying the state of the NetcoredebugOutput plug-in</h4> |
| <div class="olist arabic"> |
| <div class="title">Procedure</div> |
| <ol class="arabic"> |
| <li> |
| <p>Search for a <code>netcoredbg</code> debug configuration in the <code>launch.json</code> file.</p> |
| <div class="exampleblock"> |
| <div class="title">Example 1. Sample debug configuration</div> |
| <div class="content"> |
| <div class="listingblock"> |
| <div class="content"> |
| <pre class="highlightjs highlight"><code class="language-json hljs" data-lang="json">{ |
| "type": "netcoredbg", |
| "request": "launch", |
| "program": "${workspaceFolder}/bin/Debug/<em><target-framework></em>/<em><project-name.dll></em>", |
| "args": [], |
| "name": ".NET Core Launch (console)", |
| "stopAtEntry": false, |
| "console": "internalConsole" |
| }</code></pre> |
| </div> |
| </div> |
| </div> |
| </div> |
| </li> |
| <li> |
| <p>Test the autocompletion feature within the braces of the <code>configuration</code> section of the <code>launch.json</code> file. If you can find <code>netcoredbg</code>, the Che-Theia plug-in is correctly initialized. If not, see <a href="./" class="xref page">Viewing Che workspaces logs</a>.</p> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="viewing-netcoredebugoutput-plug-in-logs-in-the-output-panel_che"><a class="anchor" href="#viewing-netcoredebugoutput-plug-in-logs-in-the-output-panel_che"></a>Viewing <code>NetcoredebugOutput</code> plug-in logs in the Output panel</h4> |
| <div class="paragraph"> |
| <p>This section describes how to view <code>NetcoredebugOutput</code> plug-in logs in the <strong>Output</strong> panel.</p> |
| </div> |
| <div class="ulist"> |
| <div class="title">Procedure</div> |
| <ul> |
| <li> |
| <p>Open the <strong>Debug</strong> console.</p> |
| <div class="imageblock"> |
| <div class="content"> |
| <img src="../_images/logs/viewing-netcoredebugoutput-plug-in-logs-in-the-output-panel.png" alt="Viewing NetcoredebugOutput plug-in logs in the *Output* panel"> |
| </div> |
| </div> |
| </li> |
| </ul> |
| </div> |
| </div> |
| </div> |
| <div class="sect2"> |
| <h3 id="viewing-logs-for-camel_che"><a class="anchor" href="#viewing-logs-for-camel_che"></a>Viewing logs for Camel</h3> |
| <div class="sect3"> |
| <h4 id="verifying-the-state-of-the-camel-language-server_che"><a class="anchor" href="#verifying-the-state-of-the-camel-language-server_che"></a>Verifying the state of the Camel language server</h4> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>The user can inspect the log output of the sidecar container using the Camel language tools that are stored in the <code>vscode-apache-camel<em><xxx></em></code> Camel container.</p> |
| </div> |
| <div class="paragraph"> |
| <p>To verify the state of the language server:</p> |
| </div> |
| <div class="olist arabic"> |
| <ol class="arabic"> |
| <li> |
| <p>Open a terminal inside the <code>vscode-apache-camel<em><xxx></em></code> container.</p> |
| </li> |
| <li> |
| <p>Run the <code>ps aux | grep java</code> command. The following is an example language server process:</p> |
| <div class="listingblock"> |
| <div class="content"> |
| <pre>java -jar /tmp/vscode-unpacked/camel-tooling.vscode-apache-camel.latest.euqhbmepxd.camel-tooling.vscode-apache-camel-0.0.14.vsix/extension/jars/language-server.jar</pre> |
| </div> |
| </div> |
| </li> |
| <li> |
| <p>If you cannot find it, see <a href="./" class="xref page">Viewing Che workspaces logs</a>.</p> |
| </li> |
| </ol> |
| </div> |
| </div> |
| <div class="sect3"> |
| <h4 id="viewing-camel-logs-in-the-output-panel_che"><a class="anchor" href="#viewing-camel-logs-in-the-output-panel_che"></a>Viewing Camel logs in the Output panel</h4> |
| <div class="paragraph"> |
| <p>The Camel language server is a SpringBoot application that writes its log to the <code>$\{java.io.tmpdir}/log-camel-lsp.out</code> file. Typically, <code>$\{java.io.tmpdir}</code> points to the <code>/tmp</code> directory, so the filename is <code>/tmp/log-camel-lsp.out</code>.</p> |
| </div> |
| <div class="paragraph"> |
| <div class="title">Procedure</div> |
| <p>The Camel language server logs are printed in the <strong>Output</strong> channel named <strong>Language Support for Apache Camel</strong>.</p> |
| </div> |
| <div class="admonitionblock note"> |
| <table> |
| <tr> |
| <td class="icon"> |
| <i class="fa icon-note" title="Note"></i> |
| </td> |
| <td class="content"> |
| The output channel is created only at the first created log entry on the client side. It may be absent when everything is going well. |
| </td> |
| </tr> |
| </table> |
| </div> |
| <div class="imageblock"> |
| <div class="content"> |
| <a class="image" href="../_images/logs/viewing-camel-logs-in-the-output-panel.png"><img src="../_images/logs/viewing-camel-logs-in-the-output-panel.png" alt="viewing camel logs in the output panel"></a> |
| </div> |
| </div> |
| </div> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2 id="viewing-che-theia-ide-logs_che"><a class="anchor" href="#viewing-che-theia-ide-logs_che"></a>Viewing Che-Theia IDE logs</h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>This section describes how to view Che-Theia IDE logs.</p> |
| </div> |
| <div class="sect2"> |
| <h3 id="viewing-che-theia-ide-logs-on-the-cli_che"><a class="anchor" href="#viewing-che-theia-ide-logs-on-the-cli_che"></a>Viewing Che-Theia editor logs using the OpenShift CLI</h3> |
| <div class="paragraph"> |
| <p>Observing Che-Theia editor logs helps to get a better understanding and insight over the plug-ins loaded by the editor. This section describes how to access the Che-Theia editor logs using the OpenShift CLI (command-line interface).</p> |
| </div> |
| <div class="ulist"> |
| <div class="title">Prerequisites</div> |
| <ul> |
| <li> |
| <p>Che is deployed in an OpenShift cluster.</p> |
| </li> |
| <li> |
| <p>A workspace is created.</p> |
| </li> |
| <li> |
| <p>User is located in a Che installation namespace.</p> |
| </li> |
| </ul> |
| </div> |
| <div class="olist arabic"> |
| <div class="title">Procedure</div> |
| <ol class="arabic"> |
| <li> |
| <p>Obtain the list of the available Pods:</p> |
| <div class="listingblock"> |
| <div class="content"> |
| <pre>$ oc get pods</pre> |
| </div> |
| </div> |
| <div class="listingblock white-space-pre"> |
| <div class="title">Example</div> |
| <div class="content"> |
| <pre class="nowrap">$ oc get pods |
| NAME READY STATUS RESTARTS AGE |
| che-9-xz6g8 1/1 Running 1 15h |
| workspace0zqb2ew3py4srthh.go-cli-549cdcf69-9n4w2 4/4 Running 0 1h</pre> |
| </div> |
| </div> |
| </li> |
| <li> |
| <p>Obtain the list of the available containers in the particular Pod:</p> |
| <div class="listingblock white-space-pre"> |
| <div class="content"> |
| <pre class="nowrap">$ oc get pods <em><name-of-pod></em> --output jsonpath='\{.spec.containers[*].name}'</pre> |
| </div> |
| </div> |
| <div class="listingblock white-space-pre"> |
| <div class="title">Example:</div> |
| <div class="content"> |
| <pre class="nowrap">$ oc get pods workspace0zqb2ew3py4srthh.go-cli-549cdcf69-9n4w2 -o |
| jsonpath='\{.spec.containers[*].name}' |
| > go-cli che-machine-exechr7 theia-idexzb vscode-gox3r</pre> |
| </div> |
| </div> |
| </li> |
| <li> |
| <p>Get logs from the <code>theia/ide</code> container:</p> |
| <div class="listingblock"> |
| <div class="content"> |
| <pre>$ oc logs --follow <em><name-of-pod></em> --container <em><name-of-container></em></pre> |
| </div> |
| </div> |
| <div class="listingblock white-space-pre"> |
| <div class="title">Example:</div> |
| <div class="content"> |
| <pre class="nowrap">$ oc logs --follow workspace0zqb2ew3py4srthh.go-cli-549cdcf69-9n4w2 -container |
| theia-idexzb |
| >root INFO unzipping the plug-in 'task_plugin.theia' to directory: /tmp/theia-unpacked/task_plugin.theia |
| root INFO unzipping the plug-in 'theia_yeoman_plugin.theia' to directory: /tmp/theia-unpacked/theia_yeoman_plugin.theia |
| root WARN A handler with prefix term is already registered. |
| root INFO [nsfw-watcher: 75] Started watching: /home/theia/.theia |
| root WARN e.onStart is slow, took: 367.4600000013015 ms |
| root INFO [nsfw-watcher: 75] Started watching: /projects |
| root INFO [nsfw-watcher: 75] Started watching: /projects/.theia/tasks.json |
| root INFO [4f9590c5-e1c5-40d1-b9f8-ec31ec3bdac5] Sync of 9 plugins took: 62.26000000242493 ms |
| root INFO [nsfw-watcher: 75] Started watching: /projects |
| root INFO [hosted-plugin: 88] PLUGIN_HOST(88) starting instance</pre> |
| </div> |
| </div> |
| </li> |
| </ol> |
| </div> |
| </div> |
| </div> |
| </div> |
| </article> |
| </div> |
| </main> |
| </div> |
| <footer class="footer"> |
| <div> |
| <a href="https://www.eclipse.org/che/sitemap.xml" target="_blank">Site Map</a> | |
| <a href="https://www.eclipse.org" target="_blank">Eclipse Foundation</a> | |
| <a href="https://www.eclipse.org/legal/privacy.php" target="_blank">Privacy Policy</a> | |
| <a href="https://www.eclipse.org/legal/termsofuse.php" target="_blank">Terms of Use</a> | |
| <a href="https://www.eclipse.org/legal/epl-2.0/" target="_blank">Eclipse Public License</a> | |
| <a href="https://www.eclipse.org/legal" target="_blank">Legal Resources</a></div> |
| </footer> |
| |
| <script src="../../../../docs/_/js/site.js"></script> |
| <script async src="../../../../docs/_/js/vendor/highlight.js"></script> |
| <script src="../../../../docs/_/js/vendor/lunr.js"></script> |
| <script src="../../../../docs/_/js/search-ui.js" id="search-ui-script" data-site-root-path="../../../.." data-snippet-length="142" data-stylesheet="../../../../docs/_/css/search.css"></script> |
| <script async src="../../../../search-index.js"></script> |
| </body> |
| </html> |
