Re: [Openstack] Dashboard VNC Console failed to connect to server

[Lucian Thomaz]

Anthony,
I added my iptables rules in the launchpad question
https://answers.launchpad.net/nova/+question/192153 

And I'll try the tcpdump, thanks.

Lucian Thomaz

Date: Wed, 4 Apr 2012 09:25:43 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
From: sleepsonthefl...@gmail.com
To: luciantho...@hotmail.com
CC: vishvana...@gmail.com; openstack@lists.launchpad.net

Lucian - 
Could you also paste your iptables nat rules to the question?
Usually, when I get into a funky network state like you are in, I bust out 
tcpdump and map out exactly how packets are getting moved from interface to 
interface.  That usually gets to the problem quickly.

A

On Wed, Apr 4, 2012 at 5:53 AM, Lucian Thomaz  wrote:





Hi Vish,Thank you, it's really working, but I'm having another trouble yet.

I'm having this trouble in the log of the machine from Dashboard:
wget: can't connect to remote host (169.254.169.254): No route to host

And there are some other thing weird, in the log I can see that the network is 
trying during a while get the private ip for the machine and sometime it works, 
but sometime the network can't take that and so it takes a public ip from dhcp. 
Do you know something about that?

Sending select for 10.0.0.3...
Received DHCP NAK
Sending discover...
Sending select for 10.0.0.3...
Received DHCP NAK
Sending discover...
Sending select for 192.168.100.219...
Lease of 192.168.100.219 obtained, lease time 3600
starting DHCP forEthernet interface eth0  [   [1;32mOK [0;39m  ]
cloud-setup: checking http://169.254.169.254/2009-04-04/meta-data/instance-id
wget: can't connect to remote host (169.254.169.254): No route to host

My question in lauchpad have all my configurations and log. The only thing that 
I added in the configurations diferent from launchpad was this two flags:

--cc_host=192.168.100.140--routing_source_ip=192.168.100.140


https://answers.launchpad.net/nova/+question/192153




Lucian Thomaz 


> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
> From: vishvana...@gmail.com
> Date: Tue, 3 Apr 2012 11:16:04 -0700

> CC: sleepsonthefl...@gmail.com; openstack@lists.launchpad.net
> To: luciantho...@hotmail.com

> 
> It is working!
> 
> You are in the bios screen, so you probably just need to wait (software mode 
> booting can take a while)
> 
> If the vm doesn't ever actually boot, you may be attempting to boot a 
> non-bootable image.

  

  ___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Anthony Young]

Lucian -

Could you also paste your iptables nat rules to the question?

Usually, when I get into a funky network state like you are in, I bust out
tcpdump and map out exactly how packets are getting moved from interface to
interface.  That usually gets to the problem quickly.

A

On Wed, Apr 4, 2012 at 5:53 AM, Lucian Thomaz wrote:

>  Hi Vish,
> Thank you, it's really working, but I'm having another trouble yet.
>
> I'm having this trouble in the log of the machine from Dashboard:
>
> wget: can't connect to remote host (169.254.169.254): No route to host
>
> And there are some other thing weird, in the log I can see that the
> network is trying during a while get the private ip for the machine and
> sometime it works, but sometime the network can't take that and so it takes
> a public ip from dhcp. Do you know something about that?
>
> Sending select for 10.0.0.3...
> Received DHCP NAK
> Sending discover...
> Sending select for 10.0.0.3...
> Received DHCP NAK
> Sending discover...
> Sending select for 192.168.100.219...
> Lease of 192.168.100.219 obtained, lease time 3600
> starting DHCP forEthernet interface eth0  [   [1;32mOK [0;39m  ]
> cloud-setup: checking http://169.254.169.254/2009-04-04/meta-data/instance-id
> wget: can't connect to remote host (169.254.169.254): No route to host
>
>
> My question in lauchpad have all my configurations and log. The only thing
> that I added in the configurations diferent from launchpad was this two
> flags:
>
> --cc_host=192.168.100.140
> --routing_source_ip=192.168.100.140
>
>
> https://answers.launchpad.net/nova/+question/192153
>
>
>
>
> *Lucian Thomaz *
>
>
> > Subject: Re: [Openstack] Dashboard VNC Console failed to connect to
> server
> > From: vishvana...@gmail.com
> > Date: Tue, 3 Apr 2012 11:16:04 -0700
> > CC: sleepsonthefl...@gmail.com; openstack@lists.launchpad.net
> > To: luciantho...@hotmail.com
>
> >
> > It is working!
> >
> > You are in the bios screen, so you probably just need to wait (software
> mode booting can take a while)
> >
> > If the vm doesn't ever actually boot, you may be attempting to boot a
> non-bootable image.
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Lucian Thomaz]

Hi Vish,Thank you, it's really working, but I'm having another trouble yet.
I'm having this trouble in the log of the machine from Dashboard:
wget: can't connect to remote host (169.254.169.254): No route to host
And there are some other thing weird, in the log I can see that the network is 
trying during a while get the private ip for the machine and sometime it works, 
but sometime the network can't take that and so it takes a public ip from dhcp. 
Do you know something about that?
Sending select for 10.0.0.3...
Received DHCP NAK
Sending discover...
Sending select for 10.0.0.3...
Received DHCP NAK
Sending discover...
Sending select for 192.168.100.219...
Lease of 192.168.100.219 obtained, lease time 3600
starting DHCP forEthernet interface eth0  [  OK  ]
cloud-setup: checking http://169.254.169.254/2009-04-04/meta-data/instance-id
wget: can't connect to remote host (169.254.169.254): No route to host

My question in lauchpad have all my configurations and log. The only thing that 
I added in the configurations diferent from launchpad was this two flags:
--cc_host=192.168.100.140--routing_source_ip=192.168.100.140

https://answers.launchpad.net/nova/+question/192153



Lucian Thomaz 

> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
> From: vishvana...@gmail.com
> Date: Tue, 3 Apr 2012 11:16:04 -0700
> CC: sleepsonthefl...@gmail.com; openstack@lists.launchpad.net
> To: luciantho...@hotmail.com
> 
> It is working!
> 
> You are in the bios screen, so you probably just need to wait (software mode 
> booting can take a while)
> 
> If the vm doesn't ever actually boot, you may be attempting to boot a 
> non-bootable image.
  ___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Vishvananda Ishaya]

It is working!

You are in the bios screen, so you probably just need to wait (software mode 
booting can take a while)

If the vm doesn't ever actually boot, you may be attempting to boot a 
non-bootable image.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Anthony Young]

>
>
> I have just a question, the novnc works on wich browsers? I've tried on
> firefox 10.0.2 and didn't worked.
>


Here is an approximate supported version list:
https://github.com/kanaka/noVNC/wiki/Browser-support.  I'm not sure about
that exact version of FF, though I know that certain versions use websocket
emulation and require Adobe Flash to be installed.  I tried the most recent
version of FF on Windows and OSX and it seemed ok.  I also tried 3.6 and it
worked fine.



> With chrome and IE I can connect to my instances, but can't use the
> keyboard.
>
>
Can you send a screenshot and pastie the instance console log?  While it is
possible that there is still an issue with the vnc connection, it is also
possible that your instances did not boot far enough to reach an
interactive state.



> --
> Date: Fri, 30 Mar 2012 12:23:08 -0700
>
> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
> From: sleepsonthefl...@gmail.com
> To: guib...@hotmail.com
> CC: openstack@lists.launchpad.net
>
>
> On Fri, Mar 30, 2012 at 11:29 AM, Guilherme Birk 
>  wrote:
>
> I installed the nova-consoleauth service and that resolved the problem of
> 404 not found. Now I'm getting a cannot connect to the server
> 127.0.0.1:6080. The IP 127.0.0.1 is strange, because on my nova.conf file
> I have the following flags:
>
>
> The 127.0.0.1 means that your flag is not taking effect.
>
> If you are using essex you need:
>
> --novncproxy_base_url=http://192.168.100.142:6080/vnc_auto.html
>
> In https://review.openstack.org/6002 I explain that there are
> configuration options that have changed for essex, this is one of them.
>  Let me know if there is any way I can improve that explanation.
>
> Is this a 1 machine deploy? Given that vncproxy_url (again that is an
> outdated flag) references the same ip as the compute host, your configs
> would only work for all-in-one.
>
> A
>
>
> --vncserver_listen=192.168.100.142
> --vncserver_proxyclient_address=192.168.100.142
> --vncproxy_url=http://192.168.100.142:6080
> --vnc_console_proxy_url=http://192.168.100.142:6080
>
> My problem could be because of the localhost IP? I've already tried the
> port 6081, but with no success.
>
> --------------
> From: luciantho...@hotmail.com
> To: sleepsonthefl...@gmail.com
> Date: Fri, 30 Mar 2012 16:30:05 +
> CC: openstack@lists.launchpad.net
>
> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
>
>  Anthony, I tried to add this flags there and do some more things but I
> didn't have sucess yet.
>
> I made a question in launchpad with all my network configurations and my
> log. Can you see that please?
>
> Thank you.
>
> https://answers.launchpad.net/nova/+question/192153
>
>
> *Lucian Thomaz*
>
>
> --
> Date: Thu, 29 Mar 2012 12:28:24 -0700
> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
> From: sleepsonthefl...@gmail.com
> To: luciantho...@hotmail.com
> CC: openstack@lists.launchpad.net
>
> Here are several flags that you must set on your compute host for a multi
> host deploy:
>
>
>- :option:`--vncserver_listen` <https://github.com/openstack/nova#id3> -
>defaults to 127.0.0.1 This is the address that vncservers will bind, and
>should be overridden in production deployments as a private address.
>Applies to libvirt only. For multi-host libvirt deployments this should be
>set to a host management ip on the same network as the proxies.
>- 
> :option:`--vncserver_proxyclient_address`<https://github.com/openstack/nova#id5>
>  -
>defaults to 127.0.0.1 This is the address of the compute host that nova
>will instruct proxies to use when connecting to instance vncservers. For
>all-in-one xen server domU deployments this can be set to 169.254.0.1. For
>multi-host xen server domU deployments this can be set to a dom0 management
>ip on the same network as the proxies. For multi-host libvirt deployments
>this can be set to a host management ip on the same network as the proxies.
>- :option:`--novncproxy_base_url=[base url for client 
> connections]`<https://github.com/openstack/nova#id7> -
>this is the public base url to which clients will connect. "?token=abc"
>will be added to this url for the purposes of auth. When using the system
>as described in this document, an appropriate value is "
>http://$SERVICE_HOST:6080/vnc_auto.html"; where SERVICE_HOST is a
>public hostname.
>
> Suppose you have 2 servers, APISERVER and COMPUTESERVER:
>
> API

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Guilherme Birk]

Anthony, It's working now. Thanks for your support. I'll take a look at the 
outdated flags at my config.
I have just a question, the novnc works on wich browsers? I've tried on firefox 
10.0.2 and didn't worked. With chrome and IE I can connect to my instances, but 
can't use the keyboard.

Date: Fri, 30 Mar 2012 12:23:08 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
From: sleepsonthefl...@gmail.com
To: guib...@hotmail.com
CC: openstack@lists.launchpad.net

On Fri, Mar 30, 2012 at 11:29 AM, Guilherme Birk  wrote:


I installed the nova-consoleauth service and that resolved the problem of 404 
not found. Now I'm getting a cannot connect to the server127.0.0.1:6080. The IP 
127.0.0.1 is strange, because on my nova.conf file I have the following flags:

The 127.0.0.1 means that your flag is not taking effect.

If you are using essex you need:

--novncproxy_base_url=http://192.168.100.142:6080/vnc_auto.html
In https://review.openstack.org/6002 I explain that there are configuration 
options that have changed for essex, this is one of them.  Let me know if there 
is any way I can improve that explanation.

Is this a 1 machine deploy? Given that vncproxy_url (again that is an outdated 
flag) references the same ip as the compute host, your configs would only work 
for all-in-one.

A



--vncserver_listen=192.168.100.142
--vncserver_proxyclient_address=192.168.100.142
--vncproxy_url=http://192.168.100.142:6080

--vnc_console_proxy_url=http://192.168.100.142:6080

My problem could be because of the localhost IP? I've already tried the port 
6081, but with no success.


From: luciantho...@hotmail.com
To: sleepsonthefl...@gmail.com

Date: Fri, 30 Mar 2012 16:30:05 +
CC: openstack@lists.launchpad.net
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server








Anthony, I tried to add this flags there and do some more things but I didn't 
have sucess yet.


I made a question in launchpad with all my network configurations and my log. 
Can you see that please?

Thank you.

https://answers.launchpad.net/nova/+question/192153



Lucian Thomaz


Date: Thu, 29 Mar 2012 12:28:24 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server

From: sleepsonthefl...@gmail.com
To: luciantho...@hotmail.com
CC: openstack@lists.launchpad.net


Here are several flags that you must set on your compute host for a multi host 
deploy:



:option:`--vncserver_listen` - defaults to 127.0.0.1 This is the address that 
vncservers will bind, and should be overridden in production deployments as a 
private address. Applies to libvirt only. For multi-host libvirt deployments 
this should be set to a host management ip on the same network as the proxies.


:option:`--vncserver_proxyclient_address` - defaults to 127.0.0.1 This is the 
address of the compute host that nova will instruct proxies to use when 
connecting to instance vncservers. For all-in-one xen server domU deployments 
this can be set to 169.254.0.1. For multi-host xen server domU deployments this 
can be set to a dom0 management ip on the same network as the proxies. For 
multi-host libvirt deployments this can be set to a host management ip on the 
same network as the proxies.


