[ovirt-users] ovirt-websocket-proxy uses the wrong IP

[Simone Tiraboschi]

----- Original Message -----
> From: "mots" <mots at nepu.moe>
> To: users at 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 at 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 at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>