Furthermore, on the management server side the following messages exist in the logs: WARN [c.c.a.d.ParamGenericValidationWorker] (qtp1637207591-343:ctx-79672d38 ctx-0d2376ce) (logid:b4beffac) Received unknown parameters for command createConsoleEndpoint. Unknown parameters : client-inet-address INFO [o.a.c.c.ConsoleAccessManagerImpl] (qtp1637207591-343:ctx-79672d38 ctx-0d2376ce) (logid:b4beffac) Parse host info returned from executing GetVNCPortCommand. host info: 172.31.255.211 WARN [c.c.a.m.AgentManagerImpl] (qtp1637207591-343:ctx-79672d38 ctx-0d2376ce) (logid:b4beffac) Unsupported Command: Unsupported command issued: com.cloud.agent.api.BadCommand. Are you sure you got the right type of server? ERROR [c.c.c.AgentHookBase] (AgentManager-Handler-3:null) (logid:) Invalid session, only one session allowed per token
On Thu, Oct 13, 2022 at 6:57 PM Curious Pandora <p4nd...@gmail.com> wrote: > Hello, > > running a clean install on current 4.18 tree looks like something is not > working in consoleproxy. > (noVNC and classic as well) > > An identical 4.17 environment works fine. > > From Working Env, Consoleproxy cloud.log snips > -------------------------------------------------------------------------- > 2022-10-13 14:38:45,249 INFO > [cloud.consoleproxy.ConsoleProxyNoVNCHandler] (qtp1954606578-43:null) Get > websocket connection request from remote IP : 10.8.80.3 > 2022-10-13 14:38:45,272 INFO [cloud.consoleproxy.ConsoleProxyNoVncClient] > (Thread-105:null) Connect to VNC server directly. host: 172.31.255.12, > port: 5901 > 2022-10-13 14:38:45,276 INFO [consoleproxy.vnc.NoVncClient] > (Thread-105:null) Connecting to VNC server 172.31.255.12:5901... > 2022-10-13 14:38:45,465 INFO [consoleproxy.vnc.NoVncClient] > (Thread-105:null) VNC server requires password authentication > 2022-10-13 15:29:00,863 INFO > [cloud.consoleproxy.ConsoleProxyNoVNCHandler] (qtp1954606578-43:null) Get > websocket connection request from remote IP : 10.8.80.3 > 2022-10-13 15:29:00,931 INFO [cloud.consoleproxy.ConsoleProxyNoVncClient] > (Thread-110:null) Connect to VNC server directly. host: 172.31.255.12, > port: 5901 > 2022-10-13 15:29:00,937 INFO [consoleproxy.vnc.NoVncClient] > (Thread-110:null) Connecting to VNC server 172.31.255.12:5901... > 2022-10-13 15:29:01,148 INFO [consoleproxy.vnc.NoVncClient] > (Thread-110:null) VNC server requires password authentication > > > From 4.18 Dev Env, Consoleproxy cloud.log snips > --------------------------------------------------------------------------- > 2022-10-13 15:54:40,966 INFO > [cloud.consoleproxy.ConsoleProxyNoVNCHandler] (qtp1810267116-38:null) Get > websocket connection request from remote IP : 10.8.80.3 > 2022-10-13 15:54:41,017 WARN [cloud.consoleproxy.ConsoleProxy] > (qtp1810267116-38:null) External authenticator failed authentication > request for vm d59c31a5-e4c8-454f-a9ff-432bc8910fcb with sid > 7lXWphOeekTsH0G6x3xWVQ > 2022-10-13 15:54:41,024 WARN > [cloud.consoleproxy.ConsoleProxyNoVNCHandler] (qtp1810267116-38:null) > Failed to create viewer due to External authenticator failed request for vm > d59c31a5-e4c8-454f-a9ff-432bc8910fcb with sid 7lXWphOeekTsH0G6x3xWVQ > com.cloud.consoleproxy.AuthenticationException: External authenticator > failed request for vm d59c31a5-e4c8-454f-a9ff-432bc8910fcb with sid > 7lXWphOeekTsH0G6x3xWVQ > > Note that for some reason the 4.18 uses External authenticator. > > The networking for both environments is exactly the same. > > Can someone verify ? > > Regards > > -- > p4nd0ra - the curious > -- p4nd0ra - the curious
