Ask Your Question
0

Nova VNC works, but not in Dashboard

asked 2018-04-24 10:22:41 -0500

woltjert gravatar image

I have the VNC console working, but in the openstack dashboard, it does not load and shows an error code 1006 instead. If I click to show only the console, then it loads.

Nova logs on the controller when getting code:1006 on the dashboard:

==> /var/log/nova/nova-consoleauth.log <==
2018-04-24 10:23:58.894 3109 INFO nova.consoleauth.manager [req-41c322e4-76b7-47a3-aa10-27de67b47568 8bf003cdf58a4233b7e279aee1eec593 ee5d821a39174d8a91e3a741a6ecd97e - default default] Received Token: a634ec8f-c7db-45e2-8fc2-851340bb8ad3, {'instance_uuid': u'5f6785ff-f592-4f68-88a4-3ad512a959f2', 'access_url': u'http://controller:6080/vnc_auto.html?token=a634ec8f-c7db-45e2-8fc2-851340bb8ad3', 'token': u'a634ec8f-c7db-45e2-8fc2-851340bb8ad3', 'last_activity_at': 1524579838.89435, 'internal_access_path': None, 'console_type': u'novnc', 'host': u'192.168.116.23', 'port': u'5900'}

==> /var/log/nova/nova-novncproxy.log <==
2018-04-24 10:23:59.647 9358 INFO nova.console.websocketproxy [-] 192.168.116.22 - - [24/Apr/2018 10:23:59] 192.168.116.22: Plain non-SSL (ws://) WebSocket connection
2018-04-24 10:23:59.648 9358 INFO nova.console.websocketproxy [-] 192.168.116.22 - - [24/Apr/2018 10:23:59] 192.168.116.22: Version hybi-13, base64: 'False'
2018-04-24 10:23:59.649 9358 INFO nova.console.websocketproxy [-] 192.168.116.22 - - [24/Apr/2018 10:23:59] 192.168.116.22: Path: '/websockify'
2018-04-24 10:23:59.769 9358 INFO nova.console.websocketproxy [req-261346a6-84eb-4829-bdc6-b85f53939786 - - - - -] handler exception: The token 'a634ec8f-c7db-45e2-8fc2-851340bb8ad3' is invalid or has expired

The same logs when successfully showing only the console:

==> /var/log/nova/nova-consoleauth.log <==
2018-04-24 10:25:04.291 3109 INFO nova.consoleauth.manager [req-7926032b-fcd7-490e-8f0e-99b5bccef8da - - - - -] Checking Token: a634ec8f-c7db-45e2-8fc2-851340bb8ad3, True

==> /var/log/nova/nova-novncproxy.log <==
2018-04-24 10:25:04.589 9513 INFO nova.console.websocketproxy [req-7926032b-fcd7-490e-8f0e-99b5bccef8da - - - - -]   8: connect info: {u'instance_uuid': u'5f6785ff-f592-4f68-88a4-3ad512a959f2', u'internal_access_path': None, u'last_activity_at': 1524579838.89435, u'console_type': u'novnc', u'host': u'192.168.116.23', u'token': u'a634ec8f-c7db-45e2-8fc2-851340bb8ad3', u'access_url': u'http://controller:6080/vnc_auto.html?token=a634ec8f-c7db-45e2-8fc2-851340bb8ad3', u'port': u'5900'}
2018-04-24 10:25:04.590 9513 INFO nova.console.websocketproxy [req-7926032b-fcd7-490e-8f0e-99b5bccef8da - - - - -]   8: connecting to: 192.168.116.23:5900

The [vnc] section of /etc/nova/nova.conf on the controller

my_ip = 192.168.116.21

[vnc]
enabled = true
vncserver_listen = $my_ip
vncserver_proxyclient_address = $my_ip
novncproxy_host = 192.168.116.21

The [vnc] section of /etc/nova/nova.conf on the controller

my_ip = 192.168.116.23

[vnc]
enabled = true
vncserver_listen = 0.0.0.0
vncserver_proxyclient_address = $my_ip
novncproxy_base_url = http://controller:6080/vnc_auto.html

The connection to the controller is also going through HAProxy. I wouldn't expect this to be an issue as the console does partially work, but I thought I would include this detail anyway if there could be an issue with this.

edit retag flag offensive close merge delete

Comments

Deepa gravatar imageDeepa ( 2018-04-25 01:17:08 -0500 )edit

So it seems like the problem more likely has to do with HAProxy.

woltjert gravatar imagewoltjert ( 2018-04-25 08:36:38 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2018-05-15 16:02:41 -0500

Joe89 gravatar image

Hi everyone,

I have also problem with VNC setup (I guess). My setup has one controller node and two compute nodes.

enter code here` nova.conf of the controller node

[vnc] enabled = True

novncproxy_host = 0.0.0.0

novncproxy_port = 6080

server_proxyclient_address = 172.16.16.100

server_listen = 0.0.0.0

novncproxy_base_url = http://172.16.16.100:6080/vnc_auto.html

nova.conf of the compute nodes

[vnc] enabled = True

server_listen = 0.0.0.0

server_proxyclient_address = 172.16.16.10

novncproxy_base_url = http://172.16.16.100:6080/vnc_auto.html

I don't know why I still can't access to the instance via vnc console. Error code is "Failed to connect to server (code: 1006)".

Log from /var/log/nova/nova-novncproxy.log:

[15/May/2018 17:57:42] 172.16.16.1: Path: '/websockify' 2018-05-15 17:57:42.914 4582 INFO nova.console.websocketproxy [req-40a6c465-32a9-4ec0-a539-314c485b8839 - - - - -] handler exception: The token '84b0f7fc-eacb-4468-8f85-7696c52b32bc' is invalid or has expired

Have anyone seen and solve this?

Many thanks

Joe

edit flag offensive delete link more

Comments

I am using OpenStack Queens.

Thanks Joe

Joe89 gravatar imageJoe89 ( 2018-05-15 11:08:41 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2018-04-24 10:22:41 -0500

Seen: 129 times

Last updated: May 15