ovirt-websocket-proxy uses the wrong IP
=0D=0A<font size=3D"2" face=3D"tahoma">Hello,<br><br>One of my nodes </f= ont><font size=3D"2" face=3D"tahoma">has two IP addresses, 10.42.0.101 an= d 10.42.0.103. Ovirt is configured to use 10.42.0.101, yet the ovirt-webs= ocket-proxy service tries 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 corre= ct address=3F<br><br>[root@engine ~]# /usr/share/ovirt-engine/services/ov= irt-websocket-proxy/ovirt-websocket-proxy.py --debug start<br>ovirt-webso= cket-proxy[1838] DEBUG _daemon:403 daemon entry pid=3D1838<br>ovirt-webso= cket-proxy[1838] DEBUG _daemon:404 background=3DFalse<br>ovirt-websocket-=
------=_Part_27_1351307630.1416086778054 Content-Type: multipart/alternative; boundary="=_diYpkdcCc+XflEeiQy00J5SerIjuuCS5jgM5BJ73AfiuYSQ8" This is a multi-part message in MIME format. Your mail reader does not understand MIME message format. --=_diYpkdcCc+XflEeiQy00J5SerIjuuCS5jgM5BJ73AfiuYSQ8 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello,=0D=0A=0D=0AOne of my nodes has two IP addresses, 10.42.0.101 and 1= 0.42.0.103. Ovirt is configured to use 10.42.0.101, yet the ovirt-websock= et-proxy service tries to connect to 10.42.0.103, where no VNC server is = listening.=0D=0A=0D=0AIs there any way I can configure it to use the corr= ect address=3F=0D=0A=0D=0A[root@engine ~]# /usr/share/ovirt-engine/servic= es/ovirt-websocket-proxy/ovirt-websocket-proxy.py --debug start=0D=0Aovir= t-websocket-proxy[1838] DEBUG _daemon:403 daemon entry pid=3D1838=0D=0Aov= irt-websocket-proxy[1838] DEBUG _daemon:404 background=3DFalse=0D=0Aovirt= -websocket-proxy[1838] DEBUG loadFile:70 loading config '/usr/share/ovirt= -engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.conf'=0D=0Ao= virt-websocket-proxy[1838] DEBUG loadFile:70 loading config '/etc/ovirt-e= ngine/ovirt-websocket-proxy.conf.d/10-setup.conf'=0D=0Aovirt-websocket-pr= oxy[1838] DEBUG _daemon:440 I am a daemon 1838=0D=0Aovirt-websocket-proxy= [1838] DEBUG _setLimits:377 Setting rlimits=0D=0AWebSocket server setting= s:=0D=0A=C2=A0 - Listen on *:6100=0D=0A=C2=A0 - Flash security policy ser= ver=0D=0A=C2=A0 - SSL/TLS support=0D=0A=C2=A0 - Deny non-SSL/TLS connecti= ons=0D=0A=C2=A0 - proxying from *:6100 to targets in /dummy=0D=0A=0D=0A=C2= =A0 1: 10.42.0.1: new handler Process=0D=0A=C2=A0 1: 10.42.0.1: SSL/TLS (= wss://) WebSocket connection=0D=0A=C2=A0 1: 10.42.0.1: Version hybi-13, b= ase64: 'True'=0D=0A=C2=A0 1: 10.42.0.1: Path: '/eyJ2YWxpZFRvIjoiMjAxNDExM= TUyMTI1MDgiLCJkYXRhIjoiJTdCJTIyaG9zdCUyMjolMjIxMC40Mi4wLjEwMyUyMiwlMjJwb3= J0JTIyOiUyMjU5MDElMjIsJTIyc3NsX3RhcmdldCUyMjpmYWxzZSU3RCIsInZhbGlkRnJvbSI= 6IjIwMTQxMTE1MjEyMzA4Iiwic2lnbmVkRmllbGRzIjoidmFsaWRUbyxkYXRhLHZhbGlkRnJv= bSxzYWx0Iiwic2lnbmF0dXJlIjoiajRQUmxwYjBvT0dOZUNPaHZKK01wUTVrVGRMYVA0Sm8zR= DIzTGlXRlZYRm4xNU9KN0NZVmw5OTBpNTBUNzlVZkpqUzRlRmZ1SHJhT1c4TlFNbXIwanZXSU= pTWCtnL3RYSnc4MWRFS2wrcFVPVHo3MWlmY2dTbXdITmptOUkwTTl6Q0NNR2dvbE1BRzZwMnd= FbDFySDdSZkhMWnIvOGo4bnpnVGZ0NlhaOTdBcHgyejhkMlo0UjRmdklXemtXMjErMDdsNWw4= dXpNVytEM1FmaWdDS1Q3V3VKdlFHNi9SSC9zZWRBWHJXcnFUNXYzTHNuNVl0MWtYb2lGV3ZYO= HNUdE5PdGdvQWk3eGN5WUhGaEM1ei9SMjZXNEkrSlJNcDZlVDNxbWVlZnM0eWRSN0NpZWwzZW= ZvZDB5TU9meGJwMG9EMGlscXVWUWVjK1JxeGxqd21ZVG5BPT0iLCJzYWx0IjoiWGhVQ1dYL2h= QU1U9In0=3D'=0D=0A=C2=A0 1: connecting to: 10.42.0.103:5901=0D=0A=C2=A0 1= : handler exception: [Errno 111] Connection refused=0D=0A=C2=A0 1: Traceb= ack (most recent call last):=0D=0A=C2=A0 File "/usr/lib/python2.6/site-pa= ckages/websockify/websocket.py", line 711, in top_new_client=0D=0A=C2=A0=C2= =A0=C2=A0 self.new_client()=0D=0A=C2=A0 File "/usr/lib/python2.6/site-pac= kages/websockify/websocketproxy.py", line 183, in new_client=0D=0A=C2=A0=C2= =A0=C2=A0 connect=3DTrue, use_ssl=3Dself.ssl_target, unix_socket=3Dself.u= nix_target)=0D=0A=C2=A0 File "/usr/lib/python2.6/site-packages/websockify= /websocket.py", line 188, in socket=0D=0A=C2=A0=C2=A0=C2=A0 sock.connect(= addrs[0][4])=0D=0A=C2=A0 File "<string>", line 1, in connect=0D=0Aerror: = [Errno 111] Connection refused=0D=0A=0D=0A=0D=0ARegards,=0D=0A=0D=0Amots=0D= =0A --=_diYpkdcCc+XflEeiQy00J5SerIjuuCS5jgM5BJ73AfiuYSQ8 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>ovirt-websocket-proxy uses the wrong IP</title>=0D=0A</head>=0D=0A<body= proxy[1838] DEBUG loadFile:70 loading config '/usr/share/ovirt-engine/ser= vices/ovirt-websocket-proxy/ovirt-websocket-proxy.conf'<br>ovirt-websocke= t-proxy[1838] DEBUG loadFile:70 loading config '/etc/ovirt-engine/ovirt-w= ebsocket-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 _set= Limits:377 Setting rlimits<br>WebSocket server settings:<br> - List= en on *:6100<br> - Flash security policy server<br> - SSL/TLS= support<br> - Deny non-SSL/TLS connections<br> - proxying fr= om *:6100 to targets in /dummy<br><br> 1: 10.42.0.1: new handler Pr= ocess<br> 1: 10.42.0.1: SSL/TLS (wss://) WebSocket connection<br>&n= bsp; 1: 10.42.0.1: Version hybi-13, base64: 'True'<br> 1: 10.42.0.1= : Path: '/eyJ2YWxpZFRvIjoiMjAxNDExMTUyMTI1MDgiLCJkYXRhIjoiJTdCJTIyaG9zdCU= yMjolMjIxMC40Mi4wLjEwMyUyMiwlMjJwb3J0JTIyOiUyMjU5MDElMjIsJTIyc3NsX3Rhcmdl= dCUyMjpmYWxzZSU3RCIsInZhbGlkRnJvbSI6IjIwMTQxMTE1MjEyMzA4Iiwic2lnbmVkRmllb= GRzIjoidmFsaWRUbyxkYXRhLHZhbGlkRnJvbSxzYWx0Iiwic2lnbmF0dXJlIjoiajRQUmxwYj= BvT0dOZUNPaHZKK01wUTVrVGRMYVA0Sm8zRDIzTGlXRlZYRm4xNU9KN0NZVmw5OTBpNTBUNzl= VZkpqUzRlRmZ1SHJhT1c4TlFNbXIwanZXSUpTWCtnL3RYSnc4MWRFS2wrcFVPVHo3MWlmY2dT= bXdITmptOUkwTTl6Q0NNR2dvbE1BRzZwMndFbDFySDdSZkhMWnIvOGo4bnpnVGZ0NlhaOTdBc= HgyejhkMlo0UjRmdklXemtXMjErMDdsNWw4dXpNVytEM1FmaWdDS1Q3V3VKdlFHNi9SSC9zZW= RBWHJXcnFUNXYzTHNuNVl0MWtYb2lGV3ZYOHNUdE5PdGdvQWk3eGN5WUhGaEM1ei9SMjZXNEk= rSlJNcDZlVDNxbWVlZnM0eWRSN0NpZWwzZWZvZDB5TU9meGJwMG9EMGlscXVWUWVjK1JxeGxq= d21ZVG5BPT0iLCJzYWx0IjoiWGhVQ1dYL2hQU1U9In0=3D'<br> 1: connecting t= o: 10.42.0.103:5901<br> 1: handler exception: [Errno 111] Connectio= n refused<br> 1: Traceback (most recent call last):<br> File = "/usr/lib/python2.6/site-packages/websockify/websocket.py", line 711, in = top_new_client<br> self.new_client()<br> File "/u= sr/lib/python2.6/site-packages/websockify/websocketproxy.py", line 183, i= n new_client<br> connect=3DTrue, use_ssl=3Dself.ssl_tar= get, unix_socket=3Dself.unix_target)<br> File "/usr/lib/python2.6/s= ite-packages/websockify/websocket.py", line 188, in 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></font>=0D=0A</body>=0D=0A</html> --=_diYpkdcCc+XflEeiQy00J5SerIjuuCS5jgM5BJ73AfiuYSQ8-- ------=_Part_27_1351307630.1416086778054 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) iQEcBAEBCAAGBQJUZ8T6AAoJELfzdzVzTtoK3K0H/2O2w3FZAvdP+AxXEzwrZIMR W9dBZ8yuX3gyhzu5LdANuu4BVjMStfJ1bK4VdWyyp2DquR5hVtbBv1C3obBquDok rxByShXWm5YdVvWaDzxHiUtTuIqy0vqfQgp8KDHRUOubhqSEfqHFuAs/GOLJqlSv x/mo4lSrQ5IK+OiNh83fEw+S9Y5O5lems0IT3XQH6xRR7YBP0Dt0b4Rdg+qSt9GH 3VYFnxbYAY7mp7tCQPJUGSBwuclOMNgHLSGa9FapFKnFm6+ionXCuEoQFc19F7z4 u5QrogtXjTAqp26/VKW1RiSkgtbQZhLHz8xYQAuav6VKALpwTaGOwLKN4O+jYo4= =Tx0F -----END PGP SIGNATURE----- ------=_Part_27_1351307630.1416086778054--
----- Original Message -----
From: "mots" <mots@nepu.moe> To: users@ovirt.org Sent: Saturday, November 15, 2014 10:24:29 PM Subject: [ovirt-users] ovirt-websocket-proxy uses the wrong IP
ovirt-websocket-proxy uses the wrong IP Hello,
One of my nodes has two IP addresses, 10.42.0.101 and 10.42.0.103. Ovirt is configured to use 10.42.0.101, yet the ovirt-websocket-proxy service tries to connect to 10.42.0.103, where no VNC server is listening.
Is there any way I can configure it to use the correct address?
[root@engine ~]# /usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.py --debug start ovirt-websocket-proxy[1838] DEBUG _daemon:403 daemon entry pid=1838 ovirt-websocket-proxy[1838] DEBUG _daemon:404 background=False ovirt-websocket-proxy[1838] DEBUG loadFile:70 loading config '/usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.conf' ovirt-websocket-proxy[1838] DEBUG loadFile:70 loading config '/etc/ovirt-engine/ovirt-websocket-proxy.conf.d/10-setup.conf' ovirt-websocket-proxy[1838] DEBUG _daemon:440 I am a daemon 1838 ovirt-websocket-proxy[1838] DEBUG _setLimits:377 Setting rlimits WebSocket server settings: - Listen on *:6100
The WebSocketProxy is listening on all the available IPs, so no problems on that side.
- Flash security policy server - SSL/TLS support - Deny non-SSL/TLS connections - proxying from *:6100 to targets in /dummy
1: 10.42.0.1: new handler Process 1: 10.42.0.1: SSL/TLS (wss://) WebSocket connection 1: 10.42.0.1: Version hybi-13, base64: 'True' 1: 10.42.0.1: Path: '/eyJ2YWxpZFRvIjoiMjAxNDExMTUyMTI1MDgiLCJkYXRhIjoiJTdCJTIyaG9zdCUyMjolMjIxMC40Mi4wLjEwMyUyMiwlMjJwb3J0JTIyOiUyMjU5MDElMjIsJTIyc3NsX3RhcmdldCUyMjpmYWxzZSU3RCIsInZhbGlkRnJvbSI6IjIwMTQxMTE1MjEyMzA4Iiwic2lnbmVkRmllbGRzIjoidmFsaWRUbyxkYXRhLHZhbGlkRnJvbSxzYWx0Iiwic2lnbmF0dXJlIjoiajRQUmxwYjBvT0dOZUNPaHZKK01wUTVrVGRMYVA0Sm8zRDIzTGlXRlZYRm4xNU9KN0NZVmw5OTBpNTBUNzlVZkpqUzRlRmZ1SHJhT1c4TlFNbXIwanZXSUpTWCtnL3RYSnc4MWRFS2wrcFVPVHo3MWlmY2dTbXdITmptOUkwTTl6Q0NNR2dvbE1BRzZwMndFbDFySDdSZkhMWnIvOGo4bnpnVGZ0NlhaOTdBcHgyejhkMlo0UjRmdklXemtXMjErMDdsNWw4dXpNVytEM1FmaWdDS1Q3V3VKdlFHNi9SSC9zZWRBWHJXcnFUNXYzTHNuNVl0MWtYb2lGV3ZYOHNUdE5PdGdvQWk3eGN5WUhGaEM1ei9SMjZXNEkrSlJNcDZlVDNxbWVlZnM0eWRSN0NpZWwzZWZvZDB5TU9meGJwMG9EMGlscXVWUWVjK1JxeGxqd21ZVG5BPT0iLCJzYWx0IjoiWGhVQ1dYL2hQU1U9In0=' 1: connecting to: 10.42.0.103:5901
The engine is instructing the WebSocket proxy to connect to the host on the wrong IP address. Are you using an all-in-one setup where the engine, KVM and the websocketproxy are on a single machine? Can you please check how the engine machine resolve the host name?
1: handler exception: [Errno 111] Connection refused 1: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/websockify/websocket.py", line 711, in top_new_client self.new_client() File "/usr/lib/python2.6/site-packages/websockify/websocketproxy.py", line 183, in new_client connect=True, use_ssl=self.ssl_target, unix_socket=self.unix_target) File "/usr/lib/python2.6/site-packages/websockify/websocket.py", line 188, in socket sock.connect(addrs[0][4]) File "<string>", line 1, in connect error: [Errno 111] Connection refused
Regards,
mots
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (2)
-
mots -
Simone Tiraboschi