You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by David Brodbeck <br...@math.ucsb.edu> on 2021/03/12 19:43:37 UTC

Support for protocol "vnc" is not installed

I've seen a few other threads about this, but none had a solution. I've
built guacamole from source, apparently successfully, but when I try to
connect to a VNC server it times out, and I get "Support for protocol "vnc"
is not installed" in the syslog.

My configure command line was ./configure
--with-systemd-dir=/lib/systemd/system --prefix=/opt/guacamole

The configure output contained the following:

   Protocol support:

      Kubernetes .... no
      RDP ........... yes
      SSH ........... yes
      Telnet ........ no
      VNC ........... yes


I've verified that I have guacamole-client-vnc.so.0 in /opt/guacamole/lib.

Connection attempts result in this:

Mar 12 11:25:17 vector guacd[26705]: Creating new client for protocol "vnc"
Mar 12 11:25:17 vector guacd[26705]: guacd[26705]: INFO:#011Creating new
client for protocol "vnc"
Mar 12 11:25:17 vector guacd[26705]: guacd[26705]: INFO:#011Connection ID
is "$b828bd93-a812-45ce-b6a1-6bf1109af04a"
Mar 12 11:25:17 vector guacd[26705]: Connection ID is
"$b828bd93-a812-45ce-b6a1-6bf1109af04a"
Mar 12 11:25:17 vector guacd[26705]: guacd[26736]: WARNING:#011Support for
protocol "vnc" is not installed
Mar 12 11:25:17 vector guacd[26736]: Support for protocol "vnc" is not
installed
Mar 12 11:25:17 vector guacd[26705]: Connection
"$b828bd93-a812-45ce-b6a1-6bf1109af04a" removed.
Mar 12 11:25:17 vector guacd[26705]: guacd[26705]: INFO:#011Connection
"$b828bd93-a812-45ce-b6a1-6bf1109af04a" removed.
Mar 12 11:25:32 vector tomcat9[26455]: 11:25:32.598 [http-nio-8080-exec-2]
ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation of WebSocket
tunnel to guacd failed: Connection to guacd timed out.


I'm a bit stumped by this one, especially since I've done a similar build
once before on another system and had it work. Do I need to configure
something to tell guacd where to find its libraries?

-- 
David Brodbeck (they/them)
System Administrator, Department of Mathematics
University of California, Santa Barbara

Re: Support for protocol "vnc" is not installed

Posted by Nick Couchman <vn...@apache.org>.
On Fri, Mar 12, 2021 at 2:56 PM David Brodbeck <br...@math.ucsb.edu>
wrote:

>
>
> On Fri, Mar 12, 2021 at 11:50 AM Mike Jumper <mi...@glyptodon.com>
> wrote:
>
>> You would need to tell the *system-wide linker* where to find these
>> libraries. When support for a protocol is loaded, guacd does this by
>> requesting that the system-wide linker load the library
>> "libguac-client-PROTOCOLNAME.so". If those libraries are installed to a
>> non-standard location that will not be searched by the linker, this will
>> fail.
>>
>> You need to add this new "/opt/guacamole/lib" path to the set of paths
>> searched by the system-wide linker. This is normally set within
>> "/etc/ld.so.conf.d" or "/etc/ld.so.conf". Alternatively, you could manually
>> set the LD_LIBRARY_PATH environment variable when starting guacd.
>>
>
> Hmm, OK. I saw that configure ran "ldconfig -n /opt/guacamole/lib" and
> figured that would take care of it, but apparently not.
>
> I realized my other installation was in /usr/local, so I changed the
> prefix to that and reinstalled. It works now. I was trying to be too cute
> putting it in /opt, I think. (I like to separate locally compiled stuff
> from packaged stuff, hence /opt.)
>
>
I routinely install into /opt/guac, and the only time I've run into issues
was when there was a much older install of Guacamole already in that
directory, and some competing libraries. In those cases I ended up just
blowing away the entire /opt/guacd directory, since it doesn't have
anything but binaries in my case, and re-doing the "make install", then
restart gaucd. That seemed to correct issues I've seen.

-Nick

Re: Support for protocol "vnc" is not installed

Posted by David Brodbeck <br...@math.ucsb.edu>.
On Fri, Mar 12, 2021 at 11:50 AM Mike Jumper <mi...@glyptodon.com>
wrote:

