← Back to team overview

openstack team mailing list archive

Re: Problem with VNC on compute node

 

I remember solving this problem by adding the hostnames of all compute
nodes to the /etc/hosts file where the vncproxy was running.

But this was like a year ago I'm not sure if this would solve your problem.
On Fri, Jan 25, 2013 at 9:23 AM, longeek <mengql112233@xxxxxxxxx> wrote:

>  Hi,
>    I also get the same issuse, I have check the vnc config in nova config.
>    Can anybody tell us about why this and how the horizon access the vnc?
>
> Tks,
> Best Regards,
>
> --------------------------------------------
> Lawrency Meng
> mail: mengql112233@xxxxxxxxx
>
> 于 01/24/2013 12:27 AM, Guilherme Russi 写道:
>
>  Hello guys,
>
>  I'm installing the folsom version and I have one computer like the
> controller and one being the compute node. I can start the VM with cirros
> OS but I can't use the VNC, I got the error: "Failed to connect to server
> (code: 1006)". I've been following this tutorial:
> http://docs.openstack.org/folsom/basic-install/content/basic-install_compute.html
> .
>
> Can anybody help me?
>
> Thank you and regards.
>
> Guilherme.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> --
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
>
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
*Intel SSG/SSD/SOTC/PRC/CITT*
880 Zixing Road, Zizhu Science Park, Minhang District, Shanghai, 200241,
China
+862161166500

Follow ups

References