Svncterm location/directory

Hi,
My configuration looks like that, (centos7/arm64). I have compiled the svncterm tool for centos7. Where is the exact location of the svncterm?
Here is the log output, that make sense for the gurus.

[root@node01 ~]# tail -f /var/log/one/novnc.log
192.168.1.100: SSL connection but ‘/self.pem’ not found
192.168.1.100: SSL connection but ‘/self.pem’ not found
192.168.1.100: SSL connection but ‘/self.pem’ not found
192.168.1.100: SSL connection but ‘/self.pem’ not found
192.168.1.100: SSL connection but ‘/self.pem’ not found
192.168.1.100 - - [11/Aug/2018 00:22:53] 192.168.1.100: Plain non-SSL (ws://) WebSocket connection
192.168.1.100 - - [11/Aug/2018 00:22:53] 192.168.1.100: Version hybi-13, base64: ‘False’
192.168.1.100 - - [11/Aug/2018 00:22:53] 192.168.1.100: Path: ‘/?token=zh7ki79st09hfh5d2axy’
192.168.1.100 - - [11/Aug/2018 00:22:53] connecting to: node01:5902
handler exception: [Errno 111] Connection refused

Thanks.

Hi all,
I soon established to connect to the vnc, but terminal close itself suddenly with the following error. I am using Clox/LXD container system.
Could anyone help me or give any clue?
Thanks.

WebSocket server settings:

  • Listen on :29876
  • Flash security policy server
  • No SSL/TLS support (no cert file)
  • proxying from :29876 to targets in /var/lib/one/sunstone_vnc_tokens
    192.168.1.100 - - [17/Aug/2018 22:07:40] 192.168.1.100: Plain non-SSL (ws://) WebSocket connection
    192.168.1.100 - - [17/Aug/2018 22:07:40] 192.168.1.100: Version hybi-13, base64: ‘False’
    192.168.1.100 - - [17/Aug/2018 22:07:40] 192.168.1.100: Path: ‘/?token=bp4vkboavy3c0449uk3p’
    192.168.1.100 - - [17/Aug/2018 22:07:40] connecting to: node01:5902
    192.168.1.100 - - [17/Aug/2018 22:08:13] code 400, message Bad request syntax (’\x88\x8f(Y\x9d\x1c+\xb1\xc9}Z>\xf8h\x08:\xf1s[<\xf9’)

You have to refresh your browser, vnc isn’t perfect right now, somehow OpenNebula kills the vnc server on the node

Indeed, when I input something on the login prompt and hit the enter it passes the passwd prompt and replied with login incorrect message. Have you ever encountered problem like that?
Thanks for the reply.

Sometimes it happens, it is not perfect but it’s the only vnc solution we’ve found so far. There’s a lot of margin for improvement in that area