[
https://issues.apache.org/jira/browse/GUACAMOLE-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017683#comment-18017683
]
Niko edited comment on GUACAMOLE-2118 at 9/2/25 1:47 PM:
---------------------------------------------------------
[~vnick]
*[^guacamole-logs.txt]*
Yesterday we had a {{guacd}} process (PID {*}666817{*}) that remained running
until today, consuming ~100% CPU the entire time.
{quote}666817 root 20 0 4455924 85624 25108 S 99,7 0,5 21,09
guacd
{quote}
According to the database and journalctl logs:
* Connection started: *2025-09-01 09:59:46* (local time)
* Connection ended (per DB / logs): *2025-09-01 11:05:19 UTC*
* However, the {{guacd}} process never exited and continued running until we
noticed it today.
We have also seen stale {{guacd}} processes from as far back as July 2025,
sometimes persisting for weeks or months, but unfortunately we no longer have
logs from those.
The attached log excerpts cover the connection from yesterday, showing the RDP
session closing normally (“RDP server closed/refused connection: Manually
logged off”), while the corresponding {{guacd}} PID remained active afterwards.
We currently mitigate this by running a cron job that reports and kills such
stale processes.
Happy to provide more detailed debug logs if needed.
was (Author: JIRAUSER284621):
[~vnick]
Yesterday we had a {{guacd}} process (PID {*}666817{*}) that remained running
until today, consuming ~100% CPU the entire time.
{quote}666817 root 20 0 4455924 85624 25108 S 99,7 0,5 21,09
guacd
{quote}
According to the database and journalctl logs:
* Connection started: *2025-09-01 09:59:46* (local time)
* Connection ended (per DB / logs): *2025-09-01 11:05:19
UTC[^guacamole-logs.txt]*
* However, the {{guacd}} process never exited and continued running until we
noticed it today.
We have also seen stale {{guacd}} processes from as far back as July 2025,
sometimes persisting for weeks or months, but unfortunately we no longer have
logs from those.
The attached log excerpts cover the connection from yesterday, showing the RDP
session closing normally (“RDP server closed/refused connection: Manually
logged off”), while the corresponding {{guacd}} PID remained active afterwards.
We currently mitigate this by running a cron job that reports and kills such
stale processes.
Happy to provide more detailed debug logs if needed.
> 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: guacamole-logs.txt
>
>
> 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)
