Bugzilla – Bug 7016
failure to connect to the agent is listed as failing to connect to VNC
Last modified: 2017-08-22 10:15:24
You need to
before you can comment on or make changes to this bug.
This is of course confusing for everyone involved.
The error message in question is:
"Couldn't set up secure tunnel to VNC!"
I can't figure out in which scenario this error message would occur. It's
apparently not related to VNC, but it's not related to a disabled SSH server on
the agent, or the ability to execute thinlinc-login or Xvnc on the server.
(In reply to comment #2)
> I can't figure out in which scenario this error message would occur. It's
> apparently not related to VNC, but it's not related to a disabled SSH server on
> the agent, or the ability to execute thinlinc-login or Xvnc on the server.
It's a generic "catch-all" error message when trying to establish the tunnel to
the agent. The earlier error message mentioned "VNC" since the SSH tunnel is
for (among other things) creating a tunnel to the VNC server. A long time ago,
there were no tunnels except for VNC.
The error message is used for cases such as:
* Local ports already in use
* SSH binary suddenly disappearing
* Unable to create pipes, or fork
* SSH process dying unexpectedly
An easy way or reproduce is:
1) Set agent_hostname=18.104.22.168
2) Connect. The client will "hang".
3) Kill the SSH process
Verified build 5541, looks good.