On 1/9/2021 4:40 AM, Mike Jumper wrote:
On Fri, Jan 8, 2021, 20:22 Jason Keltz <[email protected]
<mailto:[email protected]>> wrote:
Hi..
I was running guacamole 1.2.0, but took the opportunity this
evening to
put in 1.3.0 before a new term of courses begins on Monday. The web
interface works fine (I can login and select a host), but any host I
select, I get disconnected right away. guacd is dumping core...
extensions include: guacamole-auth-jdc-mysql-1.3.0.jar and
guacamole-auth-ldap-1.3.0.jar
OS: CentOS 7.8
I updated the guacamole.war in tomcat..
I restarted tomcat.
I ensured that the new guacamole-server was in place and restarted
and
that I'm using it.
I had to go back to guacamole 1.2.0. I don't know if I'll have a
chance
to try again soon, but here's the core dump when I connected to 2
hosts: https://www.eecs.yorku.ca/~jas/guaclog.txt
<https://www.eecs.yorku.ca/~jas/guaclog.txt>
You likely need to rebuild guacamole-server and make sure the version
of the FreeRDP libs installed is the same as the -devel headers.
CentOS updated their FreeRDP packages from 2.0.0-rc4 to 2.1.1. The way
that FreeRDP handles memory internally changed between those versions.
The older version freed things automatically, but the newer version
requires things to be freed manually. This can only be detected by
Guacamole at build-time.
If guacamole-server was built against the newer version of FreeRDP,
yet is somehow still getting linked to the older version at runtime,
that would cause a double-free.
Hi Mike,
Thanks. My system is running CentOS 7.8 so it wasn't affected by the
move to FreeRDP 2.1.1 (which happened in 7.9 I believe). In addition,
when I went back to 1.2.0, since I had overwritten guacd with my
guacamole-server-1.3.0 install, I had to recompile
guacamole-server-1.2.0, and it worked just as before. The problem has
to be something else.
Jason.