:option:`--novncproxy_base_url=[base url for client connections]` - this is the 
public base url to which clients will connect. "?token=abc" will be added to 
this url for the purposes of auth. When using the system as described in this 
document, an appropriate value is "http://$SERVICE_HOST:6080/vnc_auto.html"; 
where SERVICE_HOST is a public hostname.

Suppose you have 2 servers, APISERVER and COMPUTESERVER:
APISERVER:public hostname = my.server.commanagement ip = 192.168.1.1

public ip = 172.24.4.1
COMPUTESERVER:management ip = 192.168.1.2
Your nova.conf con COMPUTESERVER would need the following flags:


novncproxy_base_url=http://my.server.com:6080/vnc_auto.html or 
novncproxy_base_url=http://172.24.4.1:6080/vnc_auto.html

vncserver_proxyclient_address=192.168.1.2vncserver_listen=192.168.1.2


Note that novncproxy_base_url references a public ip or hostname (so clients 
can connect), while the other flags use private ips.


For more 
info:https://github.com/openstack/nova/blob/master/doc/source/runnova/vncconsole.rst



On Thu, Mar 29, 2012 at 11:07 AM, Lucian Thomaz  
wrote:






Hey guys,
I'm using Dashboard with a nova-compute installed in another machine, but when 
I try access VNC Console I get the error "failed to connect to server".


Here is the log -> http://pastebin.com/5DZMfiNE


Anyone already saw this trouble?



Lucian Thomaz 
  

___

Mailing list: https://launchpad.net/~openstack

Post to : openstack@lists.launchpad.net

Unsubscribe : https

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Anthony Young]

On Fri, Mar 30, 2012 at 11:29 AM, Guilherme Birk 
 wrote:

> I installed the nova-consoleauth service and that resolved the problem of
> 404 not found. Now I'm getting a cannot connect to the server
> 127.0.0.1:6080. The IP 127.0.0.1 is strange, because on my nova.conf file
> I have the following flags:
>

The 127.0.0.1 means that your flag is not taking effect.

If you are using essex you need:

--novncproxy_base_url=http://192.168.100.142:6080/vnc_auto.html

In https://review.openstack.org/6002 I explain that there are configuration
options that have changed for essex, this is one of them.  Let me know if
there is any way I can improve that explanation.

Is this a 1 machine deploy? Given that vncproxy_url (again that is an
outdated flag) references the same ip as the compute host, your configs
would only work for all-in-one.

A


> --vncserver_listen=192.168.100.142
> --vncserver_proxyclient_address=192.168.100.142
> --vncproxy_url=http://192.168.100.142:6080
> --vnc_console_proxy_url=http://192.168.100.142:6080
>
> My problem could be because of the localhost IP? I've already tried the
> port 6081, but with no success.
>
> --
> From: luciantho...@hotmail.com
> To: sleepsonthefl...@gmail.com
> Date: Fri, 30 Mar 2012 16:30:05 +
> CC: openstack@lists.launchpad.net
>
> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
>
>  Anthony, I tried to add this flags there and do some more things but I
> didn't have sucess yet.
>
> I made a question in launchpad with all my network configurations and my
> log. Can you see that please?
>
> Thank you.
>
> https://answers.launchpad.net/nova/+question/192153
>
>
> *Lucian Thomaz*
>
>
> ------------------
> Date: Thu, 29 Mar 2012 12:28:24 -0700
> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
> From: sleepsonthefl...@gmail.com
> To: luciantho...@hotmail.com
> CC: openstack@lists.launchpad.net
>
> Here are several flags that you must set on your compute host for a multi
> host deploy:
>
>
>- :option:`--vncserver_listen` <https://github.com/openstack/nova#id3> -
>defaults to 127.0.0.1 This is the address that vncservers will bind, and
>should be overridden in production deployments as a private address.
>Applies to libvirt only. For multi-host libvirt deployments this should be
>set to a host management ip on the same network as the proxies.
>- 
> :option:`--vncserver_proxyclient_address`<https://github.com/openstack/nova#id5>
>  -
>defaults to 127.0.0.1 This is the address of the compute host that nova
>will instruct proxies to use when connecting to instance vncservers. For
>all-in-one xen server domU deployments this can be set to 169.254.0.1. For
>multi-host xen server domU deployments this can be set to a dom0 management
>ip on the same network as the proxies. For multi-host libvirt deployments
>this can be set to a host management ip on the same network as the proxies.
>- :option:`--novncproxy_base_url=[base url for client 
> connections]`<https://github.com/openstack/nova#id7> -
>this is the public base url to which clients will connect. "?token=abc"
>will be added to this url for the purposes of auth. When using the system
>as described in this document, an appropriate value is "
>http://$SERVICE_HOST:6080/vnc_auto.html"; where SERVICE_HOST is a
>public hostname.
>
> Suppose you have 2 servers, APISERVER and COMPUTESERVER:
>
> APISERVER:
> public hostname = my.server.com
> management ip = 192.168.1.1
> public ip = 172.24.4.1
>
> COMPUTESERVER:
> management ip = 192.168.1.2
>
> Your nova.conf con COMPUTESERVER would need the following flags:
>
> novncproxy_base_url=http://my.server.com:6080/vnc_auto.html or
> novncproxy_base_url=http://172.24.4.1:6080/vnc_auto.html
> vncserver_proxyclient_address=192.168.1.2
> vncserver_listen=192.168.1.2
>
> Note that novncproxy_base_url references a public ip or hostname (so
> clients can connect), while the other flags use private ips.
>
> For more info:
>
> https://github.com/openstack/nova/blob/master/doc/source/runnova/vncconsole.rst
>
>
> On Thu, Mar 29, 2012 at 11:07 AM, Lucian Thomaz 
> wrote:
>
>  Hey guys,
>
> I'm using Dashboard with a nova-compute installed in another machine, but
> when I try access VNC Console I get the error "failed to connect to server".
>
> Here is the log -> http://pastebin.com/5DZMfiNE
>
> Anyone already saw this trouble?
>
>
> *Lucian Thomaz *
>
>
> ___
> Mailing list: https://launchpad.net

Re: [Openstack] Dashboard VNC Console failed to connect to server

[David Kranz]

Thanks, Anthony. All is well now. Presumably once this feature is really 
in essex there will be a novnc package that will take care of the numpy 
dependency when it is installed.


 -David

On 3/30/2012 2:23 PM, Anthony Young wrote:
I've proposed doc changes that add a FAQ and also remove references to 
vnc_redux (thanks for bringing that to my attention).


https://review.openstack.org/6002

In the FAQ I also mention the python-numpy noVNC dependency, which 
appears to be biting you.


A

On Fri, Mar 30, 2012 at 7:56 AM, David Kranz > wrote:


I am also having problems with vnc console but not using dashboard
and of a different kind. First, the documentation says to use the
vnc_redux branch but that is evidently diablo-compatible code. So
I used master and did the same thing as devstack does (I think)
and I can get a console

root@xg06:~/noVNC# nova get-vnc-console test novnc

+---+---+
|  Type |Url  
 |


+---+---+
| novnc |

http://172.18.0.146:6080/vnc_auto.html?token=43971233-a806-4f01-96b1-8861c1dc7410
|

+---+---+

but when I browse to that I get this from novnc log, and an error
banner with "Websock error: [Object Event]"
If I do the same thing against devstack the log is different and
it works. Any help would be appreciated.
Also, this stuff seems only semi-official with references to
cloudbuilders git repos. Is it officially part of Essex?

 -David

multinode package deploy + noVNC from git
 1: 172.17.1.170 : "GET
/vnc_auto.html?token=43971233-a806-4f01-96b1-8861c1dc7410
HTTP/1.1" 200 -
 2: 172.17.1.170 : new handler Process
 3: 172.17.1.170 : new handler Process
 2: 172.17.1.170 : "GET /include/plain.css
HTTP/1.1" 200 -
 3: 172.17.1.170 : "GET /include/vnc.js
HTTP/1.1" 200 -
 4: 172.17.1.170 : new handler Process
 5: 172.17.1.170 : new handler Process
 6: 172.17.1.170 : new handler Process
 4: 172.17.1.170 : "GET /include/util.js
HTTP/1.1" 200 -
 7: 172.17.1.170 : new handler Process
 5: 172.17.1.170 : "GET /include/webutil.js
HTTP/1.1" 200 -
 8: 172.17.1.170 : new handler Process
 6: 172.17.1.170 : "GET /include/logo.js
HTTP/1.1" 200 -
 7: 172.17.1.170 : "GET /include/base64.js
HTTP/1.1" 200 -
 8: 172.17.1.170 : "GET /include/websock.js
HTTP/1.1" 200 -
 9: 172.17.1.170 : new handler Process
 10: 172.17.1.170 : new handler Process
 9: 172.17.1.170 : "GET /include/des.js
HTTP/1.1" 200 -
 11: 172.17.1.170 : new handler Process
 12: 172.17.1.170 : new handler Process
 10: 172.17.1.170 : "GET /include/input.js
HTTP/1.1" 200 -
 11: 172.17.1.170 : "GET /include/display.js
HTTP/1.1" 200 -
 12: 172.17.1.170 : "GET /include/rfb.js
HTTP/1.1" 200 -
 13: 172.17.1.170 : new handler Process
DIFFERENCE STARTS HERE
 14: 172.17.1.170 : new handler Process
 13: 172.17.1.170 : Python >= 2.6 and numpy
module is required for HyBi-07 or greater
 14: 172.17.1.170 : "GET /favicon.ico
HTTP/1.1" 200 -


devstack: works
 1: 172.17.1.170 : "GET
/vnc_auto.html?token=e64e682e-5c69-42dd-8d78-01537b3d3223
HTTP/1.1" 200 -
 2: 172.17.1.170 : new handler Process
 3: 172.17.1.170 : new handler Process
 2: 172.17.1.170 : "GET /include/plain.css
HTTP/1.1" 200 -
 3: 172.17.1.170 : "GET /include/vnc.js
HTTP/1.1" 200 -
 4: 172.17.1.170 : new handler Process
 5: 172.17.1.170 : new handler Process
 6: 172.17.1.170 : new handler Process
 4: 172.17.1.170 : "GET /include/util.js
HTTP/1.1" 200 -
 7: 172.17.1.170 : new handler Process
 5: 172.17.1.170 : "GET /include/webutil.js
HTTP/1.1" 200 -
 8: 172.17.1.170 : new handler Process
 6: 172.17.1.170 

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Lucian Thomaz]

Anthony,
thank you, I saw that.

I'm working in it and I'll report if I have success.

Lucian Thomaz

Date: Fri, 30 Mar 2012 11:18:31 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
From: sleepsonthefl...@gmail.com
To: luciantho...@hotmail.com
CC: openstack@lists.launchpad.net

Lucian,
I added a response to your question.  There are several issues at play there.
A

On Fri, Mar 30, 2012 at 9:30 AM, Lucian Thomaz  wrote:





Anthony, I tried to add this flags there and do some more things but I didn't 
have sucess yet.


I made a question in launchpad with all my network configurations and my log. 
Can you see that please?

Thank you.

https://answers.launchpad.net/nova/+question/192153



Lucian Thomaz



Date: Thu, 29 Mar 2012 12:28:24 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
From: sleepsonthefl...@gmail.com

To: luciantho...@hotmail.com
CC: openstack@lists.launchpad.net


Here are several flags that you must set on your compute host for a multi host 
deploy:



:option:`--vncserver_listen` - defaults to 127.0.0.1 This is the address that 
vncservers will bind, and should be overridden in production deployments as a 
private address. Applies to libvirt only. For multi-host libvirt deployments 
this should be set to a host management ip on the same network as the proxies.


:option:`--vncserver_proxyclient_address` - defaults to 127.0.0.1 This is the 
address of the compute host that nova will instruct proxies to use when 
connecting to instance vncservers. For all-in-one xen server domU deployments 
this can be set to 169.254.0.1. For multi-host xen server domU deployments this 
can be set to a dom0 management ip on the same network as the proxies. For 
multi-host libvirt deployments this can be set to a host management ip on the 
same network as the proxies.


:option:`--novncproxy_base_url=[base url for client connections]` - this is the 
public base url to which clients will connect. "?token=abc" will be added to 
this url for the purposes of auth. When using the system as described in this 
document, an appropriate value is "http://$SERVICE_HOST:6080/vnc_auto.html"; 
where SERVICE_HOST is a public hostname.

Suppose you have 2 servers, APISERVER and COMPUTESERVER:
APISERVER:public hostname = my.server.commanagement ip = 192.168.1.1

public ip = 172.24.4.1
COMPUTESERVER:management ip = 192.168.1.2
Your nova.conf con COMPUTESERVER would need the following flags:


novncproxy_base_url=http://my.server.com:6080/vnc_auto.html or 
novncproxy_base_url=http://172.24.4.1:6080/vnc_auto.html

vncserver_proxyclient_address=192.168.1.2vncserver_listen=192.168.1.2


Note that novncproxy_base_url references a public ip or hostname (so clients 
can connect), while the other flags use private ips.


For more 
info:https://github.com/openstack/nova/blob/master/doc/source/runnova/vncconsole.rst



On Thu, Mar 29, 2012 at 11:07 AM, Lucian Thomaz  
wrote:






Hey guys,
I'm using Dashboard with a nova-compute installed in another machine, but when 
I try access VNC Console I get the error "failed to connect to server".


Here is the log -> http://pastebin.com/5DZMfiNE


Anyone already saw this trouble?



Lucian Thomaz 
  

___

Mailing list: https://launchpad.net/~openstack

Post to : openstack@lists.launchpad.net

Unsubscribe : https://launchpad.net/~openstack

More help   : https://help.launchpad.net/ListHelp



  

  ___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Guilherme Birk]

