: Re: NoVNC failed to connect
Hi Ian,
Is this a fresh installation or upgraded from an older version ? Can you
destroy the CPVM and retry ?
-Wei
On Tue, 13 Jun 2023 at 12:41, Ian Tobin wrote:
> Hi Wei,
>
> Is there anything you could suggest? We could rebuild everything but
>
ort, however this isn’t production so can be done.
>
> Thanks
>
> Ian
>
>
>
>
> -Original Message-
> From: Wei ZHOU
> Sent: 12 June 2023 22:35
> To: users@cloudstack.apache.org
> Subject: Re: NoVNC failed to connect
>
> It looks the issue is cause
8: {
> Ans: , MgmtId: 217952330057572, via: 10, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.ConsoleAccessAuthenticationAnswer":{"_success":
> "false","_isReauthenticating":"false","_port":"0","result":"true
via: 10, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.ConsoleAccessAuthenticationAnswer":{"_success":"false","_isReauthenticating":"false","_port":"0","result":"true","wait":"0","bypassHostMaintenance&q
t;:"false"}}]
}
2023-06-12 19:53:03,302 DEBUG [o.a.c.h.HAManagerImpl]
(BackgroundTaskPollManager-1:ctx-bca8ab90) (logid:e408e339) HA health check
task is running...
2023-06-12 19:53:05,638 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) (logid:) SeqA 10-549: Processi
dd request for vm
> > 90faddb0-b512-4aff-9738-084b3eecc3af with sid
> > HVaYsT4NZY2UTkt4V00
> > v2Jw
> > com.cloud.consoleproxy.AuthenticationException: External authenticator
> > failed ree quest for vm 90faddb0-b512-4aff-9738-084b3eecc3af with sid
> &g
you think this is a time sync issue?
Thanks
Ian
-Original Message-
From: Wei ZHOU
Sent: 11 June 2023 19:10
To: users@cloudstack.apache.org
Subject: Re: NoVNC failed to connect
Yes, it could be relevant.
Can you check if cpvm is time-synced with the management server ? If yes
ost.
> > root@v-26-VM:/etc# telnet 192.168.0.34 5901
> > Trying 192.168.0.34...
> > Connected to 192.168.0.34.
> > Escape character is '^]'.
> > RFB 003.008
> >
> > Thanks
> >
> > Ian
> >
> >
> >
> > -Original Me
@cloudstack.apache.org
Subject: Re: NoVNC failed to connect
All looks good.
Can you check /var/log/cloud.log in cpvm if there are some errors ?
On Sunday, 11 June 2023, Ian Tobin wrote:
> Hi Wei,
>
> This is the output from consoleproxy
>
> root@v-26-VM:/etc# telnet 192.168.0
>
>
> -Original Message-
> From: Wei ZHOU
> Sent: 10 June 2023 16:19
> To: users@cloudstack.apache.org
> Subject: Re: NoVNC failed to connect
>
> Hi,
>
> Can you check in the console proxy vm if the vnc ports are reachable ?
>
> telnet 192.168.0.34 59
to 192.168.0.34.
Escape character is '^]'.
RFB 003.008
Thanks
Ian
-Original Message-
From: Wei ZHOU
Sent: 10 June 2023 16:19
To: users@cloudstack.apache.org
Subject: Re: NoVNC failed to connect
Hi,
Can you check in the console proxy vm if the vnc ports are reachable ?
telnet
0 192.168.0.34:47868 192.168.0.33:8250
> ESTABLISHED
>
>
>
> thanks
>
> Ian
>
>
> -----Original Message-----
> From: Wei ZHOU
> Sent: 10 June 2023 10:39
> To: users@cloudstack.apache.org
> Subject: Re: NoVNC failed to connect
>
> Just noticed you r
192.168.0.34:47868 192.168.0.33:8250 ESTABLISHED
thanks
Ian
-Original Message-
From: Wei ZHOU
Sent: 10 June 2023 10:39
To: users@cloudstack.apache.org
Subject: Re: NoVNC failed to connect
Just noticed you run the commands in consoleproxy vm.
Can you please run same commands
just destroyed it and
> let it re create but the netstat shows there is no VNC ports running.
>
> Thanks
>
> Ian
>
>
> -Original Message-
> From: Wei ZHOU
> Sent: 10 June 2023 06:50
> To: users@cloudstack.apache.org
> Subject: Re: NoVNC failed to connect
>
&g
@cloudstack.apache.org
Subject: Re: NoVNC failed to connect
Hi,
What OS do you use?
Normally you can find the ports listened on 5900/5901/... which are vnc ports
of vms.
-Wei
On Fri, 9 Jun 2023 at 23:40, Ian Tobin wrote:
> Hi Wei,
>
> Sorry for the delay in coming back.
>
LISTEN
> tcp0 0 192.168.0.203:36154 192.168.0.33:8250
> ESTABLISHED
>
> thanks
>
> Ian
>
>
>
>
> -Original Message-
> From: Wei ZHOU
> Sent: 07 June 2023 16:33
> To: users@cloudstack.apache.org
> Subject: Re: NoVNC failed to conne
:80010.0.0.0:* LISTEN
tcp0 0 192.168.0.203:36154 192.168.0.33:8250 ESTABLISHED
thanks
Ian
-Original Message-
From: Wei ZHOU
Sent: 07 June 2023 16:33
To: users@cloudstack.apache.org
Subject: Re: NoVNC failed to connect
The default
the password in the UI, unless im
> missing something?
>
> Thanks
>
> Ian
>
>
>
> -Original Message-
> From: Ian Tobin
> Sent: 07 June 2023 13:06
> To: users@cloudstack.apache.org
> Subject: RE: NoVNC failed to connect
>
> Hi Wei,
>
Subject: RE: NoVNC failed to connect
Hi Wei,
Thanks for the info, ill connect and report back.
Thanks
Ian
-Original Message-
From: Wei ZHOU
Sent: 07 June 2023 13:04
To: users@cloudstack.apache.org
Subject: Re: NoVNC failed to connect
Hi Ian,
You can access the system vm via
Hi Wei,
Thanks for the info, ill connect and report back.
Thanks
Ian
-Original Message-
From: Wei ZHOU
Sent: 07 June 2023 13:04
To: users@cloudstack.apache.org
Subject: Re: NoVNC failed to connect
Hi Ian,
You can access the system vm via "virsh console" on th
iginal Message-
> From: Wei ZHOU
> Sent: 07 June 2023 12:21
> To: users@cloudstack.apache.org
> Subject: Re: NoVNC failed to connect
>
> Hi Ian,
>
> Can you log into the console proxy vm, and check if the vnc port of (any)
> vm is reachable ?
> You can get the vnc port by comm
2023 12:21
To: users@cloudstack.apache.org
Subject: Re: NoVNC failed to connect
Hi Ian,
Can you log into the console proxy vm, and check if the vnc port of (any) vm is
reachable ?
You can get the vnc port by command "virsh domdisplay" or "virsh vncdisplay" on
the kvm host.
Hi Ian,
Can you log into the console proxy vm, and check if the vnc port of (any)
vm is reachable ?
You can get the vnc port by command "virsh domdisplay" or "virsh
vncdisplay" on the kvm host.
-Wei
On Wed, 7 Jun 2023 at 10:19, Ian Tobin wrote:
> Hi,
>
> We are currently testing CloudStack.
23 matches
Mail list logo
