I did a fresh re-install of devstack. Now I got the URL for the console.
localadmin@qa4:~/devstack$ nova get-vnc-console vm1 novnc +-------+-------------------------------------------------------------------------------------+ | Type | Url | +-------+-------------------------------------------------------------------------------------+ | novnc | http://172.29.172.161:6080/vnc_auto.html?token=9ced0dd0-f146-42eb-9b26-c64a29443936 | +-------+-------------------------------------------------------------------------------------+ However, when attempt to connect to the URL, error "Failed to connect to server (code: 1006)" is returned at the web page. The following traceback is logged in the Controller's screen-x-n-novnc.log: 10.131.67.144 - - [15/Oct/2014 15:11:06] "GET /include/webutil.js HTTP/1.1" 200 - 2014-10-15 15:11:06.029 DEBUG nova.console.websocketproxy [-] 10.131.67.144: new handler Process from (pid=21242) vmsg /usr/local/lib/python2.7/dist-packages/websockify/websocket.py:824 10.131.67.144 - - [15/Oct/2014 15:11:06] "GET /include/des.js HTTP/1.1" 200 - 10.131.67.144 - - [15/Oct/2014 15:11:06] "GET /include/keyboard.js HTTP/1.1" 200 - 10.131.67.144 - - [15/Oct/2014 15:11:06] "GET /include/input.js HTTP/1.1" 200 - 10.131.67.144 - - [15/Oct/2014 15:11:06] "GET /include/display.js HTTP/1.1" 200 - 10.131.67.144 - - [15/Oct/2014 15:11:06] "GET /include/jsunzip.js HTTP/1.1" 200 - 10.131.67.144 - - [15/Oct/2014 15:11:06] "GET /include/rfb.js HTTP/1.1" 200 - 2014-10-15 15:11:06.590 DEBUG nova.console.websocketproxy [-] 10.131.67.144: new handler Process from (pid=21242) vmsg /usr/local/lib/python2.7/dist-packages/websockify/websocket.py:824 10.131.67.144 - - [15/Oct/2014 15:11:06] "GET /websockify HTTP/1.1" 101 - 10.131.67.144 - - [15/Oct/2014 15:11:06] 10.131.67.144: Plain non-SSL (ws://) WebSocket connection 10.131.67.144 - - [15/Oct/2014 15:11:06] 10.131.67.144: Version hybi-13, base64: 'False' 10.131.67.144 - - [15/Oct/2014 15:11:06] 10.131.67.144: Path: '/websockify' 2014-10-15 15:11:06.605 INFO oslo.messaging._drivers.impl_rabbit [req-f5c8828b-f111-4a12-8812-d25f56e47b01 None None] Connecting to AMQP server on 172.29.172.161:5672 2014-10-15 15:11:06.616 DEBUG nova.console.websocketproxy [-] 10.131.67.144: new handler Process from (pid=21242) vmsg /usr/local/lib/python2.7/dist-packages/websockify/websocket.py:824 10.131.67.144 - - [15/Oct/2014 15:11:06] "GET /favicon.ico HTTP/1.1" 200 - 2014-10-15 15:11:06.622 INFO oslo.messaging._drivers.impl_rabbit [req-f5c8828b-f111-4a12-8812-d25f56e47b01 None None] Connected to AMQP server on 172.29.172.161:5672 2014-10-15 15:11:06.629 INFO oslo.messaging._drivers.impl_rabbit [req-f5c8828b-f111-4a12-8812-d25f56e47b01 None None] Connecting to AMQP server on 172.29.172.161:5672 2014-10-15 15:11:06.641 INFO oslo.messaging._drivers.impl_rabbit [req-f5c8828b-f111-4a12-8812-d25f56e47b01 None None] Connected to AMQP server on 172.29.172.161:5672 2014-10-15 15:11:06.652 INFO nova.console.websocketproxy [req-f5c8828b-f111-4a12-8812-d25f56e47b01 None None] handler exception: The token '9ced0dd0-f146-42eb-9b26-c64a29443936' is invalid or has expired 2014-10-15 15:11:06.652 DEBUG nova.console.websocketproxy [req-f5c8828b-f111-4a12-8812-d25f56e47b01 None None] exception from (pid=13509) vmsg /usr/local/lib/python2.7/dist-packages/websockify/websocket.py:824 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy Traceback (most recent call last): 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy File "/usr/local/lib/python2.7/dist-packages/websockify/websocket.py", line 874, in top_new_client 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy client = self.do_handshake(startsock, address) 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy File "/usr/local/lib/python2.7/dist-packages/websockify/websocket.py", line 809, in do_handshake 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy self.RequestHandlerClass(retsock, address, self) 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy File "/opt/stack/nova/nova/console/websocketproxy.py", line 112, in __init__ 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy websockify.ProxyRequestHandler.__init__(self, *args, **kwargs) 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy File "/usr/local/lib/python2.7/dist-packages/websockify/websocket.py", line 112, in __init__ 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy SimpleHTTPRequestHandler.__init__(self, req, addr, server) 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy File "/usr/lib/python2.7/SocketServer.py", line 649, in __init__ 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy self.handle() 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy File "/usr/local/lib/python2.7/dist-packages/websockify/websocket.py", line 540, in handle 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy SimpleHTTPRequestHandler.handle(self) 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy File "/usr/lib/python2.7/BaseHTTPServer.py", line 340, in handle 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy self.handle_one_request() 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy File "/usr/lib/python2.7/BaseHTTPServer.py", line 328, in handle_one_request 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy method() 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy File "/usr/local/lib/python2.7/dist-packages/websockify/websocket.py", line 506, in do_GET 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy if not self.handle_websocket(): 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy File "/usr/local/lib/python2.7/dist-packages/websockify/websocket.py", line 494, in handle_websocket 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy self.new_websocket_client() 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy File "/opt/stack/nova/nova/console/websocketproxy.py", line 74, in new_websocket_client 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy raise exception.InvalidToken(token=token) 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy InvalidToken: The token '9ced0dd0-f146-42eb-9b26-c64a29443936' is invalid or has expired 2014-10-15 15:11:06.652 TRACE nova.console.websocketproxy 2014-10-15 15:11:06.658 DEBUG nova.console.websocketproxy [-] Reaing zombies, active child count is 7 from (pid=21242) vmsg /usr/local/lib/python2.7/dist-packages/websockify/websocket.py:824 2014-10-15 15:11:50.404 DEBUG nova.console.websocketproxy [-] Reaing zombies, active child count is 4 from (pid=21242) vmsg /usr/local/lib/python2.7/dist-packages/websockify/websocket.py:824 2014-10-15 15:11:50.405 DEBUG nova.console.websocketproxy [-] Reaing zombies, active child count is 0 from (pid=21242) vmsg /usr/local/lib/python2.7/dist-packages/websockify/websocket.py:824 2014-10-15 15:11:50.405 DEBUG nova.console.websocketproxy [-] Reaing zombies, active child count is 0 from (pid=21242) vmsg /usr/local/lib/python2.7/dist-packages/websockify/websocket.py:824 Devstack is used to deploy OpenStack. I enabled the “n-novnc” service at the Compute node. Below is a snippet of the localrc. Compute: # Services disable_all_services ENABLED_SERVICES=neutron,n-cpu,rabbit,q-api,q-agt,n-novnc Controller: # Services disable_service n-net disable_service n-cpu enable_service q-svc enable_service q-agt enable_service q-dhcp enable_service q-l3 enable_service q-meta enable_service neutron The process n-novnc is running at both the Controller and Compute nodes. Is this a misconfiguration issue? Thanks, Danny --------------------------------------------------------------- Date: Wed, 15 Oct 2014 08:10:00 -0700 From: Vishvananda Ishaya <vishvana...@gmail.com<mailto:vishvana...@gmail.com>> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [qa] Cannot start the VM console when VM is launched at Compute node Message-ID: <bc5f71f5-5f45-497a-bf99-f8ccd3c71...@gmail.com<mailto:bc5f71f5-5f45-497a-bf99-f8ccd3c71...@gmail.com>> Content-Type: text/plain; charset="windows-1252" No this is not expected and may represent a misconfiguration or a bug. Something is returning a 404 when it shouldn?t. You might get more luck running the nova command with ?debug to see what specifically is 404ing. You could also see if anything is reporting NotFound in the nova-consoleauth or nova-api or nova-compute logs Vish On Oct 14, 2014, at 10:45 AM, Danny Choi (dannchoi) <dannc...@cisco.com<mailto:dannc...@cisco.com>> wrote: Hi, I used devstack to deploy multi-node OpenStack, with Controller + nova-compute + Network on one physical node (qa4), and Compute on a separate physical node (qa5). When I launch a VM which spun up on the Compute node (qa5), I cannot launch the VM console, in both CLI and Horizon. localadmin@qa4:~/devstack$ nova hypervisor-servers q +--------------------------------------+-------------------+---------------+---------------------+ | ID | Name | Hypervisor ID | Hypervisor Hostname | +--------------------------------------+-------------------+---------------+---------------------+ | 48b16e7c-0a17-42f8-9439-3146f26b4cd8 | instance-0000000e | 1 | qa4 | | 3eadf190-465b-4e90-ba49-7bc8ce7f12b9 | instance-0000000f | 1 | qa4 | | 056d4ad2-e081-4706-b7d1-84ee281e65fc | instance-00000010 | 2 | qa5 | +--------------------------------------+-------------------+---------------+---------------------+ localadmin@qa4:~/devstack$ nova list +--------------------------------------+------+--------+------------+-------------+---------------------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+------+--------+------------+-------------+---------------------------------+ | 3eadf190-465b-4e90-ba49-7bc8ce7f12b9 | vm1 | ACTIVE | - | Running | private=10.0.0.17 | | 48b16e7c-0a17-42f8-9439-3146f26b4cd8 | vm2 | ACTIVE | - | Running | private=10.0.0.16, 172.29.173.4 | | 056d4ad2-e081-4706-b7d1-84ee281e65fc | vm3 | ACTIVE | - | Running | private=10.0.0.18, 172.29.173.5 | +--------------------------------------+------+--------+------------+-------------+---------------------------------+ localadmin@qa4:~/devstack$ nova get-vnc-console vm3 novnc ERROR (CommandError): No server with a name or ID of 'vm3' exists. <<<<<<<[ERROR] This does not happen if the VM resides at the Controlller (qa5). localadmin@qa4:~/devstack$ nova get-vnc-console vm2 novnc +-------+-------------------------------------------------------------------------------------+ | Type | Url | +-------+-------------------------------------------------------------------------------------+ | novnc | http://172.29.172.161:6080/vnc_auto.html?token=f556dea2-125d-49ed-bfb7-55a9a7714b2e | +-------+-------------------------------------------------------------------------------------+ Is this expected behavior? Thanks, Danny _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
