Ask Your Question
2

nova-novncproxy not connecting to instance

asked 2013-08-08 04:36:27 -0500

shoubam gravatar image

updated 2013-08-08 04:55:56 -0500

Following up on my earlier question: I have openstack grizzly on centos 6.4. Things are working, except for console connection to the instances. Instances are up and running, and I can connect to their console with a vnc viewer, e.g. remmina. But I can not connect to their console via novnc. All it gives me is a "Server disconnected (code: 1006)".

hosts involved:

192.168.222.10 haproxy
192.168.222.17 all nova services except nova-compute
192.168.222.140 nova-compute

From an experimental devstack install, I can see that novncproxy is connecting directly to the vnc port of the instance. With this system, this is not the case, novnc is not attempting to connect to the instances console, as I can see from an empty tcpdump on the compute host:

tcpdump -i br-admin-222 port 5907
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br-admin-222, link-type EN10MB (Ethernet), capture size 65535 bytes

I am sure its the right port, because I can connect to that port with remmina and see the console. Also, I can connect to that port with telnet from the host running nova-novncproxy:

$ telnet 192.168.222.140 5907
Trying 192.168.222.140...
Connected to 192.168.222.140.
Escape character is '^]'.
RFB 003.008

So its not a networking issue.

nova.conf on nova-novncproxy host is

novncproxy_port=6080
novncproxy_base_url=http://192.168.222.10:6080/vnc_auto.html
novncproxy_host=192.168.222.17

nova.conf on nova-compute host is

vncserver_listen=0.0.0.0
vncserver_proxyclient_address=192.168.222.140
novncproxy_base_url=http://192.168.222.10:6080/vnc_auto.html

If someone could answer any of the following questions, I would be greatfull:

  • how does nova-novncproxy know about which host and which port to connect to for a certain instance? Where is this stored, and how does that information get to novnc?
  • I have started nova-novncproxy in the foreground to get more info with --debug and --verbose, but won't get any errors or warnings. How can I get more info on where exactly this is failing?
  • Any other hints on how to debug this?
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2013-08-20 07:57:17 -0500

shoubam gravatar image

updated 2013-08-20 08:20:44 -0500

So it turns out this issue is related to myself sitting in an office with a webproxy. I have firefox configured to automatic detect proxy setting for the network. In general it works fine, I can connect to outside websites AND openstack horizon. horizon itself works fine, but it does not show the console window. I can load the console in an extra window, still no conncetion. But if I disable webproxy alltogether, and then reload the window with the console, it works.

So its kind of solved, but I would really like to know why this works like this. I will make a sperate question.

edit flag offensive delete link more

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: 2013-08-08 04:36:27 -0500

Seen: 11,646 times

Last updated: Aug 20 '13