I installed the nova-consoleauth service and that resolved the problem 
of 404 not found. Now I'm getting a cannot connect to the server 
127.0.0.1:6080. The IP 127.0.0.1 is strange, because on my nova.conf 
file I have the following flags:
--vncserver_listen=192.168.100.142
--vncserver_proxyclient_address=192.168.100.142
--vncproxy_url=http://192.168.100.142:6080
--vnc_console_proxy_url=http://192.168.100.142:6080

My problem could be because of the localhost IP? I've already tried the port 
6081, but with no success.

From: luciantho...@hotmail.com
To: sleepsonthefl...@gmail.com
Date: Fri, 30 Mar 2012 16:30:05 +
CC: openstack@lists.launchpad.net
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server







Anthony, I tried to add this flags there and do some more things but I didn't 
have sucess yet.

I made a question in launchpad with all my network configurations and my log. 
Can you see that please?

Thank you.

https://answers.launchpad.net/nova/+question/192153

Lucian Thomaz


Date: Thu, 29 Mar 2012 12:28:24 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
From: sleepsonthefl...@gmail.com
To: luciantho...@hotmail.com
CC: openstack@lists.launchpad.net

Here are several flags that you must set on your compute host for a multi host 
deploy:


:option:`--vncserver_listen` - defaults to 127.0.0.1 This is the address that 
vncservers will bind, and should be overridden in production deployments as a 
private address. Applies to libvirt only. For multi-host libvirt deployments 
this should be set to a host management ip on the same network as the proxies.

:option:`--vncserver_proxyclient_address` - defaults to 127.0.0.1 This is the 
address of the compute host that nova will instruct proxies to use when 
connecting to instance vncservers. For all-in-one xen server domU deployments 
this can be set to 169.254.0.1. For multi-host xen server domU deployments this 
can be set to a dom0 management ip on the same network as the proxies. For 
multi-host libvirt deployments this can be set to a host management ip on the 
same network as the proxies.

:option:`--novncproxy_base_url=[base url for client connections]` - this is the 
public base url to which clients will connect. "?token=abc" will be added to 
this url for the purposes of auth. When using the system as described in this 
document, an appropriate value is "http://$SERVICE_HOST:6080/vnc_auto.html"; 
where SERVICE_HOST is a public hostname.
Suppose you have 2 servers, APISERVER and COMPUTESERVER:
APISERVER:public hostname = my.server.commanagement ip = 192.168.1.1
public ip = 172.24.4.1
COMPUTESERVER:management ip = 192.168.1.2
Your nova.conf con COMPUTESERVER would need the following flags:

novncproxy_base_url=http://my.server.com:6080/vnc_auto.html or 
novncproxy_base_url=http://172.24.4.1:6080/vnc_auto.html
vncserver_proxyclient_address=192.168.1.2vncserver_listen=192.168.1.2

Note that novncproxy_base_url references a public ip or hostname (so clients 
can connect), while the other flags use private ips.

For more 
info:https://github.com/openstack/nova/blob/master/doc/source/runnova/vncconsole.rst


On Thu, Mar 29, 2012 at 11:07 AM, Lucian Thomaz  
wrote:





Hey guys,
I'm using Dashboard with a nova-compute installed in another machine, but when 
I try access VNC Console I get the error "failed to connect to server".

Here is the log -> http://pastebin.com/5DZMfiNE

Anyone already saw this trouble?



Lucian Thomaz 
  

___

Mailing list: https://launchpad.net/~openstack

Post to : openstack@lists.launchpad.net

Unsubscribe : https://launchpad.net/~openstack

More help   : https://help.launchpad.net/ListHelp



  

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp   
  ___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Anthony Young]

I've proposed doc changes that add a FAQ and also remove references to
vnc_redux (thanks for bringing that to my attention).

https://review.openstack.org/6002

In the FAQ I also mention the python-numpy noVNC dependency, which appears
to be biting you.

A

On Fri, Mar 30, 2012 at 7:56 AM, David Kranz  wrote:

> I am also having problems with vnc console but not using dashboard and of
> a different kind. First, the documentation says to use the vnc_redux branch
> but that is evidently diablo-compatible code. So I used master and did the
> same thing as devstack does (I think) and I can get a console
>
> root@xg06:~/noVNC# nova get-vnc-console test novnc
> +---+-**--**
> --**--+
> |  Type |Url
>  |
> +---+-**--**
> --**--+
> | novnc | http://172.18.0.146:6080/vnc_**auto.html?token=43971233-a806-**
> 4f01-96b1-8861c1dc7410|
> +---+-**--**
> --**--+
>
> but when I browse to that I get this from novnc log, and an error banner
> with "Websock error: [Object Event]"
> If I do the same thing against devstack the log is different and it works.
> Any help would be appreciated.
> Also, this stuff seems only semi-official with references to cloudbuilders
> git repos. Is it officially part of Essex?
>
>  -David
>
> multinode package deploy + noVNC from git
>  1: 172.17.1.170: "GET 
> /vnc_auto.html?token=43971233-**a806-4f01-96b1-8861c1dc7410
> HTTP/1.1" 200 -
>  2: 172.17.1.170: new handler Process
>  3: 172.17.1.170: new handler Process
>  2: 172.17.1.170: "GET /include/plain.css HTTP/1.1" 200 -
>  3: 172.17.1.170: "GET /include/vnc.js HTTP/1.1" 200 -
>  4: 172.17.1.170: new handler Process
>  5: 172.17.1.170: new handler Process
>  6: 172.17.1.170: new handler Process
>  4: 172.17.1.170: "GET /include/util.js HTTP/1.1" 200 -
>  7: 172.17.1.170: new handler Process
>  5: 172.17.1.170: "GET /include/webutil.js HTTP/1.1" 200 -
>  8: 172.17.1.170: new handler Process
>  6: 172.17.1.170: "GET /include/logo.js HTTP/1.1" 200 -
>  7: 172.17.1.170: "GET /include/base64.js HTTP/1.1" 200 -
>  8: 172.17.1.170: "GET /include/websock.js HTTP/1.1" 200 -
>  9: 172.17.1.170: new handler Process
>  10: 172.17.1.170: new handler Process
>  9: 172.17.1.170: "GET /include/des.js HTTP/1.1" 200 -
>  11: 172.17.1.170: new handler Process
>  12: 172.17.1.170: new handler Process
>  10: 172.17.1.170: "GET /include/input.js HTTP/1.1" 200 -
>  11: 172.17.1.170: "GET /include/display.js HTTP/1.1" 200 -
>  12: 172.17.1.170: "GET /include/rfb.js HTTP/1.1" 200 -
>  13: 172.17.1.170: new handler Process
> DIFFERENCE STARTS HERE
>  14: 172.17.1.170: new handler Process
>  13: 172.17.1.170: Python >= 2.6 and numpy module is required for HyBi-07
> or greater
>  14: 172.17.1.170: "GET /favicon.ico HTTP/1.1" 200 -
>
>
> devstack: works
>  1: 172.17.1.170: "GET 
> /vnc_auto.html?token=e64e682e-**5c69-42dd-8d78-01537b3d3223
> HTTP/1.1" 200 -
>  2: 172.17.1.170: new handler Process
>  3: 172.17.1.170: new handler Process
>  2: 172.17.1.170: "GET /include/plain.css HTTP/1.1" 200 -
>  3: 172.17.1.170: "GET /include/vnc.js HTTP/1.1" 200 -
>  4: 172.17.1.170: new handler Process
>  5: 172.17.1.170: new handler Process
>  6: 172.17.1.170: new handler Process
>  4: 172.17.1.170: "GET /include/util.js HTTP/1.1" 200 -
>  7: 172.17.1.170: new handler Process
>  5: 172.17.1.170: "GET /include/webutil.js HTTP/1.1" 200 -
>  8: 172.17.1.170: new handler Process
>  6: 172.17.1.170: "GET /include/logo.js HTTP/1.1" 200 -
>  9: 172.17.1.170: new handler Process
>  7: 172.17.1.170: "GET /include/base64.js HTTP/1.1" 200 -
>  8: 172.17.1.170: "GET /include/websock.js HTTP/1.1" 200 -
>  9: 172.17.1.170: "GET /include/des.js HTTP/1.1" 200 -
>  10: 172.17.1.170: new handler Process
>  11: 172.17.1.170: new handler Process
>  12: 172.17.1.170: new handler Process
>  11: 172.17.1.170: "GET /include/display.js HTTP/1.1" 200 -
>  10: 172.17.1.170: "GET /include/input.js HTTP/1.1" 200 -
>  12: 172.17.1.170: "GET /include/rfb.js HTTP/1.1" 200 -
>  13: 172.17.1.170: new handler Process
>  13: 172.17.1.170: Plain non-SSL (ws://) WebSocket connection
>  13: 172.17.1.170: Version hybi-08, base64: 'True'
>  13: connecting to: 127.0.0.1:5900
>
>
>
>
>
> __**_
> Mailing list: 
> https://launchpad.net/~**openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : 
> https://launchpad.net/~**openstack
> More help   : 
> https://help.launchpad.net/**ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to   

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Anthony Young]

Lucian,

I added a response to your question.  There are several issues at play
there.

A

On Fri, Mar 30, 2012 at 9:30 AM, Lucian Thomaz wrote:

>  Anthony, I tried to add this flags there and do some more things but I
> didn't have sucess yet.
>
> I made a question in launchpad with all my network configurations and my
> log. Can you see that please?
>
> Thank you.
>
> https://answers.launchpad.net/nova/+question/192153
>
>
> *Lucian Thomaz*
>
>
> --
> Date: Thu, 29 Mar 2012 12:28:24 -0700
> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
> From: sleepsonthefl...@gmail.com
> To: luciantho...@hotmail.com
> CC: openstack@lists.launchpad.net
>
>
> Here are several flags that you must set on your compute host for a multi
> host deploy:
>
>
>- :option:`--vncserver_listen` <https://github.com/openstack/nova#id3> -
>defaults to 127.0.0.1 This is the address that vncservers will bind, and
>should be overridden in production deployments as a private address.
>Applies to libvirt only. For multi-host libvirt deployments this should be
>set to a host management ip on the same network as the proxies.
>- 
> :option:`--vncserver_proxyclient_address`<https://github.com/openstack/nova#id5>
>  -
>defaults to 127.0.0.1 This is the address of the compute host that nova
>will instruct proxies to use when connecting to instance vncservers. For
>all-in-one xen server domU deployments this can be set to 169.254.0.1. For
>multi-host xen server domU deployments this can be set to a dom0 management
>ip on the same network as the proxies. For multi-host libvirt deployments
>this can be set to a host management ip on the same network as the proxies.
>- :option:`--novncproxy_base_url=[base url for client 
> connections]`<https://github.com/openstack/nova#id7> -
>this is the public base url to which clients will connect. "?token=abc"
>will be added to this url for the purposes of auth. When using the system
>as described in this document, an appropriate value is "
>http://$SERVICE_HOST:6080/vnc_auto.html"; where SERVICE_HOST is a
>public hostname.
>
> Suppose you have 2 servers, APISERVER and COMPUTESERVER:
>
> APISERVER:
> public hostname = my.server.com
> management ip = 192.168.1.1
> public ip = 172.24.4.1
>
> COMPUTESERVER:
> management ip = 192.168.1.2
>
> Your nova.conf con COMPUTESERVER would need the following flags:
>
> novncproxy_base_url=http://my.server.com:6080/vnc_auto.html or
> novncproxy_base_url=http://172.24.4.1:6080/vnc_auto.html
> vncserver_proxyclient_address=192.168.1.2
> vncserver_listen=192.168.1.2
>
> Note that novncproxy_base_url references a public ip or hostname (so
> clients can connect), while the other flags use private ips.
>
> For more info:
>
> https://github.com/openstack/nova/blob/master/doc/source/runnova/vncconsole.rst
>
>
> On Thu, Mar 29, 2012 at 11:07 AM, Lucian Thomaz 
> wrote:
>
>  Hey guys,
>
> I'm using Dashboard with a nova-compute installed in another machine, but
> when I try access VNC Console I get the error "failed to connect to server".
>
> Here is the log -> http://pastebin.com/5DZMfiNE
>
> Anyone already saw this trouble?
>
>
> *Lucian Thomaz *
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Lucian Thomaz]

Anthony, I tried to add this flags there and do some more things but I didn't 
have sucess yet.

I made a question in launchpad with all my network configurations and my log. 
Can you see that please?

Thank you.

https://answers.launchpad.net/nova/+question/192153

Lucian Thomaz


Date: Thu, 29 Mar 2012 12:28:24 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
From: sleepsonthefl...@gmail.com
To: luciantho...@hotmail.com
CC: openstack@lists.launchpad.net

Here are several flags that you must set on your compute host for a multi host 
deploy:


:option:`--vncserver_listen` - defaults to 127.0.0.1 This is the address that 
vncservers will bind, and should be overridden in production deployments as a 
private address. Applies to libvirt only. For multi-host libvirt deployments 
this should be set to a host management ip on the same network as the proxies.

:option:`--vncserver_proxyclient_address` - defaults to 127.0.0.1 This is the 
address of the compute host that nova will instruct proxies to use when 
connecting to instance vncservers. For all-in-one xen server domU deployments 
this can be set to 169.254.0.1. For multi-host xen server domU deployments this 
can be set to a dom0 management ip on the same network as the proxies. For 
multi-host libvirt deployments this can be set to a host management ip on the 
same network as the proxies.

:option:`--novncproxy_base_url=[base url for client connections]` - this is the 
public base url to which clients will connect. "?token=abc" will be added to 
this url for the purposes of auth. When using the system as described in this 
document, an appropriate value is "http://$SERVICE_HOST:6080/vnc_auto.html"; 
where SERVICE_HOST is a public hostname.
Suppose you have 2 servers, APISERVER and COMPUTESERVER:
APISERVER:public hostname = my.server.commanagement ip = 192.168.1.1
public ip = 172.24.4.1
COMPUTESERVER:management ip = 192.168.1.2
Your nova.conf con COMPUTESERVER would need the following flags:

