<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
<head>
<meta name="Generator" content="Zarafa WebApp v7.1.10-44973">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>AW: [ovirt-users] ovirt-websocket-proxy uses the wrong IP</title>
</head>
<body>
<font face="tahoma" size="2">Thank you for your reply.<br><br>The engine resolves the node's IP correctly. A few details about the setup: It's a two node cluster with shared, internal storage using DRBD. The storage is managed by pacemaker, so that the node which currently serves as iscsi target gets assigned the additional IP. <br>The Engine/websocket-proxy then always connects to the storage IP when it attempts to connect to the node which currently functions as iscsi target. This only happens in oVirt 3.5, and I was able to "fix" it by going back to 3.4.<br></font><pre style="white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; white-space: pre-wrap; word-wrap: break-word;" wrap="">Regards,<br><br>mots<br> <br>-----Ursprüngliche Nachricht-----<br>> Von:Simone Tiraboschi <<a href="mailto:stirabos@redhat.com">stirabos@redhat.com</a>><br>> Gesendet: Mon 17 November 2014 18:11<br>> An: Patrick Lottenbach <<a href="mailto:pl@a-bot.ch">pl@a-bot.ch</a>><br>> CC: <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>> Betreff: Re: [ovirt-users] ovirt-websocket-proxy uses the wrong IP<br>> <br>> <br>> <br>> <br>> <br>> ----- Original Message -----<br>> > From: "mots" <<a href="mailto:mots@nepu.moe">mots@nepu.moe</a>><br>> > To: <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>> > Sent: Saturday, November 15, 2014 10:24:29 PM<br>> > Subject: [ovirt-users] ovirt-websocket-proxy uses the wrong IP<br>> > <br>> > ovirt-websocket-proxy uses the wrong IP Hello,<br>> > <br>> > One of my nodes has two IP addresses, 10.42.0.101 and 10.42.0.103. Ovirt is<br>> > configured to use 10.42.0.101, yet the ovirt-websocket-proxy service tries<br>> > to connect to 10.42.0.103, where no VNC server is listening.<br>> > <br>> > Is there any way I can configure it to use the correct address?<br>> > <br>> > [root@engine ˜]#<br>> > /usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.py<br>> > --debug start<br>> > ovirt-websocket-proxy[1838] DEBUG _daemon:403 daemon entry pid=1838<br>> > ovirt-websocket-proxy[1838] DEBUG _daemon:404 background=False<br>> > ovirt-websocket-proxy[1838] DEBUG loadFile:70 loading config<br>> > '/usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.conf'<br>> > ovirt-websocket-proxy[1838] DEBUG loadFile:70 loading config<br>> > '/etc/ovirt-engine/ovirt-websocket-proxy.conf.d/10-setup.conf'<br>> > ovirt-websocket-proxy[1838] DEBUG _daemon:440 I am a daemon 1838<br>> > ovirt-websocket-proxy[1838] DEBUG _setLimits:377 Setting rlimits<br>> > WebSocket server settings:<br>> > - Listen on *:6100<br>> <br>> The WebSocketProxy is listening on all the available IPs, so no problems on that side.<br>> <br>> > - Flash security policy server<br>> > - SSL/TLS support<br>> > - Deny non-SSL/TLS connections<br>> > - proxying from *:6100 to targets in /dummy<br>> > <br>> > 1: 10.42.0.1: new handler Process<br>> > 1: 10.42.0.1: SSL/TLS (wss://) WebSocket connection<br>> > 1: 10.42.0.1: Version hybi-13, base64: 'True'<br>> > 1: 10.42.0.1: Path:<br>> > '/eyJ2YWxpZFRvIjoiMjAxNDExMTUyMTI1MDgiLCJkYXRhIjoiJTdCJTIyaG9zdCUyMjolMjIxMC40Mi4wLjEwMyUyMiwlMjJwb3J0JTIyOiUyMjU5MDElMjIsJTIyc3NsX3RhcmdldCUyMjpmYWxzZSU3RCIsInZhbGlkRnJvbSI6IjIwMTQxMTE1MjEyMzA4Iiwic2lnbmVkRmllbGRzIjoidmFsaWRUbyxkYXRhLHZhbGlkRnJvbSxzYWx0Iiwic2lnbmF0dXJlIjoiajRQUmxwYjBvT0dOZUNPaHZKK01wUTVrVGRMYVA0Sm8zRDIzTGlXRlZYRm4xNU9KN0NZVmw5OTBpNTBUNzlVZkpqUzRlRmZ1SHJhT1c4TlFNbXIwanZXSUpTWCtnL3RYSnc4MWRFS2wrcFVPVHo3MWlmY2dTbXdITmptOUkwTTl6Q0NNR2dvbE1BRzZwMndFbDFySDdSZkhMWnIvOGo4bnpnVGZ0NlhaOTdBcHgyejhkMlo0UjRmdklXemtXMjErMDdsNWw4dXpNVytEM1FmaWdDS1Q3V3VKdlFHNi9SSC9zZWRBWHJXcnFUNXYzTHNuNVl0MWtYb2lGV3ZYOHNUdE5PdGdvQWk3eGN5WUhGaEM1ei9SMjZXNEkrSlJNcDZlVDNxbWVlZnM0eWRSN0NpZWwzZWZvZDB5TU9meGJwMG9EMGlscXVWUWVjK1JxeGxqd21ZVG5BPT0iLCJzYWx0IjoiWGhVQ1dYL2hQU1U9In0='<br>> > 1: connecting to: 10.42.0.103:5901<br>> <br>> The engine is instructing the WebSocket proxy to connect to the host on the wrong IP address.<br>> Are you using an all-in-one setup where the engine, KVM and the websocketproxy are on a single machine?<br>> Can you please check how the engine machine resolve the host name?<br>> <br>> <br>> > 1: handler exception: [Errno 111] Connection refused<br>> > 1: Traceback (most recent call last):<br>> > File "/usr/lib/python2.6/site-packages/websockify/websocket.py", line 711, in<br>> > top_new_client<br>> > self.new_client()<br>> > File "/usr/lib/python2.6/site-packages/websockify/websocketproxy.py", line<br>> > 183, in new_client<br>> > connect=True, use_ssl=self.ssl_target, unix_socket=self.unix_target)<br>> > File "/usr/lib/python2.6/site-packages/websockify/websocket.py", line 188, in<br>> > socket<br>> > sock.connect(addrs[0][4])<br>> > File "<string>", line 1, in connect<br>> > error: [Errno 111] Connection refused<br>> > <br>> > <br>> > Regards,<br>> > <br>> > mots<br>> > <br>> > _______________________________________________<br>> > Users mailing list<br>> > <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>> > <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>> > <br>> </pre>
</body>
</html>