[Bug] - kasm_guac - unhealthy - ERROR guac [server] Healthcheck failed

[fanuelsen]

Existing Resources

• [X] Please search the existing issues for related problems
• [X] Consult the product documentation : Docs
• [X] Consult the FAQ : FAQ
• [X] Consult the Troubleshooting Guide : Guide
• [X] Reviewed existing training videos: Youtube

Describe the bug After upgrading kasm (from 1.11 to 1.15) with the autoupgrade script the kasm_guac container is unhealthy. Workspaces is still working so i'm not sure what guac_server is used for. But the following output is inside the kasm_guac container.

2024-06-05 09:05:43,516 INFO guac [server] Registering kasm_guac with configuration: { "target_component": { "type": "connection_proxy", "server_address": "proxy", "server_port": 443, "zone_name": "default" }, "registration_token": "**********", "token": "JWTTOKEN" } 2024-06-05 09:05:43,516 INFO guac [server] Attempt 1/10 attempts 2024-06-05 09:05:43,850 ERROR guac [server] Healthcheck failed for "proxy". Error: Request failed with status code 502 2024-06-05 09:05:43,858 ERROR guac [server] Healthcheck failed for "kasm_proxy". Error: Request failed with status code 502 2024-06-05 09:05:45,861 INFO guac [server] Attempt 2/10 attempts ComponentRegistrationError: Access Denied! at Object.registerWithDeployment (/gclient/kasm.js:81:15) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async run (/gclient/server.js:242:5) at async run (/gclient/app.js:12:5)

Expected behavior Should start as expected.

Workspaces Version Version 1.15

Workspaces Installation Method Single Server

Workspace Server Information (please provide the output of the following commands):

• 5.4.0-42-generic #46-Ubuntu SMP
• VERSION="20.04.6 LTS (Focal Fossa)
• Client: Docker Engine - Community Version: 26.1.3
• 9b4ab264c7b0 kasmweb/nginx:1.25.3 "/docker-entrypoint.…" 2 hours ago Up 55 minutes 80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp kasm_proxy cae8635b7258 kasmweb/agent:1.15.0 "/bin/sh -c '/usr/bi…" 2 hours ago Up 55 minutes (healthy) 4444/tcp kasm_agent 5fff30b34f64 kasmweb/share:1.15.0 "/bin/sh -c '/usr/bi…" 2 hours ago Up 55 minutes (healthy) 8182/tcp kasm_share e4b2fdabc794 kasmweb/api:1.15.0 "/bin/sh -c '/usr/bi…" 2 hours ago Up 55 minutes (healthy) 8080/tcp kasm_api 1112348b6ac7 kasmweb/manager:1.15.0 "/bin/sh -c '/usr/bi…" 2 hours ago Up 55 minutes (healthy) 8181/tcp kasm_manager fe096764df08 redis:5-alpine "docker-entrypoint.s…" 2 hours ago Up 55 minutes 6379/tcp kasm_redis 148b1af31d19 postgres:12-alpine "docker-entrypoint.s…" 2 hours ago Up 55 minutes (healthy) 5432/tcp kasm_db 7ea50101632d kasmweb/kasm-guac:1.15.0 "/dockerentrypoint.sh" 2 hours ago Up 55 minutes (unhealthy) kasm_guac

[j-travis]

The kasm_guac role is used when you want to connect to existing systems over RDP , SSH, or VNC. You can try following this guide - the portions that refer to restoring the guac connection proxy.

That may clear your environment up.

https://kasmweb.atlassian.net/servicedesk/customer/kb/view/8126468

I recommend taking a backup before you do in case you need to restore

[octave21]

I experienced a similar issue with the 1.16 version. It works fine when I first install it. When I turn the server off and on again, the kasm_guac starts but goes unhealthy within 2 minutes.

Sometimes in case of heavy load of the server, the kasm_guac goes unhealthy or restarts again and again.