-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
seeking to understand how to debug remote agent further - "No Agent slots available" / "No resources are available" #653
Comments
The following line is misleading
It just means that the provisioning loop stopped making 'slots' on that server because it has no more cores to make empty slots from. It is meant to help you identify what was the limiting factor on the server for creating empty slots. It could have also stopped due to RAM or GPUs. Something is wrong on the following two lines, there should be values none
I suspect your agent does not belong to a Zone. Can you validate that your agent belongs to a zone and if it does, what is the Zone name? |
Can you provide logs from your working agent and manager? |
api logs for successful terminal session open on the single_server agent implementation herein :
for clarity this is the same manager (from failing external-agent example) talking to agent on itself |
Existing Resources
Describe the bug
Maybe misleading messaging??? anyhow when I try to start a workspace/terminal I get back a "no resources are available" in the UI.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A terminal session starts in browser
Screenshots
.
Workspaces Version
e.g Version 1.16
Workspaces Installation Method
manager was installed as single server (initial PoC) but has local agent (which works fine) currently disabled
Agent has been installed following the Multi-Server agent install process (though in a slightly non-standard way in DinD)
Client Browser (please complete the following information):
Workspace Server Information (please provide the output of the following commands):
uname -a
cat /etc/os-release
sudo docker info
sudo docker ps | grep kasm
Additional context
Several things of note.
docker logs -f
like
2024-11-14 23:35:00,818 [WARNING] tornado.access: 404 GET /test_path_to_agent (172.19.0.3) 0.31ms
Some Questions relating to the above logs
No more slots available for server : (f1682ddf-4a10-4e06-bc62-ab655f31d341)
. is this correct?slots
, are these only abstractions on the management host side of how many sessions can be created on the agent side before resources are exhausted?no resources available
to understand what, specifically, Kasm thinks is not available that is required on the agent side, when the screenshot (supported by validation on the agent side) indicates plenty of resource?The text was updated successfully, but these errors were encountered: