Hey there, We are conducting a poc on Cloudstack (v4.19.1 with KVM) and are encountering a problem getting the console to work.
Indeed it seems to work but we have a stuck screen with the bios display at boot while the VM is started. The displayed VM UUID matches the actual VM UUID. Attached a screenshot [cid:image001.png@01DAAB90.C1999880] No errors and no activity on websocket: [cid:image003.png@01DAAB95.4D0AA130] We checked the logs on the management and proxy console side, but everything seems normal except a warning concerning an unknown parameter (client-inet-address) [MGMT Server] May 21 13:20:34 acsp-olps-mgmt-02 java[1268950]: WARN [c.c.a.d.ParamGenericValidationWorker] (qtp239372207-954:ctx-a8487ad8 ctx-74e86abc ctx-6ff9c49d) (logid:14d5c24b) Received unknown parameters for command createConsoleEndpoint. Unknown parameters : client-inet-address May 21 13:20:34 acsp-olps-mgmt-02 java[1268950]: INFO [o.a.c.c.ConsoleAccessManagerImpl] (qtp239372207-954:ctx-a8487ad8 ctx-74e86abc ctx-6ff9c49d) (logid:14d5c24b) Parse host info returned from executing GetVNCPortCommand. host info: 10.0.X.X When I check apiserver.log, the token is the same in my URL's browser. [CPVM] 2024-05-21 13:20:35,606 INFO [cloud.consoleproxy.ConsoleProxyNoVNCHandler] (qtp1218168479-40:null) Get websocket connection request from remote IP : 82.X.X.X 2024-05-21 13:20:35,683 INFO [cloud.consoleproxy.ConsoleProxyNoVncClient] (Thread-1113:null) Connect to VNC server directly. host: 10.0.X.X, port: 5902 2024-05-21 13:20:35,683 INFO [consoleproxy.vnc.NoVncClient] (Thread-1113:null) Connecting to VNC server 10.0.X.X:5902 ... 2024-05-21 13:20:35,717 INFO [vnc.security.VncTLSSecurity] (Thread-1113:null) Processing VNC TLS security 2024-05-21 13:20:35,717 INFO [utils.nio.Link] (Thread-1113:null) Conf file found: /usr/local/cloud/systemvm/conf/agent.properties 2024-05-21 13:20:35,810 INFO [vnc.security.VncAuthSecurity] (Thread-1113:null) VNC server requires password authentication 2024-05-21 13:20:35,817 INFO [vnc.security.VncAuthSecurity] (Thread-1113:null) Finished VNCAuth security Sometimes we have timeout errors on the websocket but I think this is the consequence of closing my console window in my browser. 2024-05-21 13:21:17,942 INFO [cloud.consoleproxy.ConsoleProxyNoVncClient] (Thread-1111:null) Connection with client [7] is dead. 2024-05-21 13:23:38,761 INFO [cloud.consoleproxy.ConsoleProxyGCThread] (Console Proxy GC Thread:null) Dropping com.cloud.consoleproxy.ConsoleProxyNoVncClient@1e5b1305<mailto:com.cloud.consoleproxy.ConsoleProxyNoVncClient@1e5b1305> which has not been used for 182 seconds 2024-05-21 13:25:35,969 ERROR [cloud.consoleproxy.ConsoleProxyNoVNCHandler] (Connector-Scheduler-6940fda3-1:null) Error on websocket org.eclipse.jetty.websocket.api.CloseException: java.util.concurrent.TimeoutException: Idle timeout expired: 300001/300000 ms We verified the time and date between the CPVM and the MGMT servers. It's OK. (UTC Time) We use SSL for the Proxy console. The flows are open on the CPVM public network on port 8443 (websocket) (From my home network) telnet 154.49.x.x 8443 Trying 154.49.x.x... Connected to 154.49.x.x. Escape character is '^]'. ^[quit PConnection closed by foreign host. The flow is also open between the MGMT servers and the CPVM on port 8001. Moreover, we tried a tcpdump on this port (8001 - MGMT Iface)) but we did not see any packets. We observe an open socket between the proxy console and the physical server on the VNC port of the VM in question. (A telnet test returns the connection) root@v-377-VM:~# telnet 10.0.x.x 5902 Trying 10.0.x.x... Connected to 10.0.x.x. Escape character is '^]'. RFB 003.008 quit ^C^CConnection closed by foreign host. I tried to trace some logs in libvirt concerning the VNC part but found nothing or a lot of logs with QEmu. (Nothing revealant) SSL Certs have been correctly provisioned on libvirt for each compute by cloudstack (trying to regenerate them, and restart CPVM many times) So, we think the console is working but the stream between VNC Server and end user is dead. Please, can you give us a way to solve this problem? We start to dry. Best regards, Have a nice day, Maxime PAYET C1-Internal Use