> You would need to tell the *system-wide linker* where to find these
> libraries. When support for a protocol is loaded, guacd does this by
> requesting that the system-wide linker load the library
> "libguac-client-PROTOCOLNAME.so". If those libraries are installed to a
> non-standard location that will not be searched by the linker, this will
> fail.
>
> You need to add this new "/opt/guacamole/lib" path to the set of paths
> searched by the system-wide linker. This is normally set within
> "/etc/ld.so.conf.d" or "/etc/ld.so.conf". Alternatively, you could manually
> set the LD_LIBRARY_PATH environment variable when starting guacd.
>

Hmm, OK. I saw that configure ran "ldconfig -n /opt/guacamole/lib" and
figured that would take care of it, but apparently not.

I realized my other installation was in /usr/local, so I changed the prefix
to that and reinstalled. It works now. I was trying to be too cute putting
it in /opt, I think. (I like to separate locally compiled stuff from
packaged stuff, hence /opt.)

-- 
David Brodbeck (they/them)
System Administrator, Department of Mathematics
University of California, Santa Barbara

Re: Support for protocol "vnc" is not installed

Posted by Mike Jumper <mi...@glyptodon.com>.
On Fri, Mar 12, 2021 at 11:44 AM David Brodbeck <br...@math.ucsb.edu>
wrote:

> I've seen a few other threads about this, but none had a solution. I've
> built guacamole from source, apparently successfully, but when I try to
> connect to a VNC server it times out, and I get "Support for protocol "vnc"
> is not installed" in the syslog.
>
> My configure command line was ./configure
> --with-systemd-dir=/lib/systemd/system --prefix=/opt/guacamole
>
> The configure output contained the following:
>
>    Protocol support:
>
>       Kubernetes .... no
>       RDP ........... yes
>       SSH ........... yes
>       Telnet ........ no
>       VNC ........... yes
>
>
> I've verified that I have guacamole-client-vnc.so.0 in /opt/guacamole/lib.
>
> Connection attempts result in this:
>
> Mar 12 11:25:17 vector guacd[26705]: Creating new client for protocol "vnc"
> Mar 12 11:25:17 vector guacd[26705]: guacd[26705]: INFO:#011Creating new
> client for protocol "vnc"
> Mar 12 11:25:17 vector guacd[26705]: guacd[26705]: INFO:#011Connection ID
> is "$b828bd93-a812-45ce-b6a1-6bf1109af04a"
> Mar 12 11:25:17 vector guacd[26705]: Connection ID is
> "$b828bd93-a812-45ce-b6a1-6bf1109af04a"
> Mar 12 11:25:17 vector guacd[26705]: guacd[26736]: WARNING:#011Support for
> protocol "vnc" is not installed
> Mar 12 11:25:17 vector guacd[26736]: Support for protocol "vnc" is not
> installed
> Mar 12 11:25:17 vector guacd[26705]: Connection
> "$b828bd93-a812-45ce-b6a1-6bf1109af04a" removed.
> Mar 12 11:25:17 vector guacd[26705]: guacd[26705]: INFO:#011Connection
> "$b828bd93-a812-45ce-b6a1-6bf1109af04a" removed.
> Mar 12 11:25:32 vector tomcat9[26455]: 11:25:32.598 [http-nio-8080-exec-2]
> ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation of WebSocket
> tunnel to guacd failed: Connection to guacd timed out.
>
>
> I'm a bit stumped by this one, especially since I've done a similar build
> once before on another system and had it work. Do I need to configure
> something to tell guacd where to find its libraries?
>

You would need to tell the *system-wide linker* where to find these
libraries. When support for a protocol is loaded, guacd does this by
requesting that the system-wide linker load the library
"libguac-client-PROTOCOLNAME.so". If those libraries are installed to a
non-standard location that will not be searched by the linker, this will
fail.

You need to add this new "/opt/guacamole/lib" path to the set of paths
searched by the system-wide linker. This is normally set within
"/etc/ld.so.conf.d" or "/etc/ld.so.conf". Alternatively, you could manually
set the LD_LIBRARY_PATH environment variable when starting guacd.

Michael Jumper
CEO, Lead Developer
Glyptodon Inc <https://enterprise.glyptodon.com/>.