------=_Part_36_779334652.1416253714037
Content-Type: multipart/alternative;
 boundary="=_B2Bqz28RlRkiQt0tI2lBQMQUJD-DsqIJ4LiGs35u4K91tsvv"

This is a multi-part message in MIME format. Your mail reader does not
understand MIME message format.
--=_B2Bqz28RlRkiQt0tI2lBQMQUJD-DsqIJ4LiGs35u4K91tsvv
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Thank you for your reply.=0D=0A=0D=0AThe engine resolves the node's IP co=
rrectly. A few details about the setup: It's a two node cluster with shar=
ed, internal storage using DRBD. The storage is managed by pacemaker, so =
that the node which currently serves as iscsi target gets assigned the ad=
ditional IP.=20=0D=0AThe Engine/websocket-proxy then always connects to t=
he storage IP when it attempts to connect to the node which currently fun=
ctions as iscsi target. This only happens in oVirt 3.5, and I was able to=
 "fix" it by going back to 3.4.=0D=0A=0D=0ARegards,=0D=0A=0D=0Amots=0D=0A=
=20=0D=0A-----Urspr=C3=BCngliche Nachricht-----=0D=0A> Von:Simone Tirabos=
chi <stirabos@redhat.com <mailto:stirabos@redhat.com> >=0D=0A> Gesendet: =
Mon 17 November 2014 18:11=0D=0A> An: Patrick Lottenbach <pl@a-bot.ch <ma=
ilto:pl@a-bot.ch> >=0D=0A> CC: users@ovirt.org <mailto:users@ovirt.org>=20=
=0D=0A> Betreff: Re: [ovirt-users] ovirt-websocket-proxy uses the wrong I=
P=0D=0A>=20=0D=0A>=20=0D=0A>=20=0D=0A>=20=0D=0A>=20=0D=0A> ----- Original=
 Message -----=0D=0A> > From: "mots" <mots@nepu.moe <mailto:mots@nepu.moe=
> >=0D=0A> > To: users@ovirt.org <mailto:users@ovirt.org>=20=0D=0A> > Sen=
t: Saturday, November 15, 2014 10:24:29 PM=0D=0A> > Subject: [ovirt-users=
] ovirt-websocket-proxy uses the wrong IP=0D=0A> >=20=0D=0A> > ovirt-webs=
ocket-proxy uses the wrong IP Hello,=0D=0A> >=20=0D=0A> > One of my nodes=
 has two IP addresses, 10.42.0.101 and 10.42.0.103. Ovirt is=0D=0A> > con=
figured to use 10.42.0.101, yet the ovirt-websocket-proxy service tries=0D=
=0A> > to connect to 10.42.0.103, where no VNC server is listening.=0D=0A=
> >=20=0D=0A> > Is there any way I can configure it to use the correct ad=
dress=3F=0D=0A> >=20=0D=0A> > [root@engine =CB=9C]#=0D=0A> > /usr/share/o=
virt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.py=0D=0A=
> > --debug start=0D=0A> > ovirt-websocket-proxy[1838] DEBUG _daemon:403 =
daemon entry pid=3D1838=0D=0A> > ovirt-websocket-proxy[1838] DEBUG _daemo=
n:404 background=3DFalse=0D=0A> > ovirt-websocket-proxy[1838] DEBUG loadF=
ile:70 loading config=0D=0A> > '/usr/share/ovirt-engine/services/ovirt-we=
bsocket-proxy/ovirt-websocket-proxy.conf'=0D=0A> > ovirt-websocket-proxy[=
1838] DEBUG loadFile:70 loading config=0D=0A> > '/etc/ovirt-engine/ovirt-=
websocket-proxy.conf.d/10-setup.conf'=0D=0A> > ovirt-websocket-proxy[1838=
] DEBUG _daemon:440 I am a daemon 1838=0D=0A> > ovirt-websocket-proxy[183=
8] DEBUG _setLimits:377 Setting rlimits=0D=0A> > WebSocket server setting=
s:=0D=0A> > - Listen on *:6100=0D=0A>=20=0D=0A> The WebSocketProxy is lis=
tening on all the available IPs, so no problems on that side.=0D=0A>=20=0D=
=0A> > - Flash security policy server=0D=0A> > - SSL/TLS support=0D=0A> >=
 - Deny non-SSL/TLS connections=0D=0A> > - proxying from *:6100 to target=