novncproxy_base_url=http://my.server.com:6080/vnc_auto.html or 
novncproxy_base_url=http://172.24.4.1:6080/vnc_auto.html
vncserver_proxyclient_address=192.168.1.2vncserver_listen=192.168.1.2

Note that novncproxy_base_url references a public ip or hostname (so clients 
can connect), while the other flags use private ips.

For more 
info:https://github.com/openstack/nova/blob/master/doc/source/runnova/vncconsole.rst


On Thu, Mar 29, 2012 at 11:07 AM, Lucian Thomaz  
wrote:





Hey guys,
I'm using Dashboard with a nova-compute installed in another machine, but when 
I try access VNC Console I get the error "failed to connect to server".

Here is the log -> http://pastebin.com/5DZMfiNE

Anyone already saw this trouble?



Lucian Thomaz 
  

___

Mailing list: https://launchpad.net/~openstack

Post to : openstack@lists.launchpad.net

Unsubscribe : https://launchpad.net/~openstack

More help   : https://help.launchpad.net/ListHelp



  ___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Anthony Young]

On Fri, Mar 30, 2012 at 9:12 AM, Michaël Van de Borne <
michael.vandebo...@cetic.be> wrote:

>  Thank you.
>
> I installed the package.
>
>
Now I've got this error when I paste the vnc url (which I got with nova
> get-vnc-console) in firefox:
>
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/eventlet/wsgi.py", line 347, in 
> handle_one_response
> for data in result:
> TypeError: 'NoneType' object is not iterable
>
> and the nova-xvpvncproxy.log looks like this:
>
>
nova-xvpvncproxy is designed to work with a java client.  You want to use
nova-novncproxy, which is provided as part of the noVNC code from
http://github.com/cloudbuilders/noVNC.git.

More info here:
https://github.com/openstack/nova/blob/master/doc/source/runnova/vncconsole.rst

I'll be updating that doc today to incorporate some of the feedback from
this thread.





> 2012-03-30 18:06:48 AUDIT nova.vnc.xvp_proxy [-] Request: GET 
> /console?token=e77c1d12-c375-4b42-a165-f3d937bf2c41 HTTP/1.0
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> Accept-Encoding: gzip, deflate
> Accept-Language: fr,fr-fr;q=0.8,en-us;q=0.5,en;q=0.3
> Connection: keep-alive
> Content-Type: text/plain
> Cookie: csrftoken=4a9047c0e8eccd8a86da788412550c46; 
> sessionid=fad912a6dbe83526e861546b3cf7ee68
> Host: 172.22.22.1:6081
> User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:11.0) Gecko/20100101 
> Firefox/11.0
> 2012-03-30 18:06:48 DEBUG nova.rpc.amqp 
> [req-22f145a1-7834-4483-a1bf-f94ae9e53c1d None None] Making asynchronous call 
> on consoleauth ... from (pid=16674) multicall 
> /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py:321
> 2012-03-30 18:06:48 DEBUG nova.rpc.amqp 
> [req-22f145a1-7834-4483-a1bf-f94ae9e53c1d None None] MSG_ID is 
> c90d93874b33438ca4e8ffca54ee48d8 from (pid=16674) multicall 
> /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py:324
> 2012-03-30 18:06:48 DEBUG nova.rpc.amqp 
> [req-22f145a1-7834-4483-a1bf-f94ae9e53c1d None None] Pool creating new 
> connection from (pid=16674) create 
> /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py:59
> 2012-03-30 18:06:48 INFO nova.rpc.common 
> [req-22f145a1-7834-4483-a1bf-f94ae9e53c1d None None] Connected to AMQP server 
> on 172.22.22.1:5672
> 2012-03-30 18:06:48 AUDIT nova.vnc.xvp_proxy 
> [req-22f145a1-7834-4483-a1bf-f94ae9e53c1d None None] Unexpected error: [Errno 
> 111] ECONNREFUSED
>
> any help appreciated,
>
> thank you
>
>
>
>
>
> Michaël Van de Borne
> R&D Engineer, SOA team, CETIC
> Phone: +32 (0)71 49 07 45 Mobile: +32 (0)472 69 57 16, Skype: 
> mikemowgliwww.cetic.be, rue des Frères Wright, 29/3, B-6041 Charleroi
>
>
> Le 30/03/12 17:51, Guilherme Birk a écrit :
>
>  Michael, try to install nova-consoleauth, like Anthony said. The old
> error was fixed when I installed it, now I'm having another issue, but now
> I think it's related to my network.
>
>  --
> Date: Fri, 30 Mar 2012 16:36:14 +0200
> From: michael.vandebo...@cetic.be
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
>
> I've got the same problem.
>
> When I try to connect to the instance using VNC through the dashboard,
> I've got this error. I then went in /var/log/nova/nova-xvpvncproxy.log and
> it contains nothing related to any attempt to get connected to any
> instance. It seems this nova-xvpvncproxy process doesn't notice anything.
>
>
> When I try to connect using VNC through virt-manager, it works.
>
>
> Le 30/03/12 15:50, Guilherme Birk a écrit :
>
>  Thanks for the reply.
>
> I've added the flags that you mentioned on my nova.conf file. I'm using a
> all in one installation, the flags are configured this way.
> --vncserver_listen=127.0.0.1
> --vncserver_proxyclient_address=127.0.0.1
> --novncproxy_base_url=http://192.168.100.142:6080/vnc_auto.html
>
> The public IP of the machine with the OpenStack installation is
> 192.168.100.142.
> I've tried to access via browser the address
> http://192.168.100.142:6080/vnc_auto.html from another machine, but I got
> nothing.
>
> I can ping and ssh my instances from the OpenStack machine but can't use
> VNC tab at dashboard page from another machine. The details and other pages
> from dashboard are fine.
> Should I associate a public address for my instances? I'm using just the
> private address at them (10.0.0.2, 10.0.0.3, ...).
>
> I've restarted all the services and created new instances after changing
> the nova.conf, but nothing has changed.
>
> The error is a 404 not found. (*Error: *Unable to

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Anthony Young]

On Fri, Mar 30, 2012 at 7:56 AM, David Kranz  wrote:

> I am also having problems with vnc console but not using dashboard and of
> a different kind. First, the documentation says to use the vnc_redux branch
> but that is evidently diablo-compatible code. So I used master and did the
> same thing as devstack does (I think) and I can get a console
>
>
The reference to vnc_redux is old - that branch existed to support
development of the feature in nova.  I'll update the docs.


> root@xg06:~/noVNC# nova get-vnc-console test novnc
> +---+-**--**
> --**--+
> |  Type |Url
>  |
> +---+-**--**
> --**--+
> | novnc | http://172.18.0.146:6080/vnc_**auto.html?token=43971233-a806-**
> 4f01-96b1-8861c1dc7410|
> +---+-**--**
> --**--+
>
> but when I browse to that I get this from novnc log, and an error banner
> with "Websock error: [Object Event]"
> If I do the same thing against devstack the log is different and it works.
> Any help would be appreciated.
>

Devstack automatically installs python-numpy, which noVNC requires for
certain websocket connections.


> Also, this stuff seems only semi-official with references to cloudbuilders
> git repos. Is it officially part of Essex?
>
>
I'll talk to jeblair about moving it to an openstack repo.  I view vnc as
essential to any deployment, so while it is not 'core' or anything anyone
deploying Essex will need it.


>  -David
>
> multinode package deploy + noVNC from git
>  1: 172.17.1.170: "GET 
> /vnc_auto.html?token=43971233-**a806-4f01-96b1-8861c1dc7410
> HTTP/1.1" 200 -
>  2: 172.17.1.170: new handler Process
>  3: 172.17.1.170: new handler Process
>  2: 172.17.1.170: "GET /include/plain.css HTTP/1.1" 200 -
>  3: 172.17.1.170: "GET /include/vnc.js HTTP/1.1" 200 -
>  4: 172.17.1.170: new handler Process
>  5: 172.17.1.170: new handler Process
>  6: 172.17.1.170: new handler Process
>  4: 172.17.1.170: "GET /include/util.js HTTP/1.1" 200 -
>  7: 172.17.1.170: new handler Process
>  5: 172.17.1.170: "GET /include/webutil.js HTTP/1.1" 200 -
>  8: 172.17.1.170: new handler Process
>  6: 172.17.1.170: "GET /include/logo.js HTTP/1.1" 200 -
>  7: 172.17.1.170: "GET /include/base64.js HTTP/1.1" 200 -
>  8: 172.17.1.170: "GET /include/websock.js HTTP/1.1" 200 -
>  9: 172.17.1.170: new handler Process
>  10: 172.17.1.170: new handler Process
>  9: 172.17.1.170: "GET /include/des.js HTTP/1.1" 200 -
>  11: 172.17.1.170: new handler Process
>  12: 172.17.1.170: new handler Process
>  10: 172.17.1.170: "GET /include/input.js HTTP/1.1" 200 -
>  11: 172.17.1.170: "GET /include/display.js HTTP/1.1" 200 -
>  12: 172.17.1.170: "GET /include/rfb.js HTTP/1.1" 200 -
>  13: 172.17.1.170: new handler Process
> DIFFERENCE STARTS HERE
>  14: 172.17.1.170: new handler Process
>  13: 172.17.1.170: Python >= 2.6 and numpy module is required for HyBi-07
> or greater
>  14: 172.17.1.170: "GET /favicon.ico HTTP/1.1" 200 -
>
>
> devstack: works
>  1: 172.17.1.170: "GET 
> /vnc_auto.html?token=e64e682e-**5c69-42dd-8d78-01537b3d3223
> HTTP/1.1" 200 -
>  2: 172.17.1.170: new handler Process
>  3: 172.17.1.170: new handler Process
>  2: 172.17.1.170: "GET /include/plain.css HTTP/1.1" 200 -
>  3: 172.17.1.170: "GET /include/vnc.js HTTP/1.1" 200 -
>  4: 172.17.1.170: new handler Process
>  5: 172.17.1.170: new handler Process
>  6: 172.17.1.170: new handler Process
>  4: 172.17.1.170: "GET /include/util.js HTTP/1.1" 200 -
>  7: 172.17.1.170: new handler Process
>  5: 172.17.1.170: "GET /include/webutil.js HTTP/1.1" 200 -
>  8: 172.17.1.170: new handler Process
>  6: 172.17.1.170: "GET /include/logo.js HTTP/1.1" 200 -
>  9: 172.17.1.170: new handler Process
>  7: 172.17.1.170: "GET /include/base64.js HTTP/1.1" 200 -
>  8: 172.17.1.170: "GET /include/websock.js HTTP/1.1" 200 -
>  9: 172.17.1.170: "GET /include/des.js HTTP/1.1" 200 -
>  10: 172.17.1.170: new handler Process
>  11: 172.17.1.170: new handler Process
>  12: 172.17.1.170: new handler Process
>  11: 172.17.1.170: "GET /include/display.js HTTP/1.1" 200 -
>  10: 172.17.1.170: "GET /include/input.js HTTP/1.1" 200 -
>  12: 172.17.1.170: "GET /include/rfb.js HTTP/1.1" 200 -
>  13: 172.17.1.170: new handler Process
>  13: 172.17.1.170: Plain non-SSL (ws://) WebSocket connection
>  13: 172.17.1.170: Version hybi-08, base64: 'True'
>  13: connecting to: 127.0.0.1:5900
>
>
>
>
>
> __**_
> Mailing list: 
> https://launchpad.net/~**openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : 
> https://launchpad.net/~**openstack
> More help   : 
> https://help.launchpa

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Michaël Van de Borne]

Thank you.

I installed the package.

Now I've got this error when I paste the vnc url (which I got with nova 
get-vnc-console) in firefox:


Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/eventlet/wsgi.py", line 347, in 
handle_one_response
for data in result:
TypeError: 'NoneType' object is not iterable

and the nova-xvpvncproxy.log looks like this:

2012-03-30 18:06:48 AUDIT nova.vnc.xvp_proxy [-] Request: GET 
/console?token=e77c1d12-c375-4b42-a165-f3d937bf2c41 HTTP/1.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: gzip, deflate
Accept-Language: fr,fr-fr;q=0.8,en-us;q=0.5,en;q=0.3
Connection: keep-alive
Content-Type: text/plain
Cookie: csrftoken=4a9047c0e8eccd8a86da788412550c46; 
sessionid=fad912a6dbe83526e861546b3cf7ee68
Host: 172.22.22.1:6081
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:11.0) Gecko/20100101 
Firefox/11.0
2012-03-30 18:06:48 DEBUG nova.rpc.amqp 
[req-22f145a1-7834-4483-a1bf-f94ae9e53c1d None None] Making asynchronous call 
on consoleauth ... from (pid=16674) multicall 
/usr/lib/python2.7/dist-packages/nova/rpc/amqp.py:321
2012-03-30 18:06:48 DEBUG nova.rpc.amqp 
[req-22f145a1-7834-4483-a1bf-f94ae9e53c1d None None] MSG_ID is 
c90d93874b33438ca4e8ffca54ee48d8 from (pid=16674) multicall 
/usr/lib/python2.7/dist-packages/nova/rpc/amqp.py:324
2012-03-30 18:06:48 DEBUG nova.rpc.amqp 
[req-22f145a1-7834-4483-a1bf-f94ae9e53c1d None None] Pool creating new 
connection from (pid=16674) create 
/usr/lib/python2.7/dist-packages/nova/rpc/amqp.py:59
2012-03-30 18:06:48 INFO nova.rpc.common 
[req-22f145a1-7834-4483-a1bf-f94ae9e53c1d None None] Connected to AMQP server 
on 172.22.22.1:5672
2012-03-30 18:06:48 AUDIT nova.vnc.xvp_proxy 
[req-22f145a1-7834-4483-a1bf-f94ae9e53c1d None None] Unexpected error: [Errno 
111] ECONNREFUSED

