<div dir="ltr">Hi Jacob, you were right, i had a problem in the nova.conf of the new compute node. The vncserver_proxyclient_address  was pointing to the wrong IP, i changed it, restarted nova in the compute-node and novncproxy in the controller and everything worked fine! Thanks!!</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">2013/4/8 Jacob Liberman <span dir="ltr"><<a href="mailto:jliberma@redhat.com" target="_blank">jliberma@redhat.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    what is the vnc server listen address in /etc/nova/nova.conf  should
    be unique to each compute node<br>
    <br>
    the vnc proxy should be the same across all the compute nodes<br>
    <br>
    [root@rhos0 ~(keystone_admin)]$ for i in 2 3 4 5; do ssh rhos$i grep
    vnc /etc/nova/nova.conf; done | grep -v \#<br>
    novncproxy_base_url=<a href="http://10.16.137.100:6080/vnc_auto.html" target="_blank">http://10.16.137.100:6080/vnc_auto.html</a><br>
    vncserver_listen=10.16.137.102<br>
    vncserver_proxyclient_address=10.16.137.102<br>
    vnc_enabled=true<br>
    novncproxy_base_url=<a href="http://10.16.137.100:6080/vnc_auto.html" target="_blank">http://10.16.137.100:6080/vnc_auto.html</a><br>
    vncserver_listen=10.16.137.103<br>
    vncserver_proxyclient_address=10.16.137.103<br>
    vnc_enabled=true<br>
    novncproxy_base_url=<a href="http://10.16.137.100:6080/vnc_auto.html" target="_blank">http://10.16.137.100:6080/vnc_auto.html</a><br>
    vncserver_listen=10.16.137.104<br>
    vncserver_proxyclient_address=10.16.137.104<br>
    vnc_enabled=true<br>
    novncproxy_base_url=<a href="http://10.16.137.100:6080/vnc_auto.html" target="_blank">http://10.16.137.100:6080/vnc_auto.html</a><br>
    vncserver_listen=10.16.137.105<br>
    vncserver_proxyclient_address=10.16.137.105<br>
    vnc_enabled=true<br>
    <br>
    <br>
    thanks, jacob<div><div class="h5"><br>
    <br>
    <br>
    On 04/08/2013 05:03 PM, Juan José Pavlik Salles wrote:
    </div></div><blockquote type="cite"><div><div class="h5">
      <div dir="ltr">Hi guys, today i added my second compute-node to my
        folsom deploy. After configuring everything i launched 2 VMs.
        One of the VMs is running on the new node, awesome i said!, but
        when i tried to open VNC (from the dashboard) i always get just
        the console of the VM running on the first compute-node i added.
        <div>
          <br>
        </div>
        <div>What i see is on the first compute node is 2 tcp
          connections to KVM:</div>
        <div><br>
        </div>
        <div>
          <div>tcp        0      0 <a href="http://172.19.136.20:5900" target="_blank">172.19.136.20:5900</a>  
               <a href="http://172.19.136.1:53082" target="_blank">172.19.136.1:53082</a>  
               ESTABLECIDO 37988/kvm        </div>
          <div>tcp        0      0 <a href="http://172.19.136.20:5900" target="_blank">172.19.136.20:5900</a>  
               <a href="http://172.19.136.1:53107" target="_blank">172.19.136.1:53107</a>  
               ESTABLECIDO 37988/kvm  </div>
          <div><br>
          </div>
          <div>But i don't see any on the new compute node. So
            i assume that somehow, the VNC from dashboard is connecting
            to the same console instead of the one in the VM running in
            the new compute-node.</div>
          <div><br>
          </div>
          <div>I may have forgotten something in this new
            compute-node, but i can't figure it out. </div>
          <div><br>
          </div>
          <div>The new VM is running on 172.19.136.21 (my new
            compute-node) so i should see one connection on this host to
            5900 TCP, but instead of this, both connections go to
            172.19.136.20.</div>
          <div><br>
          </div>
          <div>I ran nova-novncproxy and i saw that no matter
            what VM i choose it always connects to: </div>
          <div>
            <div><br>
            </div>
            <div> 21: connecting to: <a href="http://172.19.136.20:5900" target="_blank">172.19.136.20:5900</a></div>
            <div><br>
            </div>
            <div>Any ideas?? Thanks!</div>
            <div><br>
            </div>
          </div>
          -- <br>
          Pavlik Juan José
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      </div></div><pre>_______________________________________________
OpenStack-operators mailing list
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
</pre>
    </blockquote>
    <br>
  </div>

<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Pavlik Juan José
</div>