s in /dummy=0D=0A> >=20=0D=0A> > 1: 10.42.0.1: new handler Process=0D=0A>=
 > 1: 10.42.0.1: SSL/TLS (wss://) WebSocket connection=0D=0A> > 1: 10.42.=
0.1: Version hybi-13, base64: 'True'=0D=0A> > 1: 10.42.0.1: Path:=0D=0A> =
> '/eyJ2YWxpZFRvIjoiMjAxNDExMTUyMTI1MDgiLCJkYXRhIjoiJTdCJTIyaG9zdCUyMjolM=
jIxMC40Mi4wLjEwMyUyMiwlMjJwb3J0JTIyOiUyMjU5MDElMjIsJTIyc3NsX3RhcmdldCUyMj=
pmYWxzZSU3RCIsInZhbGlkRnJvbSI6IjIwMTQxMTE1MjEyMzA4Iiwic2lnbmVkRmllbGRzIjo=
idmFsaWRUbyxkYXRhLHZhbGlkRnJvbSxzYWx0Iiwic2lnbmF0dXJlIjoiajRQUmxwYjBvT0dO=
ZUNPaHZKK01wUTVrVGRMYVA0Sm8zRDIzTGlXRlZYRm4xNU9KN0NZVmw5OTBpNTBUNzlVZkpqU=
zRlRmZ1SHJhT1c4TlFNbXIwanZXSUpTWCtnL3RYSnc4MWRFS2wrcFVPVHo3MWlmY2dTbXdITm=
ptOUkwTTl6Q0NNR2dvbE1BRzZwMndFbDFySDdSZkhMWnIvOGo4bnpnVGZ0NlhaOTdBcHgyejh=
kMlo0UjRmdklXemtXMjErMDdsNWw4dXpNVytEM1FmaWdDS1Q3V3VKdlFHNi9SSC9zZWRBWHJX=
cnFUNXYzTHNuNVl0MWtYb2lGV3ZYOHNUdE5PdGdvQWk3eGN5WUhGaEM1ei9SMjZXNEkrSlJNc=
DZlVDNxbWVlZnM0eWRSN0NpZWwzZWZvZDB5TU9meGJwMG9EMGlscXVWUWVjK1JxeGxqd21ZVG=
5BPT0iLCJzYWx0IjoiWGhVQ1dYL2hQU1U9In0=3D'=0D=0A> > 1: connecting to: 10.4=
2.0.103:5901=0D=0A>=20=0D=0A> The engine is instructing the WebSocket pro=
xy to connect to the host on the wrong IP address.=0D=0A> Are you using a=
n all-in-one setup where the engine, KVM and the websocketproxy are on a =
single machine=3F=0D=0A> Can you please check how the engine machine reso=
lve the host name=3F=0D=0A>=20=0D=0A>=20=0D=0A> > 1: handler exception: [=
Errno 111] Connection refused=0D=0A> > 1: Traceback (most recent call las=
t):=0D=0A> > File "/usr/lib/python2.6/site-packages/websockify/websocket.=
py", line 711, in=0D=0A> > top_new_client=0D=0A> > self.new_client()=0D=0A=
> > File "/usr/lib/python2.6/site-packages/websockify/websocketproxy.py",=
 line=0D=0A> > 183, in new_client=0D=0A> > connect=3DTrue, use_ssl=3Dself=
=2Essl_target, unix_socket=3Dself.unix_target)=0D=0A> > File "/usr/lib/py=
thon2.6/site-packages/websockify/websocket.py", line 188, in=0D=0A> > soc=
ket=0D=0A> > sock.connect(addrs[0][4])=0D=0A> > File "<string>", line 1, =
in connect=0D=0A> > error: [Errno 111] Connection refused=0D=0A> >=20=0D=0A=
> >=20=0D=0A> > Regards,=0D=0A> >=20=0D=0A> > mots=0D=0A> >=20=0D=0A> > _=
______________________________________________=0D=0A> > Users mailing lis=
t=0D=0A> > Users@ovirt.org <mailto:Users@ovirt.org>=20=0D=0A> > http://li=
sts.ovirt.org/mailman/listinfo/users <http://lists.ovirt.org/mailman/list=
info/users>=20=0D=0A> >=20=0D=0A>=20=0D=0A=0D=0A
--=_B2Bqz28RlRkiQt0tI2lBQMQUJD-DsqIJ4LiGs35u4K91tsvv
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