any help appreciated,

thank you





Michaël Van de Borne
R&D Engineer, SOA team, CETIC
Phone: +32 (0)71 49 07 45 Mobile: +32 (0)472 69 57 16, Skype: mikemowgli
www.cetic.be, rue des Frères Wright, 29/3, B-6041 Charleroi


Le 30/03/12 17:51, Guilherme Birk a écrit :
Michael, try to install nova-consoleauth, like Anthony said. The old 
error was fixed when I installed it, now I'm having another issue, but 
now I think it's related to my network.



Date: Fri, 30 Mar 2012 16:36:14 +0200
From: michael.vandebo...@cetic.be
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server

I've got the same problem.

When I try to connect to the instance using VNC through the dashboard, 
I've got this error. I then went in /var/log/nova/nova-xvpvncproxy.log 
and it contains nothing related to any attempt to get connected to any 
instance. It seems this nova-xvpvncproxy process doesn't notice anything.



When I try to connect using VNC through virt-manager, it works.


Le 30/03/12 15:50, Guilherme Birk a écrit :

Thanks for the reply.

I've added the flags that you mentioned on my nova.conf file. I'm
using a all in one installation, the flags are configured this way.
--vncserver_listen=127.0.0.1
--vncserver_proxyclient_address=127.0.0.1
--novncproxy_base_url=http://192.168.100.142:6080/vnc_auto.html

The public IP of the machine with the OpenStack installation is
192.168.100.142.
I've tried to access via browser the address
http://192.168.100.142:6080/vnc_auto.html from another machine,
but I got nothing.

I can ping and ssh my instances from the OpenStack machine but
can't use VNC tab at dashboard page from another machine. The
details and other pages from dashboard are fine.
Should I associate a public address for my instances? I'm using
just the private address at them (10.0.0.2, 10.0.0.3, ...).

I've restarted all the services and created new instances after
changing the nova.conf, but nothing has changed.

The error is a 404 not found. (*Error: *Unable to get VNC console
for instance "7376e17b-e329-4b8b-b5fc-076e8a80c058".)
The log from dashboards page looks like this:
- Page Not Found (404)
- Requested method: GET
- Requested URL:

*http://192.168.100.142/nova/instances_and_volumes/instances/7376e17b-e329-4b8b-b5fc-076e8a80c058/None*

This is the nova-api.log relative to the VNC atempt:
http://pastebin.com/wSuyctrg

Thanks for your time.
Guilherme Birk.

----------------
Date: Thu, 29 Mar 2012 13:06:37 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect
to server
From: sleepsonthefl...@gmail.com <mailto:sleepsonthefl...@gmail.com>
To: guib...@hotmail.com <mailto:guib...@hotmail.com>
CC: openstack@lists.launchpad.net
<

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Michaël Van de Borne]

I'm getting forward here.

I installed nova-consoleauth
apt-get install nova-consoleauth

and I get these settings in nova.conf:

--vnc_enabled=true
--vncproxy_url=http://172.22.22.1:6080
--vnc_console_proxy_url=http://172.22.22.1:6080
--vncserver_listen=10.18.9.1
--novncproxy_base_url=http://172.22.22.1:6080/vnc_auto.html
--xvpvncproxy_base_url=http://172.22.22.1:6081/console
--xvpvncproxy_host=172.22.22.1
--xvpvncproxy_port=6081

172.22.22.1 being the 'public' NIC, and 10.18.9.1 being the private one 
(for VM deployements)



Now, the command
nova get-vnc-console servername xvpvnc
gives me the url.

The error in the dashboard has changed. It now says it cannot establish 
connection to 172.22.22.1:6080 (which is the noVNC port whereas I'm 
using xvpvnc). So I guess I need to tell the dashboard to try on 6081. 
Which setting is that?



Michaël Van de Borne
R&D Engineer, SOA team, CETIC
Phone: +32 (0)71 49 07 45 Mobile: +32 (0)472 69 57 16, Skype: mikemowgli
www.cetic.be, rue des Frères Wright, 29/3, B-6041 Charleroi


Le 30/03/12 16:36, Michaël Van de Borne a écrit :

I've got the same problem.

When I try to connect to the instance using VNC through the dashboard, 
I've got this error. I then went in /var/log/nova/nova-xvpvncproxy.log 
and it contains nothing related to any attempt to get connected to any 
instance. It seems this nova-xvpvncproxy process doesn't notice anything.



When I try to connect using VNC through virt-manager, it works.


Le 30/03/12 15:50, Guilherme Birk a écrit :

Thanks for the reply.

I've added the flags that you mentioned on my nova.conf file. I'm 
using a all in one installation, the flags are configured this way.

--vncserver_listen=127.0.0.1
--vncserver_proxyclient_address=127.0.0.1
--novncproxy_base_url=http://192.168.100.142:6080/vnc_auto.html

The public IP of the machine with the OpenStack installation is 
192.168.100.142.
I've tried to access via browser the address 
http://192.168.100.142:6080/vnc_auto.html from another machine, but I 
got nothing.


I can ping and ssh my instances from the OpenStack machine but can't 
use VNC tab at dashboard page from another machine. The details and 
other pages from dashboard are fine.
Should I associate a public address for my instances? I'm using just 
the private address at them (10.0.0.2, 10.0.0.3, ...).


I've restarted all the services and created new instances after 
changing the nova.conf, but nothing has changed.


The error is a 404 not found. (*Error: *Unable to get VNC console for 
instance "7376e17b-e329-4b8b-b5fc-076e8a80c058".)

The log from dashboards page looks like this:
- Page Not Found (404)
- Requested method: GET
- Requested URL: 
*http://192.168.100.142/nova/instances_and_volumes/instances/7376e17b-e329-4b8b-b5fc-076e8a80c058/None*


This is the nova-api.log relative to the VNC atempt: 
http://pastebin.com/wSuyctrg


Thanks for your time.
Guilherme Birk.

------------
Date: Thu, 29 Mar 2012 13:06:37 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to 
server

From: sleepsonthefl...@gmail.com
To: guib...@hotmail.com
CC: openstack@lists.launchpad.net

How are you generating this link: 
http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None ? 



It looks like if horizon is behaving nicely the link would look like 
http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/vnc 
<http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None>


Also, could you pastie your nova-api.log somewhere?

A

On Thu, Mar 29, 2012 at 11:52 AM, Guilherme Birk <mailto:guib...@hotmail.com>> wrote:


I'm having problems with it too. I'm trying to connect on my
instances in the VNC tab at the dashboard, but I'm getting a 404
not found in the URL

http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None

Here is my nova-api.log. Looks like nova is having problems with
the POST at

http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action.

Any suggestions ?

From: luciantho...@hotmail.com <mailto:luciantho...@hotmail.com>
To: openstack@lists.launchpad.net
<mailto:openstack@lists.launchpad.net>
Date: Thu, 29 Mar 2012 18:07:59 +
Subject: [Openstack] Dashboard VNC Console failed to connect to
server


Hey guys,

I'm using Dashboard with a nova-compute installed in another
machine, but when I try access VNC Console I get the error
"failed to connect to server".

Here is the log -> http://pastebin.com/5DZMfiNE

Anyone alr

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Guilherme Birk]

Michael, try to install nova-consoleauth, like Anthony said. The old error was 
fixed when I installed it, now I'm having another issue, but now I think it's 
related to my network.

Date: Fri, 30 Mar 2012 16:36:14 +0200
From: michael.vandebo...@cetic.be
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server


  



  
  
I've got the same problem.



When I try to connect to the instance using VNC through the
dashboard, I've got this error. I then went in
/var/log/nova/nova-xvpvncproxy.log and it contains nothing related
to any attempt to get connected to any instance. It seems this
nova-xvpvncproxy process doesn't notice anything.





When I try to connect using VNC through virt-manager, it works.





Le 30/03/12 15:50, Guilherme Birk a écrit :

  
  
Thanks for the reply.



I've added the flags that you mentioned on my nova.conf file.
I'm using a all in one installation, the flags are configured
this way.

--vncserver_listen=127.0.0.1

--vncserver_proxyclient_address=127.0.0.1

--novncproxy_base_url=http://192.168.100.142:6080/vnc_auto.html



The public IP of the machine with the OpenStack installation is
192.168.100.142.

I've tried to access via browser the address
http://192.168.100.142:6080/vnc_auto.html from another machine,
but I got nothing.



I can ping and ssh my instances from the OpenStack machine but
can't use VNC tab at dashboard page from another machine. The
details and other pages from dashboard are fine.

Should I associate a public address for my instances? I'm using
just the private address at them (10.0.0.2, 10.0.0.3, ...).



I've restarted all the services and created new instances after
changing the nova.conf, but nothing has changed.



The error is a 404 not found. (Error: Unable
to get VNC console for instance
"7376e17b-e329-4b8b-b5fc-076e8a80c058".)

The log from dashboards page looks like this:

- Page Not Found (404)

- Requested method: GET

- Requested URL: 
http://192.168.100.142/nova/instances_and_volumes/instances/7376e17b-e329-4b8b-b5fc-076e8a80c058/None



This is the nova-api.log relative to the VNC atempt: 
http://pastebin.com/wSuyctrg



Thanks for your time.

Guilherme Birk.




  Date: Thu, 29 Mar 2012 13:06:37 -0700

  Subject: Re: [Openstack] Dashboard VNC Console failed to
  connect to server

  From: sleepsonthefl...@gmail.com

  To: guib...@hotmail.com

  CC: openstack@lists.launchpad.net

  

  How are you generating this link: 
http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
 ?
  


  
  It looks like if
horizon is behaving nicely the link would look like 
http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/vnc
  

  
  Also, could you pastie your nova-api.log somewhere?
  

  
  A
  

  
  
On Thu, Mar 29, 2012 at 11:52
  AM, Guilherme Birk 
  wrote:

  

  
I'm having problems with it too. I'm trying to
connect on my instances in the VNC tab at the
dashboard, but I'm getting a 404 not found in the
URL 
http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None



Here is my nova-api.log. Looks like nova is having
problems with the POST at 
http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action.



Any suggestions ?


  
From: luciantho...@hotmail.com

To: openstack@lists.launchpad.net

    Date: Thu, 29 Mar 2012 18:07:59 +

            Subject: [Openstack] Dashboard VNC Console
failed to connect to server
  


  

  
Hey
  guys,


  
I'm
using Dashboard with a 

Re: [Openstack] Dashboard VNC Console failed to connect to server

[David Kranz]

I am also having problems with vnc console but not using dashboard and 
of a different kind. First, the documentation says to use the vnc_redux 
branch but that is evidently diablo-compatible code. So I used master 
and did the same thing as devstack does (I think) and I can get a console


root@xg06:~/noVNC# nova get-vnc-console test novnc
+---+---+
|  Type |
Url|

+---+---+
| novnc | 
http://172.18.0.146:6080/vnc_auto.html?token=43971233-a806-4f01-96b1-8861c1dc7410 
|

+---+---+

but when I browse to that I get this from novnc log, and an error banner 
with "Websock error: [Object Event]"
If I do the same thing against devstack the log is different and it 
works. Any help would be appreciated.
Also, this stuff seems only semi-official with references to 
cloudbuilders git repos. Is it officially part of Essex?


 -David

multinode package deploy + noVNC from git
  1: 172.17.1.170: "GET 
/vnc_auto.html?token=43971233-a806-4f01-96b1-8861c1dc7410 HTTP/1.1" 200 -

  2: 172.17.1.170: new handler Process
  3: 172.17.1.170: new handler Process
  2: 172.17.1.170: "GET /include/plain.css HTTP/1.1" 200 -
  3: 172.17.1.170: "GET /include/vnc.js HTTP/1.1" 200 -
  4: 172.17.1.170: new handler Process
  5: 172.17.1.170: new handler Process
  6: 172.17.1.170: new handler Process
  4: 172.17.1.170: "GET /include/util.js HTTP/1.1" 200 -
  7: 172.17.1.170: new handler Process
  5: 172.17.1.170: "GET /include/webutil.js HTTP/1.1" 200 -
  8: 172.17.1.170: new handler Process
  6: 172.17.1.170: "GET /include/logo.js HTTP/1.1" 200 -
  7: 172.17.1.170: "GET /include/base64.js HTTP/1.1" 200 -
  8: 172.17.1.170: "GET /include/websock.js HTTP/1.1" 200 -
  9: 172.17.1.170: new handler Process
 10: 172.17.1.170: new handler Process
  9: 172.17.1.170: "GET /include/des.js HTTP/1.1" 200 -
 11: 172.17.1.170: new handler Process
 12: 172.17.1.170: new handler Process
 10: 172.17.1.170: "GET /include/input.js HTTP/1.1" 200 -
 11: 172.17.1.170: "GET /include/display.js HTTP/1.1" 200 -
 12: 172.17.1.170: "GET /include/rfb.js HTTP/1.1" 200 -
 13: 172.17.1.170: new handler Process
DIFFERENCE STARTS HERE
 14: 172.17.1.170: new handler Process
 13: 172.17.1.170: Python >= 2.6 and numpy module is required for 
HyBi-07 or greater

 14: 172.17.1.170: "GET /favicon.ico HTTP/1.1" 200 -


devstack: works
  1: 172.17.1.170: "GET 
