NoVNC connect error 1006
On a brand new OpenStack install (Liberty) we're receiving a 1006 error when trying to access the console of a VM through NoVNC. When we access it a token is generated and listed in the config file but it seems that when the client tries to access it, there is a write delay and it does not connect. However, if you open the same URL in another page or refresh the iframe it immediately connects. Seems to me that there is a race condition occurring here between writing the token and reading it. While it does work, it is extremely irritating to use does anyone have a fix for this?
Before Refresh
/var/log/nova/nova-novncproxy.log:
2016-02-23 01:27:55.639 20827 INFO oslo.messaging._drivers.impl_rabbit [req-9a20b179-b226-4d93-a496-76b95540f325 - - - - -] Connecting to AMQP server on controller:5672
2016-02-23 01:27:55.648 20827 INFO oslo.messaging._drivers.impl_rabbit [req-9a20b179-b226-4d93-a496-76b95540f325 - - - - -] Connected to AMQP server on controller:5672
2016-02-23 01:27:55.678 20827 INFO oslo.messaging._drivers.impl_rabbit [req-9a20b179-b226-4d93-a496-76b95540f325 - - - - -] Connecting to AMQP server on controller:5672
2016-02-23 01:27:55.691 20827 INFO oslo.messaging._drivers.impl_rabbit [req-9a20b179-b226-4d93-a496-76b95540f325 - - - - -] Connected to AMQP server on controller:5672
2016-02-23 01:27:55.700 20827 INFO nova.console.websocketproxy [req-9a20b179-b226-4d93-a496-76b95540f325 - - - - -] handler exception: The token '0a794a36-7c48-409e-bca8-936e6203d170' is invalid or has expired
After Refresh
/var/log/nova/nova-novncproxy.log:
2016-02-23 01:28:40.362 20840 INFO oslo.messaging._drivers.impl_rabbit [req-b7e4dc7b-9533-44d4-9d56-45d3cf21b5d6 - - - - -] Connecting to AMQP server on controller:5672
2016-02-23 01:28:40.376 20840 INFO oslo.messaging._drivers.impl_rabbit [req-b7e4dc7b-9533-44d4-9d56-45d3cf21b5d6 - - - - -] Connected to AMQP server on controller:5672
2016-02-23 01:28:40.399 20840 INFO oslo.messaging._drivers.impl_rabbit [req-b7e4dc7b-9533-44d4-9d56-45d3cf21b5d6 - - - - -] Connecting to AMQP server on controller:5672
2016-02-23 01:28:40.408 20840 INFO oslo.messaging._drivers.impl_rabbit [req-b7e4dc7b-9533-44d4-9d56-45d3cf21b5d6 - - - - -] Connected to AMQP server on controller:5672
2016-02-23 01:28:40.481 20840 INFO nova.console.websocketproxy [req-b7e4dc7b-9533-44d4-9d56-45d3cf21b5d6 - - - - -] 741: connect info: {u'instance_uuid': u'bd970307-9a90-4d4d-8b9a-a4a0b250d589', u'internal_access_path': None, u'last_activity_at': 1456190874.85105, u'console_type': u'novnc', u'host': u'10.3.1.13', u'token': u'0a794a36-7c48-409e-bca8-936e6203d170', u'access_url': u'http://controller:6080/vnc_auto.html?token=0a794a36-7c48-409e-bca8-936e6203d170', u'port': u'5900'}
2016-02-23 01:28:40.482 20840 INFO nova.console.websocketproxy [req-b7e4dc7b-9533-44d4-9d56-45d3cf21b5d6 - - - - -] 741: connecting to: 10.3.1.13:5900
Infrastructure:
- Controller - 10.3.1.1
- Compute3 (node where the instance is running) - 10.3.1.13
- Load Balancer - 10.3.1.10
Thanks,
check if this can help you.
Are your nodes synced in time with a NTP server?
@Syed That documents has to do with setting up NoVNC from the beginning which as I said in my question is working. There just seems to be a delay in the token.
@Eduardo Yes, they are all using the same NTP server with ntpd. I understand the documentation recommends Chrony but it shouldn't matter.
You need to configure memcached to your nova-consoleauth services. Only one service can be running at the same time. Regards