vnc guacd segfault after upgrading from 0.9.10 to 0.9.12

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

vnc guacd segfault after upgrading from 0.9.10 to 0.9.12

Philip Herbert

Hello,

 

after upgrading from 0.9.10 to 0.9.12 I can no longer connect via vnc.

 

Apr 22 00:38:00 guacamole guacd[3189]: Creating new client for protocol "vnc"

Apr 22 00:38:00 guacamole guacd[3189]: Connection ID is "$1d54e86d-fd79-466e-b22f-425510b76060"

Apr 22 00:38:00 guacamole guacd[3682]: Cursor rendering: local

Apr 22 00:38:00 guacamole guacd[3682]: User "@28231e99-aed6-47c9-8d01-8437597cb0b6" joined connection "$1d54e86d-fd79-466e-b22f-425510b76060" (1 users now present)

Apr 22 00:38:00 guacamole kernel: [ 2137.939066] guacd[3689]: segfault at 57d00 ip 00007f5bfabd5472 sp 00007f5bfb7fdd68 error 4 in libvncclient.so.1.0.0[7f5bfabcb000+1e000]

Apr 22 00:38:00 guacamole guacd[3189]: Connection "$1d54e86d-fd79-466e-b22f-425510b76060" removed.

 

system is ubuntu LT 14.04, both guac versions (old and new) have been build from source.

 

Any Idea ?

 

Thanks, Philip

 

 

Reply | Threaded
Open this post in threaded view
|

Re: vnc guacd segfault after upgrading from 0.9.10 to 0.9.12

Mike Jumper
1) Can you confirm that you haven't installed Guacamole packages
provided by your distribution? Such packages would conflict with the
result of the build, resulting in guacd loading older,
binary-incompatible versions of its protocol support plugins.

2) What is the output of:

    ldd /usr/local/sbin/guacd | grep guac

and:

    ldd /usr/local/lib/libguac-client-vnc.so | grep guac

?

Thanks,

- Mike


On Fri, Apr 21, 2017 at 3:50 PM, Philip Herbert <[hidden email]> wrote:

> Hello,
>
>
>
> after upgrading from 0.9.10 to 0.9.12 I can no longer connect via vnc.
>
>
>
> Apr 22 00:38:00 guacamole guacd[3189]: Creating new client for protocol
> "vnc"
>
> Apr 22 00:38:00 guacamole guacd[3189]: Connection ID is
> "$1d54e86d-fd79-466e-b22f-425510b76060"
>
> Apr 22 00:38:00 guacamole guacd[3682]: Cursor rendering: local
>
> Apr 22 00:38:00 guacamole guacd[3682]: User
> "@28231e99-aed6-47c9-8d01-8437597cb0b6" joined connection
> "$1d54e86d-fd79-466e-b22f-425510b76060" (1 users now present)
>
> Apr 22 00:38:00 guacamole kernel: [ 2137.939066] guacd[3689]: segfault at
> 57d00 ip 00007f5bfabd5472 sp 00007f5bfb7fdd68 error 4 in
> libvncclient.so.1.0.0[7f5bfabcb000+1e000]
>
> Apr 22 00:38:00 guacamole guacd[3189]: Connection
> "$1d54e86d-fd79-466e-b22f-425510b76060" removed.
>
>
>
> system is ubuntu LT 14.04, both guac versions (old and new) have been build
> from source.
>
>
>
> Any Idea ?
>
>
>
> Thanks, Philip
>
>
>
>
Reply | Threaded
Open this post in threaded view
|

AW: vnc guacd segfault after upgrading from 0.9.10 to 0.9.12

Philip Herbert


Hello,

sorry for the delayed Information.


1) yes, guacamole packages have from the Distribution are not installed


(apt list --installed |grep gua  does not Show anything related)


2)


root@guacamole:/var/log# ldd /usr/local/sbin/guacd | grep guac        libguac.so.12 => /usr/local/lib/libguac.so.12 (0x00007f41922f7000)

root@guacamole:/var/log# ldd /usr/local/sbin/guacd | grep guac        libguac.so.12 => /usr/local/lib/libguac.so.12 (0x00007feb66a3f000)



Thanks, Philip



Von: Mike Jumper <[hidden email]>
Gesendet: Montag, 24. April 2017 04:52
An: [hidden email]
Betreff: Re: vnc guacd segfault after upgrading from 0.9.10 to 0.9.12
 
1) Can you confirm that you haven't installed Guacamole packages
provided by your distribution? Such packages would conflict with the
result of the build, resulting in guacd loading older,
binary-incompatible versions of its protocol support plugins.

2) What is the output of:

    ldd /usr/local/sbin/guacd | grep guac

and:

    ldd /usr/local/lib/libguac-client-vnc.so | grep guac

?

Thanks,

- Mike


On Fri, Apr 21, 2017 at 3:50 PM, Philip Herbert <[hidden email]> wrote:
> Hello,
>
>
>
> after upgrading from 0.9.10 to 0.9.12 I can no longer connect via vnc.
>
>
>
> Apr 22 00:38:00 guacamole guacd[3189]: Creating new client for protocol
> "vnc"
>
> Apr 22 00:38:00 guacamole guacd[3189]: Connection ID is
> "$1d54e86d-fd79-466e-b22f-425510b76060"
>
> Apr 22 00:38:00 guacamole guacd[3682]: Cursor rendering: local
>
> Apr 22 00:38:00 guacamole guacd[3682]: User
> "@28231e99-aed6-47c9-8d01-8437597cb0b6" joined connection
> "$1d54e86d-fd79-466e-b22f-425510b76060" (1 users now present)
>
> Apr 22 00:38:00 guacamole kernel: [ 2137.939066] guacd[3689]: segfault at
> 57d00 ip 00007f5bfabd5472 sp 00007f5bfb7fdd68 error 4 in
> libvncclient.so.1.0.0[7f5bfabcb000+1e000]
>
> Apr 22 00:38:00 guacamole guacd[3189]: Connection
> "$1d54e86d-fd79-466e-b22f-425510b76060" removed.
>
>
>
> system is ubuntu LT 14.04, both guac versions (old and new) have been build
> from source.
>
>
>
> Any Idea ?
>
>
>
> Thanks, Philip
>
>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: vnc guacd segfault after upgrading from 0.9.10 to 0.9.12

