Ask Your Question
0

VNC console in dashboard failed to connect to server (code: 1006)

asked 2019-03-13 09:03:00 -0500

chakravarthy gravatar image

Unable to access VM thorough console in dashboard. I have multi-node Queens version of openstack bare metal setup on ubuntu 16.

Errors:

Failed to connect to server (code: 1006)

2019-03-13 18:55:15.926 9339 INFO nova.console.websocketproxy [req-db19bd87-c70b-481d-8939-d3957fe2d393 - - - - -] handler exception: [Errno 110] ETIMEDOUT

2019-03-13 13:25:13,556 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by <class 'socket.error'>: [Errno 101] Network is unreachable)]

My vnc configuration in controller's nova.conf is as mentioned below:

[DEFAULT]
my_ip = 10.0.0.11
[vnc]
enabled = true
server_listen = $my_ip
server_proxyclient_address = $my_ip

My vnc configuration in compute's nova.conf is as mentioned below:

[DEFAULT]
my_ip = 10.0.0.31
[vnc]
enabled = true
server_listen = 0.0.0.0
server_proxyclient_address = $my_ip
novncproxy_base_url = http://controller:6080/vnc_auto.html

My VM's console log points to route error:

ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2019-03-13 13:25:13,556 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by <class 'socket.error'>: [Errno 101] Network is unreachable)]
...
2019-03-13 13:27:19,970 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 126 seconds
2019-03-13 13:27:19,973 - util.py[WARNING]: Getting data from <class 'cloudinit.sources.DataSourceCloudStack.DataSourceCloudStack'> failed

My nova-novncproxy.log point to timeout error:

2019-03-13 18:52:18.040 9266 INFO nova.console.websocketproxy [-] WebSocket server settings:
2019-03-13 18:52:18.040 9266 INFO nova.console.websocketproxy [-]   - Listen on 0.0.0.0:6080
2019-03-13 18:52:18.040 9266 INFO nova.console.websocketproxy [-]   - Flash security policy server
2019-03-13 18:52:18.041 9266 INFO nova.console.websocketproxy [-]   - Web server (no directory listings). Web root: /usr/share/novnc
2019-03-13 18:52:18.041 9266 INFO nova.console.websocketproxy [-]   - No SSL/TLS support (no cert file)
2019-03-13 18:52:18.041 9266 INFO nova.console.websocketproxy [-]   - proxying from 0.0.0.0:6080 to None:None
2019-03-13 18:53:05.622 9339 INFO nova.console.websocketproxy [-] 10.0.0.11 - - [13/Mar/2019 18:53:05] 10.0.0.11: Plain non-SSL (ws://) WebSocket connection
2019-03-13 18:53:05.639 9339 INFO nova.console.websocketproxy [-] 10.0.0.11 - - [13/Mar/2019 18:53:05] 10.0.0.11: Version hybi-13, base64: 'False'
2019-03-13 18:53:05.640 9339 INFO nova.console.websocketproxy [-] 10.0.0.11 - - [13/Mar/2019 18:53:05] 10.0.0.11: Path: '/websockify'
2019-03-13 18:53:05.890 9339 INFO nova.console.websocketproxy [req-db19bd87-c70b-481d-8939-d3957fe2d393 - - - - -]   2: connect info: {u'instance_uuid': u'6c1337ca-f4d3-4072-9133-ce03afac1f53', u'internal_access_path': None, u'last_activity_at': 1552483384.72316, u'console_type': u'novnc', u'host': u'10.0.0.31', u'token': u'39e439b5-4406-4fbb-b305-90ba3e800cb1', u'access_url': u'http://controller:6080/vnc_auto.html?token=39e439b5-4406-4fbb-b305-90ba3e800cb1', u'port': u'5900'}
2019-03-13 ...
(more)
edit retag flag offensive close merge delete

Comments

Instead of controller use the actual ip address in the configuration files, unsure about internal dns lookups on your setup

Mohit gravatar imageMohit ( 2019-03-14 00:40:19 -0500 )edit

@Mohit, thanks for your comment. changing controller to IP didn't fix this issue. tried restarting the nova services in controller and compute machines and also tried restarting the VM.

chakravarthy gravatar imagechakravarthy ( 2019-03-14 01:24:34 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2019-03-15 11:15:35 -0500

updated 2019-03-15 11:19:56 -0500

Have you installed the VNC proxy server on the compute servers?

https://access.redhat.com/documentati...

If yes, You should have on both controller and compute the following:

novncproxy_host=$host
novncproxy_port=$port
enabled = true // optional
server_listen = $my_ip
server_proxyclient_address = $my_ip

And for compute servers at the end of the line the following:

novncproxy_base_url = http://controller:<port>/vnc_auto.html

That should work. hopefully :D

edit flag offensive delete link more

Comments

I reinstalled everything and didn't see this issue. I have not included above change and still it works. just followed the instructions from the official documentation.

chakravarthy gravatar imagechakravarthy ( 2019-04-02 01:49:51 -0500 )edit

That's good to know :D

JorgeFranco gravatar imageJorgeFranco ( 2019-05-03 09:53:49 -0500 )edit

What offical documentation did you have follow i run CentOS and cannot fix this issue.

rediumbv gravatar imagerediumbv ( 2019-08-06 06:43:28 -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: 2019-03-13 09:03:00 -0500

Seen: 596 times

Last updated: Mar 15