Skip to main content
Version: Developer

Troubleshoot workspaces that crash after launch in Kasm

Overview​

A workspace can fail to load when its container crashes shortly after launch. Users see the launch begin and then return to the user dashboard without an active session. Administrators see error logs that report the container is restarting or to wait until the container is running. This guide enables container logging so you can capture the container output and diagnose the root cause.

Prerequisites​

  • Administrator access to the Kasm Workspaces UI.
  • Permission to edit the Group Settings for the affected group.

Enable container logging​

Container logging redirects all logs generated by the workspace container to Kasm Workspaces. The redirected logs reveal why the container exits after launch.

  1. Set enable_container_logging to True in the Group Settings.

  2. Launch a workspace.

  3. View the container logs in the Kasm UI. Filter the Host field by the workspace Session ID.

warning

This group setting logs the container sessions for every session started by users in that group. The high volume of log messages can degrade performance.