/vnc_auto.html?token=e64e682e-5c69-42dd-8d78-01537b3d3223 HTTP/1.1" 200 -

  2: 172.17.1.170: new handler Process
  3: 172.17.1.170: new handler Process
  2: 172.17.1.170: "GET /include/plain.css HTTP/1.1" 200 -
  3: 172.17.1.170: "GET /include/vnc.js HTTP/1.1" 200 -
  4: 172.17.1.170: new handler Process
  5: 172.17.1.170: new handler Process
  6: 172.17.1.170: new handler Process
  4: 172.17.1.170: "GET /include/util.js HTTP/1.1" 200 -
  7: 172.17.1.170: new handler Process
  5: 172.17.1.170: "GET /include/webutil.js HTTP/1.1" 200 -
  8: 172.17.1.170: new handler Process
  6: 172.17.1.170: "GET /include/logo.js HTTP/1.1" 200 -
  9: 172.17.1.170: new handler Process
  7: 172.17.1.170: "GET /include/base64.js HTTP/1.1" 200 -
  8: 172.17.1.170: "GET /include/websock.js HTTP/1.1" 200 -
  9: 172.17.1.170: "GET /include/des.js HTTP/1.1" 200 -
 10: 172.17.1.170: new handler Process
 11: 172.17.1.170: new handler Process
 12: 172.17.1.170: new handler Process
 11: 172.17.1.170: "GET /include/display.js HTTP/1.1" 200 -
 10: 172.17.1.170: "GET /include/input.js HTTP/1.1" 200 -
 12: 172.17.1.170: "GET /include/rfb.js HTTP/1.1" 200 -
 13: 172.17.1.170: new handler Process
 13: 172.17.1.170: Plain non-SSL (ws://) WebSocket connection
 13: 172.17.1.170: Version hybi-08, base64: 'True'
 13: connecting to: 127.0.0.1:5900




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Michaël Van de Borne]

I've got the same problem.

When I try to connect to the instance using VNC through the dashboard, 
I've got this error. I then went in /var/log/nova/nova-xvpvncproxy.log 
and it contains nothing related to any attempt to get connected to any 
instance. It seems this nova-xvpvncproxy process doesn't notice anything.



When I try to connect using VNC through virt-manager, it works.


Le 30/03/12 15:50, Guilherme Birk a écrit :

Thanks for the reply.

I've added the flags that you mentioned on my nova.conf file. I'm 
using a all in one installation, the flags are configured this way.

--vncserver_listen=127.0.0.1
--vncserver_proxyclient_address=127.0.0.1
--novncproxy_base_url=http://192.168.100.142:6080/vnc_auto.html

The public IP of the machine with the OpenStack installation is 
192.168.100.142.
I've tried to access via browser the address 
http://192.168.100.142:6080/vnc_auto.html from another machine, but I 
got nothing.


I can ping and ssh my instances from the OpenStack machine but can't 
use VNC tab at dashboard page from another machine. The details and 
other pages from dashboard are fine.
Should I associate a public address for my instances? I'm using just 
the private address at them (10.0.0.2, 10.0.0.3, ...).


I've restarted all the services and created new instances after 
changing the nova.conf, but nothing has changed.


The error is a 404 not found. (*Error: *Unable to get VNC console for 
instance "7376e17b-e329-4b8b-b5fc-076e8a80c058".)

The log from dashboards page looks like this:
- Page Not Found (404)
- Requested method: GET
- Requested URL: 
*http://192.168.100.142/nova/instances_and_volumes/instances/7376e17b-e329-4b8b-b5fc-076e8a80c058/None*


This is the nova-api.log relative to the VNC atempt: 
http://pastebin.com/wSuyctrg


Thanks for your time.
Guilherme Birk.

----
Date: Thu, 29 Mar 2012 13:06:37 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
From: sleepsonthefl...@gmail.com
To: guib...@hotmail.com
CC: openstack@lists.launchpad.net

How are you generating this link: 
http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None ? 



It looks like if horizon is behaving nicely the link would look like 
http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/vnc 
<http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None>


Also, could you pastie your nova-api.log somewhere?

A

On Thu, Mar 29, 2012 at 11:52 AM, Guilherme Birk <mailto:guib...@hotmail.com>> wrote:


I'm having problems with it too. I'm trying to connect on my
instances in the VNC tab at the dashboard, but I'm getting a 404
not found in the URL

http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None

Here is my nova-api.log. Looks like nova is having problems with
the POST at

http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action.

Any suggestions ?

From: luciantho...@hotmail.com <mailto:luciantho...@hotmail.com>
To: openstack@lists.launchpad.net
<mailto:openstack@lists.launchpad.net>
    Date: Thu, 29 Mar 2012 18:07:59 +
Subject: [Openstack] Dashboard VNC Console failed to connect to server


Hey guys,

I'm using Dashboard with a nova-compute installed in another
machine, but when I try access VNC Console I get the error "failed
to connect to server".

Here is the log -> http://pastebin.com/5DZMfiNE

Anyone already saw this trouble?


*Lucian Thomaz *


___ Mailing list:
https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack> Post to :
openstack@lists.launchpad.net
<mailto:openstack@lists.launchpad.net> Unsubscribe :
https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack> More help :
https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack>
Post to : openstack@lists.launchpad.net
<mailto:openstack@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack>
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp
__

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Anthony Young]

It does not look like you are running nova-consoleauth.  The vnc proxies
use that service to verify incoming tokens.  Try running that and see if
that fixes things.

A

On Fri, Mar 30, 2012 at 6:50 AM, Guilherme Birk  wrote:

>  Thanks for the reply.
>
> I've added the flags that you mentioned on my nova.conf file. I'm using a
> all in one installation, the flags are configured this way.
> --vncserver_listen=127.0.0.1
> --vncserver_proxyclient_address=127.0.0.1
> --novncproxy_base_url=http://192.168.100.142:6080/vnc_auto.html
>
> The public IP of the machine with the OpenStack installation is
> 192.168.100.142.
> I've tried to access via browser the address
> http://192.168.100.142:6080/vnc_auto.html from another machine, but I got
> nothing.
>
> I can ping and ssh my instances from the OpenStack machine but can't use
> VNC tab at dashboard page from another machine. The details and other pages
> from dashboard are fine.
> Should I associate a public address for my instances? I'm using just the
> private address at them (10.0.0.2, 10.0.0.3, ...).
>
> I've restarted all the services and created new instances after changing
> the nova.conf, but nothing has changed.
>
> The error is a 404 not found. (*Error: *Unable to get VNC console for
> instance "7376e17b-e329-4b8b-b5fc-076e8a80c058".)
> The log from dashboards page looks like this:
> - Page Not Found (404)
> - Requested method: GET
> - Requested URL: *
> http://192.168.100.142/nova/instances_and_volumes/instances/7376e17b-e329-4b8b-b5fc-076e8a80c058/None
> *
>
> This is the nova-api.log relative to the VNC atempt:
> http://pastebin.com/wSuyctrg
>
> Thanks for your time.
> Guilherme Birk.
>
> --
> Date: Thu, 29 Mar 2012 13:06:37 -0700
> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
> From: sleepsonthefl...@gmail.com
> To: guib...@hotmail.com
> CC: openstack@lists.launchpad.net
>
>
> How are you generating this link:
> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>  ?
>
> It looks like if horizon is behaving nicely the link would look like
> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/vnc<http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None>
>
> Also, could you pastie your nova-api.log somewhere?
>
> A
>
> On Thu, Mar 29, 2012 at 11:52 AM, Guilherme Birk wrote:
>
>  I'm having problems with it too. I'm trying to connect on my instances in
> the VNC tab at the dashboard, but I'm getting a 404 not found in the URL
> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>
> Here is my nova-api.log. Looks like nova is having problems with the POST
> at
> http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action
> .
>
> Any suggestions ?
> --
> From: luciantho...@hotmail.com
> To: openstack@lists.launchpad.net
> Date: Thu, 29 Mar 2012 18:07:59 +
> Subject: [Openstack] Dashboard VNC Console failed to connect to server
>
>
>  Hey guys,
>
> I'm using Dashboard with a nova-compute installed in another machine, but
> when I try access VNC Console I get the error "failed to connect to server".
>
> Here is the log -> http://pastebin.com/5DZMfiNE
>
> Anyone already saw this trouble?
>
>
> *Lucian Thomaz *
>
>
> ___ Mailing list:
> https://launchpad.net/~openstack Post to : 
> openstack@lists.launchpad.netUnsubscribe :
> https://launchpad.net/~openstack More help :
> https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Guilherme Birk]

Thanks for the reply.

I've added the flags that you mentioned on my nova.conf file. I'm using a all 
in one installation, the flags are configured this way.
--vncserver_listen=127.0.0.1
--vncserver_proxyclient_address=127.0.0.1
--novncproxy_base_url=http://192.168.100.142:6080/vnc_auto.html

The public IP of the machine with the OpenStack installation is 192.168.100.142.
I've tried to access via browser the address 
http://192.168.100.142:6080/vnc_auto.html from another machine, but I got 
nothing.

I can ping and ssh my instances from the OpenStack machine but can't use VNC 
tab at dashboard page from another machine. The details and other pages from 
dashboard are fine.
Should I associate a public address for my instances? I'm using just the 
private address at them (10.0.0.2, 10.0.0.3, ...).

I've restarted all the services and created new instances after changing the 
nova.conf, but nothing has changed.

The error is a 404 not found. (Error: Unable to get VNC console for instance 
"7376e17b-e329-4b8b-b5fc-076e8a80c058".)
The log from dashboards page looks like this:
- Page Not Found (404)
- Requested method: GET
- Requested URL: 
http://192.168.100.142/nova/instances_and_volumes/instances/7376e17b-e329-4b8b-b5fc-076e8a80c058/None

This is the nova-api.log relative to the VNC atempt: 
http://pastebin.com/wSuyctrg

Thanks for your time.
Guilherme Birk.

Date: Thu, 29 Mar 2012 13:06:37 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
From: sleepsonthefl...@gmail.com
To: guib...@hotmail.com
CC: openstack@lists.launchpad.net

How are you generating this link: 
http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
 ?

It looks like if horizon is behaving nicely the link would look like 
http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/vnc

Also, could you pastie your nova-api.log somewhere?
A
On Thu, Mar 29, 2012 at 11:52 AM, Guilherme Birk  wrote:





I'm having problems with it too. I'm trying to connect on my instances in the 
VNC tab at the dashboard, but I'm getting a 404 not found in the URL 
http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None


Here is my nova-api.log. Looks like nova is having problems with the POST at 
http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action.


Any suggestions ?
From: luciantho...@hotmail.com
To: openstack@lists.launchpad.net

Date: Thu, 29 Mar 2012 18:07:59 +0000
Subject: [Openstack] Dashboard VNC Console failed to connect to server







Hey guys,
I'm using Dashboard with a nova-compute installed in another machine, but when 
I try access VNC Console I get the error "failed to connect to server".

Here is the log -> http://pastebin.com/5DZMfiNE

Anyone already saw this trouble?


Lucian Thomaz 

  

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp   
  

___

Mailing list: https://launchpad.net/~openstack

Post to : openstack@lists.launchpad.net

Unsubscribe : https://launchpad.net/~openstack

More help   : https://help.launchpad.net/ListHelp



  ___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Anthony Young]

Your existing instance likely still has the wrong vncserver listen address
baked into its libvirt.xml, which you would have to update manually.  New
instances should be ok.

A

On Thu, Mar 29, 2012 at 3:15 PM, Joseph Heck  wrote:

> Well, even with the change, I'm not getting the live VNCconsole.
> Javascript all comes up happy, but fails to connect - same errors. Anything
> that I should query in the javascript console that will tell me what's
> happening? Or logs form the novnc process?
>
> -joe
>
> On Mar 29, 2012, at 3:02 PM, Joseph Heck wrote:
>
> thank you - morons-r-us is trying that suggestion right now...
>
> -joe
>
> On Mar 29, 2012, at 3:01 PM, Anthony Young wrote:
>
> Joe - looks like it could just be a typo:
>
> 1
> 2
> 3
>
> --vncserver_list=172.18.1.1--vncserver_proxyclient_address=172.18.1.1--novncproxy_base_url=http://172.17.1.50:6080/vnc_auto.html
>
>
>
> that should be vncserver_listen
>
> A
>
> On Thu, Mar 29, 2012 at 2:42 PM, Joseph Heck  wrote:
>
>> http://pastie.org/3694439
>>
>> The compute host is 172.18.1.1 with my instance (TTY, named "zerglet")
>> The nova vncproxy code is running at 172.17.1.50 - both have direct
>> access to each other - pingable, etc. 172.17.1.50 is the nova-api host for
>> this setup as well
>>
>> -joe
>>
>> On Mar 29, 2012, at 2:35 PM, Anthony Young wrote:
>>
>> Joe - can you pastie your nova.conf from your compute host?  The most
>> relevant flags are vncserver_proxyclient_address and  vncserver_listen
>>
>> On Thu, Mar 29, 2012 at 2:21 PM, Joseph Heck  wrote:
>>
>>> Hey Tony,
>>>
>>> Slightly related - I'm getting a valid link form the dashboard that gets
>>> to VNCProxy and such, but the page that comes active reports a "Server
>>> timeout". Any idea how to diagnose this and what's happened/not responded?
>>>
>>>
>>> http://172.17.1.50:6080/vnc_auto.html?token=f96cf65b-1a2f-415c-97f7-90da7cdc102a&title=zerglet(b13812ac-8310-49ea-97e6-50ff062754af)
>>>
>>> In the javascript console, here's what I'm seeing:
>>>
>>> New state 'loaded', was 'disconnected'. Msg: noVNC ready: native
>>> WebSockets, createImageData rendering
>>>  util.js:71 <http://172.17.1.50:6080/include/util.js>New state
>>> 'connect', was 'loaded'.
>>>  util.js:71 <http://172.17.1.50:6080/include/util.js>New state
>>> 'ProtocolVersion', was 'connect'. Msg: Starting VNC handshake
>>>  util.js:72 <http://172.17.1.50:6080/include/util.js>New state
>>> 'failed', was 'ProtocolVersion'. Msg: Failed to connect to server
>>>  util.js:71 <http://172.17.1.50:6080/include/util.js>New state
>>> 'failed', was 'failed'.
>>>
>>>
>>> Any ideas?
>>>
>>> -joe
>>>
>>>
>>> On Mar 29, 2012, at 1:06 PM, Anthony Young wrote:
>>>
>>> How are you generating this link:
>>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>>>  ?
>>>
>>> It looks like if horizon is behaving nicely the link would look like
>>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/vnc<http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None>
>>>
>>> Also, could you pastie your nova-api.log somewhere?
>>>
>>> A
>>>
>>> On Thu, Mar 29, 2012 at 11:52 AM, Guilherme Birk wrote:
>>>
>>>>  I'm having problems with it too. I'm trying to connect on my instances
>>>> in the VNC tab at the dashboard, but I'm getting a 404 not found in the URL
>>>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>>>>
>>>> Here is my nova-api.log. Looks like nova is having problems with the
>>>> POST at
>>>> http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action
>>>> .
>>>>
>>>> Any suggestions ?
>>>> --
>>>> From: luciantho...@hotmail.com
>>>> To: openstack@lists.launchpad.net
>>>> Date: Thu, 29 Mar 2012 18:07:59 +
>>>> Subject: [Openstack] Dashboard VNC Console failed to connect to server
>>>>
>>>>
>>>

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Joseph Heck]

