openstack team mailing list archive

[Anthony Young <sleepsonthefloor@xxxxxxxxx>]

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 <heckj@xxxxxx> 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 <heckj@xxxxxx> 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 <heckj@xxxxxx> 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 <guibirk@xxxxxxxxxxx>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: lucianthomaz@xxxxxxxxxxx
>>>> To: openstack@xxxxxxxxxxxxxxxxxxx
>>>> 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@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
>>>
>>>
>>>
>>
>>
>
>
>