On 8/7/25 11:17, Nick Couchman wrote:
On Thu, Aug 7, 2025 at 10:53 AM Jason Keltz <[email protected]> wrote:
Hi.
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 there 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 may have to re-install 1.6.0 on the production system to get the
debugging information that I need, but I'd really rather not do
that it
if not necessary since it causes user inconvenience, and a lot of
emails. Guacamole is an important part of our educational
environment.
Sorry that I missed your question originally. I don't think that
you'll have to re-install to get the debug info - just need to put
both guacd and the client into debug mode:
https://guacamole.apache.org/doc/gug/configuring-guacamole.html#logging-within-the-web-application
https://guacamole.apache.org/doc/gug/configuring-guacamole.html#command-line-options
https://guacamole.apache.org/doc/gug/configuring-guacamole.html#daemon-section
Once you have that done, look at your Tomcat logs and your guacd logs
(syslog - journalctl on RHEL8) and see if you're seeing any messages
that point to the problem. You can also look at "dmesg" output and see
if there are any indications of segfaults in the guacd process - it
almost sounds like you're hitting some sort of segfault, there,
causing guacd to drop and the client to stop responding. But that's
just my speculation at the moment.
-Nick
Hi Nick
On the production server, I'm running 1.5.5 at the moment so I would
have to arrange to re-install guacamole 1.6.0 there.
On the devel server I'm running 1.6.0 and will run for a few days first
to see if I can re-create the problem with the debug lines so that I
could get details without inconveniencing the users and generating panic
and many support emails :)
In guacd.conf, I have added in the [daemon] section log_level = debug
In logback.xml I have the DEBUG section...
Jas.