Well, even with the change, I'm not getting the live VNCconsole. Javascript all 
comes up happy, but fails to connect - same errors. Anything that I should 
query in the javascript console that will tell me what's happening? Or logs 
form the novnc process?

-joe

On Mar 29, 2012, at 3:02 PM, Joseph Heck wrote:

> thank you - morons-r-us is trying that suggestion right now...
> 
> -joe
> 
> On Mar 29, 2012, at 3:01 PM, Anthony Young wrote:
> 
>> Joe - looks like it could just be a typo:
>> 
>> 1
>> 2
>> 3
>> --vncserver_list=172.18.1.1
>> --vncserver_proxyclient_address=172.18.1.1
>> --novncproxy_base_url=http://172.17.1.50:6080/vnc_auto.html
>> 
>> 
>> that should be vncserver_listen
>> 
>> A
>> 
>> On Thu, Mar 29, 2012 at 2:42 PM, Joseph Heck  wrote:
>> http://pastie.org/3694439
>> 
>> The compute host is 172.18.1.1 with my instance (TTY, named "zerglet")
>> The nova vncproxy code is running at 172.17.1.50 - both have direct access 
>> to each other - pingable, etc. 172.17.1.50 is the nova-api host for this 
>> setup as well
>> 
>> -joe
>> 
>> On Mar 29, 2012, at 2:35 PM, Anthony Young wrote:
>>> Joe - can you pastie your nova.conf from your compute host?  The most 
>>> relevant flags are vncserver_proxyclient_address and  vncserver_listen
>>> 
>>> On Thu, Mar 29, 2012 at 2:21 PM, Joseph Heck  wrote:
>>> Hey Tony,
>>> 
>>> Slightly related - I'm getting a valid link form the dashboard that gets to 
>>> VNCProxy and such, but the page that comes active reports a "Server 
>>> timeout". Any idea how to diagnose this and what's happened/not responded?
>>> 
>>> http://172.17.1.50:6080/vnc_auto.html?token=f96cf65b-1a2f-415c-97f7-90da7cdc102a&title=zerglet(b13812ac-8310-49ea-97e6-50ff062754af)
>>> 
>>> In the javascript console, here's what I'm seeing:
>>> 
>>> New state 'loaded', was 'disconnected'. Msg: noVNC ready: native 
>>> WebSockets, createImageData rendering
>>> util.js:71New state 'connect', was 'loaded'.
>>> util.js:71New state 'ProtocolVersion', was 'connect'. Msg: Starting VNC 
>>> handshake
>>> util.js:72New state 'failed', was 'ProtocolVersion'. Msg: Failed to connect 
>>> to server
>>> util.js:71New state 'failed', was 'failed'.
>>> 
>>> 
>>> Any ideas?
>>> 
>>> -joe
>>> 
>>> 
>>> On Mar 29, 2012, at 1:06 PM, Anthony Young wrote:
>>> 
>>>> How are you generating this link: 
>>>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>>>>  ?
>>>> 
>>>> It looks like if horizon is behaving nicely the link would look like 
>>>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/vnc
>>>> 
>>>> Also, could you pastie your nova-api.log somewhere?
>>>> 
>>>> A
>>>> 
>>>> On Thu, Mar 29, 2012 at 11:52 AM, Guilherme Birk  
>>>> wrote:
>>>> I'm having problems with it too. I'm trying to connect on my instances in 
>>>> the VNC tab at the dashboard, but I'm getting a 404 not found in the URL 
>>>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>>>> 
>>>> Here is my nova-api.log. Looks like nova is having problems with the POST 
>>>> at 
>>>> http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action.
>>>> 
>>>> Any suggestions ?
>>>> From: luciantho...@hotmail.com
>>>> To: openstack@lists.launchpad.net
>>>> Date: Thu, 29 Mar 2012 18:07:59 +
>>>> Subject: [Openstack] Dashboard VNC Console failed to connect to server
>>>> 
>>>> 
>>>> Hey guys,
>>>> 
>>>> I'm using Dashboard with a nova-compute installed in another machine, but 
>>>> when I try access VNC Console I get the error "failed to connect to 
>>>> server".
>>>> 
>>>> Here is the log -> http://pastebin.com/5DZMfiNE
>>>> 
>>>> Anyone already saw this trouble?
>>>> 
>>>> 
>>>> Lucian Thomaz 
>>>> 
>>>> 
>>>> ___ Mailing list: 
>>>> https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net 
>>>> Unsubscribe : https://launchpad.net/~openstack More help : 
>>>> https://help.launchpad.net/ListHelp
>>>> 
>>>> ___
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>> 
>>>> 
>>>> ___
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>> 
>>> 
>> 
>> 
> 

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Joseph Heck]

thank you - morons-r-us is trying that suggestion right now...

-joe

On Mar 29, 2012, at 3:01 PM, Anthony Young wrote:

> Joe - looks like it could just be a typo:
> 
> 1
> 2
> 3
> --vncserver_list=172.18.1.1
> --vncserver_proxyclient_address=172.18.1.1
> --novncproxy_base_url=http://172.17.1.50:6080/vnc_auto.html
> 
> 
> that should be vncserver_listen
> 
> A
> 
> On Thu, Mar 29, 2012 at 2:42 PM, Joseph Heck  wrote:
> http://pastie.org/3694439
> 
> The compute host is 172.18.1.1 with my instance (TTY, named "zerglet")
> The nova vncproxy code is running at 172.17.1.50 - both have direct access to 
> each other - pingable, etc. 172.17.1.50 is the nova-api host for this setup 
> as well
> 
> -joe
> 
> On Mar 29, 2012, at 2:35 PM, Anthony Young wrote:
>> Joe - can you pastie your nova.conf from your compute host?  The most 
>> relevant flags are vncserver_proxyclient_address and  vncserver_listen
>> 
>> On Thu, Mar 29, 2012 at 2:21 PM, Joseph Heck  wrote:
>> Hey Tony,
>> 
>> Slightly related - I'm getting a valid link form the dashboard that gets to 
>> VNCProxy and such, but the page that comes active reports a "Server 
>> timeout". Any idea how to diagnose this and what's happened/not responded?
>> 
>> http://172.17.1.50:6080/vnc_auto.html?token=f96cf65b-1a2f-415c-97f7-90da7cdc102a&title=zerglet(b13812ac-8310-49ea-97e6-50ff062754af)
>> 
>> In the javascript console, here's what I'm seeing:
>> 
>> New state 'loaded', was 'disconnected'. Msg: noVNC ready: native WebSockets, 
>> createImageData rendering
>> util.js:71New state 'connect', was 'loaded'.
>> util.js:71New state 'ProtocolVersion', was 'connect'. Msg: Starting VNC 
>> handshake
>> util.js:72New state 'failed', was 'ProtocolVersion'. Msg: Failed to connect 
>> to server
>> util.js:71New state 'failed', was 'failed'.
>> 
>> 
>> Any ideas?
>> 
>> -joe
>> 
>> 
>> On Mar 29, 2012, at 1:06 PM, Anthony Young wrote:
>> 
>>> How are you generating this link: 
>>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>>>  ?
>>> 
>>> It looks like if horizon is behaving nicely the link would look like 
>>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/vnc
>>> 
>>> Also, could you pastie your nova-api.log somewhere?
>>> 
>>> A
>>> 
>>> On Thu, Mar 29, 2012 at 11:52 AM, Guilherme Birk  
>>> wrote:
>>> I'm having problems with it too. I'm trying to connect on my instances in 
>>> the VNC tab at the dashboard, but I'm getting a 404 not found in the URL 
>>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>>> 
>>> Here is my nova-api.log. Looks like nova is having problems with the POST 
>>> at 
>>> http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action.
>>> 
>>> Any suggestions ?
>>> From: luciantho...@hotmail.com
>>> To: openstack@lists.launchpad.net
>>> Date: Thu, 29 Mar 2012 18:07:59 +
>>> Subject: [Openstack] Dashboard VNC Console failed to connect to server
>>> 
>>> 
>>> Hey guys,
>>> 
>>> I'm using Dashboard with a nova-compute installed in another machine, but 
>>> when I try access VNC Console I get the error "failed to connect to server".
>>> 
>>> Here is the log -> http://pastebin.com/5DZMfiNE
>>> 
>>> Anyone already saw this trouble?
>>> 
>>> 
>>> Lucian Thomaz 
>>> 
>>> 
>>> ___ Mailing list: 
>>> https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net 
>>> Unsubscribe : https://launchpad.net/~openstack More help : 
>>> https://help.launchpad.net/ListHelp
>>> 
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>> 
>>> 
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>> 
>> 
> 
> 

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Anthony Young]

Joe - looks like it could just be a typo:

1
2
3

--vncserver_list=172.18.1.1--vncserver_proxyclient_address=172.18.1.1--novncproxy_base_url=http://172.17.1.50:6080/vnc_auto.html



that should be vncserver_listen

A

On Thu, Mar 29, 2012 at 2:42 PM, Joseph Heck  wrote:

> http://pastie.org/3694439
>
> The compute host is 172.18.1.1 with my instance (TTY, named "zerglet")
> The nova vncproxy code is running at 172.17.1.50 - both have direct access
> to each other - pingable, etc. 172.17.1.50 is the nova-api host for this
> setup as well
>
> -joe
>
> On Mar 29, 2012, at 2:35 PM, Anthony Young wrote:
>
> Joe - can you pastie your nova.conf from your compute host?  The most
> relevant flags are vncserver_proxyclient_address and  vncserver_listen
>
> On Thu, Mar 29, 2012 at 2:21 PM, Joseph Heck  wrote:
>
>> Hey Tony,
>>
>> Slightly related - I'm getting a valid link form the dashboard that gets
>> to VNCProxy and such, but the page that comes active reports a "Server
>> timeout". Any idea how to diagnose this and what's happened/not responded?
>>
>>
>> http://172.17.1.50:6080/vnc_auto.html?token=f96cf65b-1a2f-415c-97f7-90da7cdc102a&title=zerglet(b13812ac-8310-49ea-97e6-50ff062754af)
>>
>> In the javascript console, here's what I'm seeing:
>>
>> New state 'loaded', was 'disconnected'. Msg: noVNC ready: native
>> WebSockets, createImageData rendering
>>  util.js:71 <http://172.17.1.50:6080/include/util.js>New state
>> 'connect', was 'loaded'.
>>  util.js:71 <http://172.17.1.50:6080/include/util.js>New state
>> 'ProtocolVersion', was 'connect'. Msg: Starting VNC handshake
>>  util.js:72 <http://172.17.1.50:6080/include/util.js>New state 'failed',
>> was 'ProtocolVersion'. Msg: Failed to connect to server
>>  util.js:71 <http://172.17.1.50:6080/include/util.js>New state 'failed',
>> was 'failed'.
>>
>>
>> Any ideas?
>>
>> -joe
>>
>>
>> On Mar 29, 2012, at 1:06 PM, Anthony Young wrote:
>>
>> How are you generating this link:
>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>>  ?
>>
>> It looks like if horizon is behaving nicely the link would look like
>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/vnc<http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None>
>>
>> Also, could you pastie your nova-api.log somewhere?
>>
>> A
>>
>> On Thu, Mar 29, 2012 at 11:52 AM, Guilherme Birk wrote:
>>
>>>  I'm having problems with it too. I'm trying to connect on my instances
>>> in the VNC tab at the dashboard, but I'm getting a 404 not found in the URL
>>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>>>
>>> Here is my nova-api.log. Looks like nova is having problems with the
>>> POST at
>>> http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action
>>> .
>>>
>>> Any suggestions ?
>>> --
>>> From: luciantho...@hotmail.com
>>> To: openstack@lists.launchpad.net
>>> Date: Thu, 29 Mar 2012 18:07:59 +
>>> Subject: [Openstack] Dashboard VNC Console failed to connect to server
>>>
>>>
>>>  Hey guys,
>>>
>>> I'm using Dashboard with a nova-compute installed in another machine,
>>> but when I try access VNC Console I get the error "failed to connect to
>>> server".
>>>
>>> Here is the log -> http://pastebin.com/5DZMfiNE
>>>
>>> Anyone already saw this trouble?
>>>
>>>
>>> *Lucian Thomaz *
>>>
>>>
>>> ___ Mailing list:
>>> https://launchpad.net/~openstack Post to : 
>>> openstack@lists.launchpad.netUnsubscribe :
>>> https://launchpad.net/~openstack More help :
>>> https://help.launchpad.net/ListHelp
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Joseph Heck]

