See below: > > but I get some thing strange for: > if I set > --vnc_enabled=true > --novncproxy_base_url=http://localhost:6080/vnc_auto.html<http://78.153.xxx.xxx:6080/vnc_auto.html> > --vncserver_proxyclient_address=localhost > --vncserver_listen=0.0.0.0 > in nova.conf that it return > Oops! Google Chrome could not connect to > localhost:6080<http://192.168.0.202:6080/> > > in dashboard,but work fine when I use command *nova get-vnc-console demo > novnc ..*It return a url as > http://localhost:6080/vnc_auto.html?token=XXXXXXXXXXXXXX.. > then I enter this url in chrome with > http://172.18.187.110:6080/vnc_auto.html?token=XXXXXXXXXXXXXX > ps:172.18.187.110 is the public ip of my openstack server.. > *It can return my VM's screen ..* > * > * > however,when I set > --vnc_enabled=true > --novncproxy_base_url=http://172.18.187.110:6080/vnc_auto.html<http://78.153.xxx.xxx:6080/vnc_auto.html> > --vncserver_proxyclient_address=172.18.187.110 > --vncserver_listen=0.0.0.0 > > and restart all the services .. > both dashboard and url from command *nova get-vnc-console demo novnc *returns > server connot connect > ** > > *I am wondering how would localhost and 172.18.187.110 be not the same???* > * > * >
If you launched this instance before you specified --vncserver_listen, then the instance's vnc server will bind 127.0.0.1. Furthermore, this configuration will be baked into the instances libvirt.xml file, so changes to --vncserver_listen in your nova.conf will not have any effect for already existing instances. Did you happen to launch this instance before you set --vncserver_listen to 0.0.0.0? If so, you may try to launch another instance and see if vnc is working properly. Just for the record, --vncserver_listen is generally set to the hosts management ip, rather than the public ip or 0.0.0.0, for security reasons. > ** > thanks > > dming > > ------------------ Original ------------------ > *From: * "Kiall Mac Innes"<[email protected]>; > *Date: * Sat, Apr 7, 2012 07:15 PM > *To: * "Eric Luo"<[email protected]>;** > *Cc: * "openstack"<[email protected]>;** > *Subject: * Re: [Openstack] What is the correct config for vnc or novnc > tosuccessfully enable VNC CONSOLE in a browser? > > For anyone else who might be hng the same issue.. These two packages, > combined with these options will get novnc working on precise.. > > --vnc_enabled=true > --novncproxy_base_url=http://78.153.XXX.XXX:6080/vnc_auto.html<http://78.153.xxx.xxx:6080/vnc_auto.html> > --vncserver_proxyclient_address=78.153.XXX.XXX > --vncserver_listen=0.0.0.0 > > I've intentionally kept the version numbers identical to the packages > currently in the precise repo's. This will hopefully let apt "do the right > thing" once an official update is released.. > > http://dl.dropbox.com/u/1400487/novnc_2012.1~e3%2Bdfsg-1_amd64.deb > > http://dl.dropbox.com/u/1400487/python-novnc_2012.1~e3%2Bdfsg-1_all.deb > > Thanks, > Kiall > > > On Sat, Apr 7, 2012 at 11:14 AM, Kiall Mac Innes <[email protected]> > wrote: > >> The novnc package included in 12.04 is outdated/broken. >> >> I know Chuck is planning to fix it ASAP.. >> >> In the meantime, I hacked together a fixed .deb.. I can stick it >> somewhere for you to download if you like? >> >> Thanks, >> Kiall >> >> Sent from my phone. >> On Apr 7, 2012 9:31 a.m., "Eric Luo" <[email protected]> wrote: >> >>> Hello ,all >>> I installed Openstack as a all-in-one solution ,I got everything runs >>> correctly ,I can ssh to my VMs etc. But there is a problem here: I can not >>> use the VNC tag in dashboard. >>> I have installed the nova-consoleauth and novnc by "apt-get" .but I can >>> not statrt the nova-novncproxy service (by the way ,the nova-vncproxy >>> service always runs OK), >>> When I use the command root@ubuntu:~# *service novnc start* >>> I got the following with nothing else: >>> * Starting OpenStack NoVNC proxy nova-novncproxy >>> >>> It only says "starting",but does not say "started"! >>> >>> actually it is not started ,by command *service novnc status, *it says: >>> * nova-novncproxy is not running. >>> >>> when I use command *nova-novncproxy --flagfile=/etc/nova/nova.conf* ,I >>> got the following: >>> >>> WARNING: no 'numpy' module, HyBi protocol support disabled >>> Traceback (most recent call last): >>> File "/usr/bin/nova-novncproxy", line 40, in <module> >>> flags.DEFINE_boolean('verbose', False, >>> AttributeError: 'module' object has no attribute 'DEFINE_boolean' >>> >>> When I use command *nova get-vnc-console testVM novnc* >>> >>> >>> >>> +-------+------------------------------------------------------------------------------------+ >>> | Type | Url | >>> >>> +-------+------------------------------------------------------------------------------------+ >>> | novnc | >>> http://192.168.0.202:6080/vnc_auto.html?token=e1095862-deb9-4cb5-9ec9-44aa0200342e >>> | >>> >>> +-------+------------------------------------------------------------------------------------+ >>> >>> but When pasted the url above into my chrome ,I got the following : >>> Oops! Google Chrome could not connect to 192.168.0.202:6080Suggestions: >>> >>> - Try reloading the page >>> - Search on Google:when I click the "VNC " tag in dashboard ,I got >>> the folloing : >>> >>> >>> This webpage is not available >>> Google Chrome's connection attempt to *192.168.0.202* was rejected. The >>> website may be down, or your network may not be properly configured. >>> Here are some suggestions: >>> >>> - >>> Reload<http://192.168.0.202:6080/vnc_auto.html?token=4ecea055-2253-48e7-9542-544761432d29&title=VM9(11323336-8e18-453b-8b31-f4c821649df4)> >>> this >>> webpage later. >>> - Check your Internet connection. Restart any router, modem, or >>> other network devices you may be using. >>> - Add Google Chrome as a permitted program in your firewall's or >>> antivirus software's settings. If it is already a permitted program, try >>> deleting it from the list of permitted programs and adding it again. >>> - If you use a proxy server, check your proxy settings or contact >>> your network administrator to make sure the proxy server is working. If >>> you >>> don't believe you should be using a proxy server, adjust your proxy >>> settings: Go to *the wrench menu > Settings > Under the >>> Hood > Change Proxy Settings... *and make sure your configuration is >>> set to "no proxy" or "direct." >>> >>> Error 102 (net::ERR_CONNECTION_REFUSED): The server refused the >>> connection. >>> I hvae an nova config as following: >>> --dhcpbridge_flagfile=/etc/nova/nova.conf >>> --dhcpbridge=/usr/bin/nova-dhcpbridge >>> --logdir=/var/log/nova >>> --state_path=/var/lib/nova >>> --lock_path=/var/lock/nova >>> --allow_admin_api=true >>> --use_deprecated_auth=false >>> --auth_strategy=keystone >>> --scheduler_driver=nova.scheduler.simple.SimpleScheduler >>> --s3_host=192.168.0.202 >>> --ec2_host=192.168.0.202 >>> --rabbit_host=192.168.0.202 >>> --cc_host=192.168.0.202 >>> --nova_url=http://192.168.0.202:8774/v1.1/ >>> --routing_source_ip=192.168.0.202 >>> --glance_api_servers=192.168.0.202:9292 >>> --image_service=nova.image.glance.GlanceImageService >>> --iscsi_ip_prefix=192.168.0 >>> --sql_connection=mysql://novadbadmin:[email protected]/nova >>> --ec2_url=http://192.168.0.202:8773/services/Cloud >>> --keystone_ec2_url=http://192.168.0.202:5000/v2.0/ec2tokens >>> --api_paste_config=/etc/nova/api-paste.ini >>> --libvirt_type=kvm >>> --libvirt_use_virtio_for_bridges=true >>> --start_guests_on_host_boot=false >>> --resume_guests_state_on_host_boot=false >>> >>> >>> --vnc_enabled=true >>> --novnc_enabled=true >>> --vncserver_listen=127.0.0.1 >>> --vncserver_proxyclient_address=127.0.0.1 >>> --novncproxy_base_url=http://192.168.0.202:6080/vnc_auto.html >>> --xvpvncproxy_base_url=http://192.168.0.202:6081/console >>> --xvpvncproxy_port=6081 >>> --novncproxy_port=65535 >>> # network specific settings >>> --network_manager=nova.network.manager.FlatDHCPManager >>> --public_interface=eth0 >>> --flat_interface=eth0 >>> --flat_network_bridge=br100 >>> --fixed_range=192.168.0.60/27 <http://192.168.0..60/27> >>> --floating_range=192.168.0.202/27 >>> --network_size=32 >>> --flat_network_dhcp_start=192.168.0.61 >>> --flat_injected=False >>> --force_dhcp_release >>> --iscsi_helper=tgtadm >>> --connection_type=libvirt >>> --root_helper=sudo nova-rootwrap >>> --verbose >>> >>> >>> I guess that's all the information I can give it for now . >>> I did a lot of googling ,and read ton of docs on openstack.org ..but >>> nothing seams help...... >>> Can someone please help me out of here ?...I almost get crazy about this >>> = = !...... >>> >>> >>> >>> -- >>> Stay with me,stay with my heart,honey..... >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~openstack >>> Post to : [email protected] >>> Unsubscribe : https://launchpad.net/~openstack >>> More help : https://help.launchpad.net/ListHelp >>> >>> ** > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