=0D=0A<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "htt=
p://www.w3.org/TR/html4/loose.dtd"><html>=0D=0A<head>=0D=0A  <meta name=3D=
"Generator" content=3D"Zarafa WebApp v7.1.10-44973">=0D=0A  <meta http-eq=
uiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">=0D=0A  <titl=
e>AW: [ovirt-users] ovirt-websocket-proxy uses the wrong IP</title>=0D=0A=
</head>=0D=0A<body>=0D=0A<font face=3D"tahoma" size=3D"2">Thank you for y=
our reply.<br><br>The engine resolves the node's IP correctly. A few deta=
ils about the setup: It's a two node cluster with shared, internal storag=
e using DRBD. The storage is managed by pacemaker, so that the node which=
 currently serves as iscsi target gets assigned the additional IP. <br>Th=
e Engine/websocket-proxy then always connects to the storage IP when it a=
ttempts 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=3D"white-space: -moz-pre-wrap; white-space:=
 -pre-wrap; white-space: -o-pre-wrap; white-space: pre-wrap; word-wrap: b=
reak-word;" wrap=3D"">Regards,<br><br>mots<br> <br>-----Urspr=C3=BCnglich=
e Nachricht-----<br>> Von:Simone Tiraboschi <<a href=3D"mailto:stir=
abos@redhat.com">stirabos@redhat.com</a>><br>> Gesendet: Mon 17 Nov=
ember 2014 18:11<br>> An: Patrick Lottenbach <<a href=3D"mailto:pl@=
a-bot.ch">pl@a-bot.ch</a>><br>> CC: <a href=3D"mailto:users@ovirt.o=
rg">users@ovirt.org</a><br>> Betreff: Re: [ovirt-users] ovirt-websocke=
t-proxy uses the wrong IP<br>> <br>> <br>> <br>> <br>> <br=
>> ----- Original Message -----<br>> > From: "mots" <<a href=3D=
"mailto:mots@nepu.moe">mots@nepu.moe</a>><br>> > To: <a href=3D"=
mailto:users@ovirt.org">users@ovirt.org</a><br>> > Sent: Saturday, =
November 15, 2014 10:24:29 PM<br>> > Subject: [ovirt-users] ovirt-w=
ebsocket-proxy uses the wrong IP<br>> > <br>> > ovirt-websock=
et-proxy uses the wrong IP Hello,<br>> > <br>> > One of my no=
des has two IP addresses, 10.42.0.101 and 10.42.0.103. Ovirt is<br>> &=
gt; 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 list=
ening.<br>> > <br>> > Is there any way I can configure it to =
use the correct address=3F<br>> > <br>> > [root@engine =CB=9C=
]#<br>> > /usr/share/ovirt-engine/services/ovirt-websocket-proxy/ov=
irt-websocket-proxy.py<br>> > --debug start<br>> > ovirt-webs=
ocket-proxy[1838] DEBUG _daemon:403 daemon entry pid=3D1838<br>> > =
ovirt-websocket-proxy[1838] DEBUG _daemon:404 background=3DFalse<br>> =
> ovirt-websocket-proxy[1838] DEBUG loadFile:70 loading config<br>>=
 > '/usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-webso=