http://pastie.org/3694439

The compute host is 172.18.1.1 with my instance (TTY, named "zerglet")
The nova vncproxy code is running at 172.17.1.50 - both have direct access to 
each other - pingable, etc. 172.17.1.50 is the nova-api host for this setup as 
well

-joe

On Mar 29, 2012, at 2:35 PM, Anthony Young wrote:
> Joe - can you pastie your nova.conf from your compute host?  The most 
> relevant flags are vncserver_proxyclient_address and  vncserver_listen
> 
> On Thu, Mar 29, 2012 at 2:21 PM, Joseph Heck  wrote:
> Hey Tony,
> 
> Slightly related - I'm getting a valid link form the dashboard that gets to 
> VNCProxy and such, but the page that comes active reports a "Server timeout". 
> Any idea how to diagnose this and what's happened/not responded?
> 
> http://172.17.1.50:6080/vnc_auto.html?token=f96cf65b-1a2f-415c-97f7-90da7cdc102a&title=zerglet(b13812ac-8310-49ea-97e6-50ff062754af)
> 
> In the javascript console, here's what I'm seeing:
> 
> New state 'loaded', was 'disconnected'. Msg: noVNC ready: native WebSockets, 
> createImageData rendering
> util.js:71New state 'connect', was 'loaded'.
> util.js:71New state 'ProtocolVersion', was 'connect'. Msg: Starting VNC 
> handshake
> util.js:72New state 'failed', was 'ProtocolVersion'. Msg: Failed to connect 
> to server
> util.js:71New state 'failed', was 'failed'.
> 
> 
> Any ideas?
> 
> -joe
> 
> 
> On Mar 29, 2012, at 1:06 PM, Anthony Young wrote:
> 
>> How are you generating this link: 
>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>>  ?
>> 
>> It looks like if horizon is behaving nicely the link would look like 
>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/vnc
>> 
>> Also, could you pastie your nova-api.log somewhere?
>> 
>> A
>> 
>> On Thu, Mar 29, 2012 at 11:52 AM, Guilherme Birk  wrote:
>> I'm having problems with it too. I'm trying to connect on my instances in 
>> the VNC tab at the dashboard, but I'm getting a 404 not found in the URL 
>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>> 
>> Here is my nova-api.log. Looks like nova is having problems with the POST at 
>> http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action.
>> 
>> Any suggestions ?
>> From: luciantho...@hotmail.com
>> To: openstack@lists.launchpad.net
>> Date: Thu, 29 Mar 2012 18:07:59 +
>> Subject: [Openstack] Dashboard VNC Console failed to connect to server
>> 
>> 
>> Hey guys,
>> 
>> I'm using Dashboard with a nova-compute installed in another machine, but 
>> when I try access VNC Console I get the error "failed to connect to server".
>> 
>> Here is the log -> http://pastebin.com/5DZMfiNE
>> 
>> Anyone already saw this trouble?
>> 
>> 
>> Lucian Thomaz 
>> 
>> 
>> ___ Mailing list: 
>> https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net 
>> Unsubscribe : https://launchpad.net/~openstack More help : 
>> https://help.launchpad.net/ListHelp
>> 
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>> 
>> 
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
> 
> 

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Anthony Young]

Joe - can you pastie your nova.conf from your compute host?  The most
relevant flags are vncserver_proxyclient_address and  vncserver_listen

On Thu, Mar 29, 2012 at 2:21 PM, Joseph Heck  wrote:

> Hey Tony,
>
> Slightly related - I'm getting a valid link form the dashboard that gets
> to VNCProxy and such, but the page that comes active reports a "Server
> timeout". Any idea how to diagnose this and what's happened/not responded?
>
>
> http://172.17.1.50:6080/vnc_auto.html?token=f96cf65b-1a2f-415c-97f7-90da7cdc102a&title=zerglet(b13812ac-8310-49ea-97e6-50ff062754af)
>
> In the javascript console, here's what I'm seeing:
>
> New state 'loaded', was 'disconnected'. Msg: noVNC ready: native
> WebSockets, createImageData rendering
> util.js:71 <http://172.17.1.50:6080/include/util.js>New state 'connect',
> was 'loaded'.
> util.js:71 <http://172.17.1.50:6080/include/util.js>New state
> 'ProtocolVersion', was 'connect'. Msg: Starting VNC handshake
> util.js:72 <http://172.17.1.50:6080/include/util.js>New state 'failed',
> was 'ProtocolVersion'. Msg: Failed to connect to server
> util.js:71 <http://172.17.1.50:6080/include/util.js>New state 'failed',
> was 'failed'.
>
>
> Any ideas?
>
> -joe
>
>
> On Mar 29, 2012, at 1:06 PM, Anthony Young wrote:
>
> How are you generating this link:
> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>  ?
>
> It looks like if horizon is behaving nicely the link would look like
> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/vnc<http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None>
>
> Also, could you pastie your nova-api.log somewhere?
>
> A
>
> On Thu, Mar 29, 2012 at 11:52 AM, Guilherme Birk wrote:
>
>>  I'm having problems with it too. I'm trying to connect on my instances
>> in the VNC tab at the dashboard, but I'm getting a 404 not found in the URL
>> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>>
>> Here is my nova-api.log. Looks like nova is having problems with the POST
>> at
>> http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action
>> .
>>
>> Any suggestions ?
>> --
>> From: luciantho...@hotmail.com
>> To: openstack@lists.launchpad.net
>> Date: Thu, 29 Mar 2012 18:07:59 +
>> Subject: [Openstack] Dashboard VNC Console failed to connect to server
>>
>>
>>  Hey guys,
>>
>> I'm using Dashboard with a nova-compute installed in another machine, but
>> when I try access VNC Console I get the error "failed to connect to server".
>>
>> Here is the log -> http://pastebin.com/5DZMfiNE
>>
>> Anyone already saw this trouble?
>>
>>
>> *Lucian Thomaz *
>>
>>
>> ___ Mailing list:
>> https://launchpad.net/~openstack Post to : 
>> openstack@lists.launchpad.netUnsubscribe :
>> https://launchpad.net/~openstack More help :
>> https://help.launchpad.net/ListHelp
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Joseph Heck]

Hey Tony,

Slightly related - I'm getting a valid link form the dashboard that gets to 
VNCProxy and such, but the page that comes active reports a "Server timeout". 
Any idea how to diagnose this and what's happened/not responded?

http://172.17.1.50:6080/vnc_auto.html?token=f96cf65b-1a2f-415c-97f7-90da7cdc102a&title=zerglet(b13812ac-8310-49ea-97e6-50ff062754af)

In the javascript console, here's what I'm seeing:

New state 'loaded', was 'disconnected'. Msg: noVNC ready: native WebSockets, 
createImageData rendering
util.js:71New state 'connect', was 'loaded'.
util.js:71New state 'ProtocolVersion', was 'connect'. Msg: Starting VNC 
handshake
util.js:72New state 'failed', was 'ProtocolVersion'. Msg: Failed to connect to 
server
util.js:71New state 'failed', was 'failed'.


Any ideas?

-joe


On Mar 29, 2012, at 1:06 PM, Anthony Young wrote:

> How are you generating this link: 
> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>  ?
> 
> It looks like if horizon is behaving nicely the link would look like 
> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/vnc
> 
> Also, could you pastie your nova-api.log somewhere?
> 
> A
> 
> On Thu, Mar 29, 2012 at 11:52 AM, Guilherme Birk  wrote:
> I'm having problems with it too. I'm trying to connect on my instances in the 
> VNC tab at the dashboard, but I'm getting a 404 not found in the URL 
> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
> 
> Here is my nova-api.log. Looks like nova is having problems with the POST at 
> http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action.
> 
> Any suggestions ?
> From: luciantho...@hotmail.com
> To: openstack@lists.launchpad.net
> Date: Thu, 29 Mar 2012 18:07:59 +
> Subject: [Openstack] Dashboard VNC Console failed to connect to server
> 
> 
> Hey guys,
> 
> I'm using Dashboard with a nova-compute installed in another machine, but 
> when I try access VNC Console I get the error "failed to connect to server".
> 
> Here is the log -> http://pastebin.com/5DZMfiNE
> 
> Anyone already saw this trouble?
> 
> 
> Lucian Thomaz 
> 
> 
> ___ Mailing list: 
> https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net 
> Unsubscribe : https://launchpad.net/~openstack More help : 
> https://help.launchpad.net/ListHelp
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Anthony Young]

How are you generating this link:
http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
 ?

It looks like if horizon is behaving nicely the link would look like
http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/vnc<http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None>

Also, could you pastie your nova-api.log somewhere?

A

On Thu, Mar 29, 2012 at 11:52 AM, Guilherme Birk wrote:

>  I'm having problems with it too. I'm trying to connect on my instances in
> the VNC tab at the dashboard, but I'm getting a 404 not found in the URL
> http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None
>
> Here is my nova-api.log. Looks like nova is having problems with the POST
> at
> http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action
> .
>
> Any suggestions ?
> --
> From: luciantho...@hotmail.com
> To: openstack@lists.launchpad.net
> Date: Thu, 29 Mar 2012 18:07:59 +
> Subject: [Openstack] Dashboard VNC Console failed to connect to server
>
>
>  Hey guys,
>
> I'm using Dashboard with a nova-compute installed in another machine, but
> when I try access VNC Console I get the error "failed to connect to server".
>
> Here is the log -> http://pastebin.com/5DZMfiNE
>
> Anyone already saw this trouble?
>
>
> *Lucian Thomaz *
>
>
> ___ Mailing list:
> https://launchpad.net/~openstack Post to : 
> openstack@lists.launchpad.netUnsubscribe :
> https://launchpad.net/~openstack More help :
> https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Anthony Young]

Here are several flags that you must set on your compute host for a multi
host deploy:


   - :option:`--vncserver_listen`  -
   defaults to 127.0.0.1 This is the address that vncservers will bind, and
   should be overridden in production deployments as a private address.
   Applies to libvirt only. For multi-host libvirt deployments this should be
   set to a host management ip on the same network as the proxies.
   - 
:option:`--vncserver_proxyclient_address`
-
   defaults to 127.0.0.1 This is the address of the compute host that nova
   will instruct proxies to use when connecting to instance vncservers. For
   all-in-one xen server domU deployments this can be set to 169.254.0.1. For
   multi-host xen server domU deployments this can be set to a dom0 management
   ip on the same network as the proxies. For multi-host libvirt deployments
   this can be set to a host management ip on the same network as the proxies.
   - :option:`--novncproxy_base_url=[base url for client
connections]` -
   this is the public base url to which clients will connect. "?token=abc"
   will be added to this url for the purposes of auth. When using the system
   as described in this document, an appropriate value is "
   http://$SERVICE_HOST:6080/vnc_auto.html"; where SERVICE_HOST is a public
   hostname.

Suppose you have 2 servers, APISERVER and COMPUTESERVER:

APISERVER:
public hostname = my.server.com
management ip = 192.168.1.1
public ip = 172.24.4.1

COMPUTESERVER:
management ip = 192.168.1.2

Your nova.conf con COMPUTESERVER would need the following flags:

novncproxy_base_url=http://my.server.com:6080/vnc_auto.html or
novncproxy_base_url=http://172.24.4.1:6080/vnc_auto.html
vncserver_proxyclient_address=192.168.1.2
vncserver_listen=192.168.1.2

Note that novncproxy_base_url references a public ip or hostname (so
clients can connect), while the other flags use private ips.

For more info:
https://github.com/openstack/nova/blob/master/doc/source/runnova/vncconsole.rst


On Thu, Mar 29, 2012 at 11:07 AM, Lucian Thomaz wrote:

>  Hey guys,
>
> I'm using Dashboard with a nova-compute installed in another machine, but
> when I try access VNC Console I get the error "failed to connect to server".
>
> Here is the log -> http://pastebin.com/5DZMfiNE
>
> Anyone already saw this trouble?
>
>
> *Lucian Thomaz *
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Dashboard VNC Console failed to connect to server

[Guilherme Birk]

I'm having problems with it too. I'm trying to connect on my instances in the 
VNC tab at the dashboard, but I'm getting a 404 not found in the URL 
http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None

Here is my nova-api.log. Looks like nova is having problems with the POST at 
http://localhost:8774/v1.1/db742491018d467690ba7d3a7bb383a5/servers/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/action.

Any suggestions ?
From: luciantho...@hotmail.com
To: openstack@lists.launchpad.net
Date: Thu, 29 Mar 2012 18:07:59 +
Subject: [Openstack] Dashboard VNC Console failed to connect to server







Hey guys,
I'm using Dashboard with a nova-compute installed in another machine, but when 
I try access VNC Console I get the error "failed to connect to server".
Here is the log -> http://pastebin.com/5DZMfiNE
Anyone already saw this trouble?

Lucian Thomaz 
  

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp   
  ___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Dashboard VNC Console failed to connect to server

[Lucian Thomaz]

Hey guys,
I'm using Dashboard with a nova-compute installed in another machine, but when 
I try access VNC Console I get the error "failed to connect to server".
Here is the log -> http://pastebin.com/5DZMfiNE
Anyone already saw this trouble?

Lucian Thomaz 
  ___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp