[
https://issues.apache.org/jira/browse/GUACAMOLE-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18052428#comment-18052428
]
Levin Anliker commented on GUACAMOLE-2118:
------------------------------------------
We are using Guacamole only on MS Edge with Login over EntraID (SAML) to
connect to approx. 100 Windows vm's (RDP only). It's a native installation on
Ubuntu Server. In Version 1.5.5. we had no problems with the connections at
all. After upgrading to 1.6.0 we encountered the same type of issues and could
not really recreate a pattern on when the issues shows up. I did a short
testing with other browsers and did not have the issue.
For us the following tweak helped solving the issue:
* Download and extract guacamole-server-1.6.0.tar.gz
* Open up src/guacd/proc.h
* Change the value of GUAC_TIMEOUT from 15000 to 65000 -> # Define
GUAC_TIMEOUT 65000
* Recompile an install guacamole-server
Maybe you can give it a try and test if it works for you.
> unable to upgrade 1.5.5 to 1.6.0 due to sporadic hanging issue
> --------------------------------------------------------------
>
> Key: GUACAMOLE-2118
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-2118
> Project: Guacamole
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Jason Keltz
> Priority: Major
> Attachments: backtrace threads, backtrace.log, guacamole-logs.txt,
> guacd-178388-gdb.txt, guacd-178388-lsof.txt, guacd-240326-gdb.txt,
> guacd-240326-lsof.txt, image-2025-09-08-15-11-59-435.png
>
>
> I've been running Guacamole since around 2020, upgrading reasonably quickly
> each and every time there's been an update. I update my Tomcat to the latest
> 9.X release from time to time (currently 9.0.102) , and my JDK to the latest
> 8.X release from time to time (currently jdk8u452-b09).
> Recently, after attempting an upgrade from Guacamole 1.5.5 to 1.6.0, I ran
> into a problem. Initially, everything seemed to work just fine. I can
> connect to any of the systems I have available. However, at some point
> later, I notice in the tomcat logs a lot of "connects" and "disconnects" to
> hosts. Users start complaining that "Guacamole isn't working". What I
> noticed at this point was that when they would try to return to a connection,
> it would connect, and their existing connecting would start to redraw, but
> it would hang in the middle. If I restart guacd at this point, it starts to
> work again, but the problem comes back. Some users would see it. Other users
> were fine.
> I feel like there's a bug hiding, and it may require a lot of user activity
> to get to it. I ended up creating a devel system for testing, and I'm
> running guac 1.6.0 there, and I've enabled full debugging, but I can't seem
> to make it happen here yet. Is there any easy way I can force a bunch of
> connections? The devel system is running labtest Rocky 8.10 (RHEL8.10) with
> latest kernel and patches and this matches the production system. They are
> both installed with the same kickstart configuration.
> I'm opening this "bug" even though I don't have concrete information yet. If
> I really have to do it, I may have to re-install on the production system to
> get the debugging information that I need, but I'd rather not do it if not
> necessary since it causes user inconvenience, and Guacamole is an important
> part of our educational environment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
