It is hard to debug websocket proxy currently. In current version, we can catch extra information from ovirt-websocket-proxy service by edditing "/etc/init.d/ovirt-websocket-proxy" file, removing "--redirect-output \" (line 44). The daemon output then goes to the console. Please improve ovirt-websocket-proxy log, by redirecting daemon outputs/debbug messages to a log file in "/var/log" directory.
should be simple, just need to pick up the new python-websockify and finish up the posted patch
This is not an RFE (hence removed the RFE from title)
ok, rhevm-websocket-proxy-3.6.0.3-0.1.el6.noarch [root@jb-rhevm36 tmp]# grep -i 'websocket.*trace' /var/log/messages Nov 4 18:14:16 jb-rhevm36 2015-11-04 18:14:16,942 ovirt-websocket-proxy: INFO msg:824 - Recording to '/tmp/websocketproxy_trace.log.*' [root@jb-rhevm36 tmp]# ls -l /tmp/websocketproxy_trace.log* -rw-r--r--. 1 ovirt ovirt 1024000 Nov 4 18:18 /tmp/websocketproxy_trace.log.2 -rw-r--r--. 1 ovirt ovirt 0 Nov 4 18:18 /tmp/websocketproxy_trace.log.3 -rw-r--r--. 1 ovirt ovirt 131072 Nov 4 18:18 /tmp/websocketproxy_trace.log.4 -rw-r--r--. 1 ovirt ovirt 0 Nov 4 18:18 /tmp/websocketproxy_trace.log.5 [root@jb-rhevm36 tmp]# cat /etc/ovirt-engine/ovirt-websocket-proxy.conf.d/00-my.conf TRACE_ENABLE=True TRACE_FILE=/tmp/websocketproxy_trace.log