Advanced Workspace Troubleshooting

There are times that a workspace can fail to load because it crashes shortly after launch.

From the user’s perspective launching a workspace would seem to work correctly, but end in returning the user to the user dashboard.

From the kasm administrators perspective you might see error logs referring to the container or workspace is “is restarting, wait until the container is running".

To diagnose the root cause of this error you can enable the advanced feature "container logging" which will redirect all logs generated by the container to Kasm Workspaces.

To use this feature:

1. Ensure that enable_container_logging in is set to True in the Group Settings.

2. Launch a workspace.

3. View the container logs in the Kasm UI by filtering the Host field using the Session ID.

warning

Note that enabling this group setting will cause the container sessions to be logged for all sessions started by users in that group, and may impact performance due to the high number of log messages generated.