cket-proxy.conf'<br>> > ovirt-websocket-proxy[1838] DEBUG loadFile:=
70 loading config<br>> > '/etc/ovirt-engine/ovirt-websocket-proxy.c=
onf.d/10-setup.conf'<br>> > ovirt-websocket-proxy[1838] DEBUG _daem=
on: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 list=
ening on all the available IPs, so no problems on that side.<br>> <br>=
> > - Flash security policy server<br>> > - SSL/TLS support<b=
r>> > - Deny non-SSL/TLS connections<br>> > - proxying from *=
:6100 to targets in /dummy<br>> > <br>> > 1: 10.42.0.1: new h=
andler Process<br>> > 1: 10.42.0.1: SSL/TLS (wss://) WebSocket conn=
ection<br>> > 1: 10.42.0.1: Version hybi-13, base64: 'True'<br>>=
 > 1: 10.42.0.1: Path:<br>> > '/eyJ2YWxpZFRvIjoiMjAxNDExMTUyMTI1=
MDgiLCJkYXRhIjoiJTdCJTIyaG9zdCUyMjolMjIxMC40Mi4wLjEwMyUyMiwlMjJwb3J0JTIyO=
iUyMjU5MDElMjIsJTIyc3NsX3RhcmdldCUyMjpmYWxzZSU3RCIsInZhbGlkRnJvbSI6IjIwMT=
QxMTE1MjEyMzA4Iiwic2lnbmVkRmllbGRzIjoidmFsaWRUbyxkYXRhLHZhbGlkRnJvbSxzYWx=
0Iiwic2lnbmF0dXJlIjoiajRQUmxwYjBvT0dOZUNPaHZKK01wUTVrVGRMYVA0Sm8zRDIzTGlX=
RlZYRm4xNU9KN0NZVmw5OTBpNTBUNzlVZkpqUzRlRmZ1SHJhT1c4TlFNbXIwanZXSUpTWCtnL=
3RYSnc4MWRFS2wrcFVPVHo3MWlmY2dTbXdITmptOUkwTTl6Q0NNR2dvbE1BRzZwMndFbDFySD=
dSZkhMWnIvOGo4bnpnVGZ0NlhaOTdBcHgyejhkMlo0UjRmdklXemtXMjErMDdsNWw4dXpNVyt=
EM1FmaWdDS1Q3V3VKdlFHNi9SSC9zZWRBWHJXcnFUNXYzTHNuNVl0MWtYb2lGV3ZYOHNUdE5P=
dGdvQWk3eGN5WUhGaEM1ei9SMjZXNEkrSlJNcDZlVDNxbWVlZnM0eWRSN0NpZWwzZWZvZDB5T=
U9meGJwMG9EMGlscXVWUWVjK1JxeGxqd21ZVG5BPT0iLCJzYWx0IjoiWGhVQ1dYL2hQU1U9In=
0=3D'<br>> > 1: connecting to: 10.42.0.103:5901<br>> <br>> Th=
e 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 en=
gine, KVM and the websocketproxy are on a single machine=3F<br>> Can y=
ou please check how the engine machine resolve the host name=3F<br>> <=
br>> <br>> > 1: handler exception: [Errno 111] Connection refuse=
d<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>> > Fil=
e "/usr/lib/python2.6/site-packages/websockify/websocketproxy.py", line<b=
r>> > 183, in new_client<br>> > connect=3DTrue, use_ssl=3Dsel=
f.ssl_target, unix_socket=3Dself.unix_target)<br>> > File "/usr/lib=
/python2.6/site-packages/websockify/websocket.py", line 188, in<br>> &=
gt; socket<br>> > sock.connect(addrs[0][4])<br>> > File "<=
string>", line 1, in connect<br>> > error: [Errno 111] Connectio=
n refused<br>> > <br>> > <br>> > Regards,<br>> > =
<br>> > mots<br>> > <br>> > ___________________________=
____________________<br>> > Users mailing list<br>> > <a href=
=3D"mailto:Users@ovirt.org">Users@ovirt.org</a><br>> > <a href=3D"h=
ttp://lists.ovirt.org/mailman/listinfo/users" target=3D"_blank">http://li=
sts.ovirt.org/mailman/listinfo/users</a><br>> > <br>> </pre>=0D=0A=
</body>=0D=0A</html>
--=_B2Bqz28RlRkiQt0tI2lBQMQUJD-DsqIJ4LiGs35u4K91tsvv--

------=_Part_36_779334652.1416253714037
Content-Type: application/pgp-signature; name=signature.asc
Content-Transfer-Encoding: 7bit
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: CIPHERMAIL (2.8.6-4)

iQEcBAEBCAAGBQJUalESAAoJELfzdzVzTtoKeF0H/1YQt1E5Xa6ddb/QDmr+a0xm
l0YZi8SP2bDvKsktd5u1skXpXp5BMhYYQL77P9/dvg/nUudz5Pv+MNLtMc/VeWoS
X46jIJBsL8l+eg5hTa/LocJZ2mBRkZnbwSYUuNKFNrHc7hDhWXwNBZsObrXsBQIK
4wllZgmAhm+yUxX2S2oWDRF76XkuSnQdGLjVHySfrD4/ko39+hQyOZWjKNFUlNB2
WXwfI6xurJDccVWW9wLndt6JO8s2uKf2NcDLSDaY1abi2gFEqx1iIFxY3v4YV+LT
tIc4HwK/BqE+HusOVAxLL20tvV4ki+2/2g4jsYmXjpPYyWByLspV1IcHKnbtbpw=
=u///
-----END PGP SIGNATURE-----

------=_Part_36_779334652.1416253714037--