Herzog
This post was updated on .
In reply to this post by Philip Herbert
Same issue here. Any progress on resolving this?

My log has a tad more information:

May 29 04:18:58 infinity guacd[11089]: Creating new client for protocol "vnc"
May 29 04:18:58 infinity guacd[11089]: Connection ID is "$bf3e7254-4e6a-421c-9806-f6f8d97e2b47"
May 29 04:18:58 infinity guacd[11094]: Cursor rendering: local
May 29 04:18:58 infinity guacd[11094]: User "@ce80ba6a-6f10-4fbb-8edc-09bdf73b89d8" joined connection "$bf3e7254-4e6a-421c-9806-f6f8d97e2b47" (1 users now present)
May 29 04:18:58 infinity guacd[11094]: Listening for connections on port 43027
May 29 04:18:58 infinity guacd[11094]:  -listennofork: Listening on port 43027
May 29 04:18:58 infinity guacd[11094]:  -listennofork: Command line errors are not reported until a connection comes in.
May 29 04:18:58 infinity guacd[11094]: VNC server supports protocol version 3.8 (viewer 3.8)
May 29 04:18:58 infinity guacd[11094]: We have 2 security types to read
May 29 04:18:58 infinity guacd[11094]: 0) Received security type 17
May 29 04:18:58 infinity guacd[11094]: 1) Received security type 1
May 29 04:18:58 infinity guacd[11094]: Selecting security type 1 (1/2 in the list)
May 29 04:18:58 infinity guacd[11094]: Selected Security Scheme 1
May 29 04:18:58 infinity guacd[11094]: No authentication needed
May 29 04:18:58 infinity guacd[11094]: VNC authentication succeeded
May 29 04:18:58 infinity kernel: [112656.756224] guacd[11099]: segfault at 57d00 ip 00007fa2a68b33b0 sp 00007fa29d99bd68 error 4 in libvncclient.so.1.0.0[7fa2a68a9000+1e000]
May 29 04:18:58 infinity guacd[11089]: Connection "$bf3e7254-4e6a-421c-9806-f6f8d97e2b47" removed.
Reply | Threaded
Open this post in threaded view
|

Re: vnc guacd segfault after upgrading from 0.9.10 to 0.9.12

Mike Jumper
Please try a recent build from git. There is a recently-fixed issue which could result in these symptoms:


See also:


- Mike


On May 28, 2017 19:15, "Herzog" <[hidden email]> wrote:
Same issue here. Any progress on resolving this?



--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/vnc-guacd-segfault-after-upgrading-from-0-9-10-to-0-9-12-tp825p1015.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Reply | Threaded
Open this post in threaded view
|

Re: vnc guacd segfault after upgrading from 0.9.10 to 0.9.12

Herzog
Hi Mike,

thanks for the quick response! Just checked out master from git. Works splendidly :-)

Have a great week!

Kind Regards
Herzog
Reply | Threaded
Open this post in threaded view
|

Re: vnc guacd segfault after upgrading from 0.9.10 to 0.9.12

Herzog
We had another similar issue, but only when reverse connecting from a Windows Server 2016 (with the latest UltraVNC).

Is guacamole somehow handling VNC clients differently based on OS? Otherwise, it may just be a UltaVNC issue. Do you have a recommendation for VNC servers? If possible (e.g. on Windows clients), should we rather use RDP or that VNC recommendation?

Thanks a lot!
Reply | Threaded
Open this post in threaded view
|

Re: vnc guacd segfault after upgrading from 0.9.10 to 0.9.12

Mike Jumper
On Tue, May 30, 2017 at 1:05 AM, Herzog <[hidden email]> wrote:
We had another similar issue, but only when reverse connecting from a Windows
Server 2016 (with the latest UltraVNC).

Is guacamole somehow handling VNC clients differently based on OS?

Nope.

Otherwise, it may just be a UltaVNC issue. Do you have a recommendation for
VNC servers?

The manual has a summary of some VNC servers and their pros/cons:


If possible (e.g. on Windows clients), should we rather use RDP
or that VNC recommendation?


If connecting to Windows *servers*, RDP would be better, but a browser running on Windows is no different to Guacamole than a browser running on Linux (or Android ... or iOS ... or OSX ... etc.).

Further, the difference between the protocols exists only server-side. From the client's perspective, everything is just Guacamole protocol. The main difference between VNC and RDP in the case of the client is that RDP provides some performance features which VNC lacks, like bitmap caching, and Guacamole can leverage analogous features of its protocol to provide the same.

To the Guacamole server, all clients are the same. To the Guacamole client, all protocols are the same.

- Mike

Reply | Threaded
Open this post in threaded view
|

Re: vnc guacd segfault after upgrading from 0.9.10 to 0.9.12

Herzog
Hi Mike,

thanks for the hints!

RDP performs magnitudes better for us than VNC.

The Windows server crashing was indeed an issue caused by the VNC server we used. But as we switched to RDP, that's no issue any longer.