search

kasmtech / workspaces-issues

19 stars 4 forks source link

[Bug] - Cannot update hostnames error in logs after import #510

Open elproducto opened 8 months ago

elproducto commented 8 months ago

Existing Resources

Describe the bug Imported KASM config from a prior host into a new host. Post import I am unable to start any existing workspaces, or install a new one. It appears images have not been download. I am getting the following error in the console. The the install is having issue updating hostnames. Not sure what setting to tweak. Docker agents has a green checkmark above enabled, even thought hostname is proxy. I removed the old manager as the new manager(host) appears, but it shows "-" above agents. Thanks for creating Kasmweb, and let me know if any additional information is required

host: kasm01
ingest_date: 202402022027
application: connection_proxy
levelname: ERROR
message
[server] Cannot update hostnames. Failed to authorize session (https://proxy:443/api/guac_get_managers). Connection Proxy by id (6a4f4f75-15ad-4a04-a5c0-9ad69f2a2d13) not found

To Reproduce Steps to reproduce the behavior:

  1. Export setting from an existing single servers install
  2. Setup new single server install on VM
  3. import prior export setting
  4. check Logging for error around Cannot update hostnames

Expected behavior Import working as it was prior

Workspaces Version Version 1.14.0.32d10f

Workspaces Installation Method Single Server

Client Browser (please complete the following information):

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

Server: Containers: 8 Running: 8 Paused: 0 Stopped: 0 Images: 8 Server Version: 25.0.2 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: systemd Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb runc version: v1.1.12-0-g51d5e94 init version: de40ad0 Security Options: apparmor seccomp Profile: builtin cgroupns Kernel Version: 5.10.0-27-cloud-amd64 Operating System: Debian GNU/Linux 11 (bullseye) OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 1.938GiB Name: kasm01 ID: f9170242-bc49-4614-b94d-d048cc0445f5 Docker Root Dir: /var/lib/docker Debug Mode: false Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false

 - `sudo docker ps | grep kasm`

f6b494d0a700 kasmweb/nginx:1.25.1 "/docker-entrypoint.…" 15 hours ago Up 20 minutes 80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp kasm_proxy 8b71a8364314 kasmweb/share:1.14.0 "/bin/sh -c '/usr/bi…" 15 hours ago Up 20 minutes (healthy) 8182/tcp kasm_share 61c526961743 kasmweb/agent:1.14.0 "/bin/sh -c '/usr/bi…" 15 hours ago Up 20 minutes (healthy) 4444/tcp kasm_agent c2d5459330db kasmweb/manager:1.14.0 "/bin/sh -c '/usr/bi…" 15 hours ago Up 20 minutes (healthy) 8181/tcp kasm_manager b91c1d6528b1 kasmweb/kasm-guac:1.14.0 "/dockerentrypoint.sh" 15 hours ago Up 20 minutes (healthy) kasm_guac 64a32d7e1d3f kasmweb/api:1.14.0 "/bin/sh -c '/usr/bi…" 15 hours ago Up 20 minutes (healthy) 8080/tcp kasm_api 5871be024492 redis:5-alpine "docker-entrypoint.s…" 15 hours ago Up 20 minutes 6379/tcp kasm_redis c1663c5c7d77 postgres:12-alpine "docker-entrypoint.s…" 15 hours ago Up 20 minutes (healthy) 5432/tcp kasm_db

Majoraslayer commented 4 months ago

I have the same issue, were you ever able to find a solution for this?