![]() Here you can see that both the kasm_agent and kasm_proxy containers are up and healthy. The first thing to verify if you have an agent that is not reporting in to Kasm Workspaces is to verify that the agent is powered on and that the Kasm agent container is running on the agent.Īfter verifying that the agent is powered on, ssh into the agent and from the command line run sudo docker ps to verify the Kasm agent docker container is running. The Docker Agent Table has a Column Displaying the Last Reported Time In the screenshot below you can see one agent that has not reported for more than 3 days. The heartbeat interval of an agent is configurable in the agent config (in milliseconds) /opt/kasm/current/config/app/. The table on the Docker Agents page in the admin UI also displays a column for the last time the agent reported in to Kasm Workspaces. If all the agents that are supposed to be enabled are enabled, then it may be a communication problem. The Docker Agent Table has a Column Displaying the Enabled Status After enabling an agent that agent might require some time to download the latest images. NOTE: Agents that are disabled will not download new images until re-enabled. The table below shows both an enabled and a disabled agent. Enable the agents and try again after a few minutes. If agents are listed as disabled that should be enabled that may be the reason for the No Resources Available error. There is a column in the table that displays if the agent is enabled or not. ![]() In the admin UI select Compute and then select Docker Agents this will display a table of all agents registered with the system. It’s possible the admin has created enough docker agents, but not all of them are enabled. Before proceeding with troubleshooting this video provides and overview on resource allocation within Kasm Workspaces: Checking That the Agents Are Online This error has several possible causes, the most common ones are covered below. Security Group Example No Resources Available This is done by creating an additional rule to the security group allowing https connections from the same security group. (the source IP is not “0.0.0.0/0”), then an additional rule must be added to allow the server to connect to itself. If the security group rule in the AWS / Azure / OCI console that allows https into the Web App restricts connections by IP address The Agent Doesn’t Have the Image Requested.Session Hangs at “Creating a secure connection”.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |