Ok. I don't know.
The command nova get-vnc-console ID novnc generate that in my environment
2013-08-19 18:50:02 AUDIT nova.consoleauth.manager
[req-3956b820-0f72-475d-ac0e-10e663368fff 0f5e030e8ac44d9a8a91d80d5ceeb45f
8431ce087f4e40a4baf7dcb38d9278fc] Received Token:
3d1f1b20-02fc-46f8-b823-87af9
Resolved vnc console issue. Started vnc in debug and passed "nova_token"
value in rfb.js. After that console came. Thanks Minox for clue.
On Mon, Aug 19, 2013 at 9:04 PM, Jitendra Bhaskar wrote:
> Only one nova-consoleauth process is running on controller. Started
> consoleauth in debug mode ,
How many nova-consoleauth process you have? Three? One in each controller?.
In this case, the nova-consoleauth(s) should shared the tokens.
Enabled verbose output to nova-consoleauth log and you see token - FAIL?
2013/8/19 Jitendra Bhaskar
> Hi,
>
> Unable to see console using vnc. Running op
Hi,
Unable to see console using vnc. Running openstack with three node
controller, network and compute.
Compute node nova.conf for vnc :
# novnc
vnc_enabled=true
novncproxy_base_url=http://public_ip_of_controller:6080/vnc_auto.html
novncproxy_port=6080
vncserver_proxyclient_address=management_ip_
