On 7/7/25 14:56, Jason Keltz wrote:
On 7/5/25 07:56, Nick Couchman wrote:
On Thu, Jul 3, 2025 at 12:52 PM Jason Keltz <[email protected]> wrote:
Hi.
Yesterday, I tried to update my Guacamole 1.5.5 install to 1.6.0
when there were no users logged in to my guacamole server.
This is on a RHEL 8.10 system where I do a self compile.
After updating the system, I restarted guacd. All of a sudden, I
noticed when trying to connect to any system (all also running
RHEL8.10), the GNOME would sort of "freeze" mid login.
I tried a few systems with the same behaviour. I had to quickly
revert the system to using 1.5.5 so couldn't debug.
Today, I setup a separate dev system for testing. I got 1.5.5
working, then did the same steps I did yesterday when upgrading
the production server with 1.6.0.
This time, oddly enough, it seems to be working which is very
puzzling. The server is auto installed so the dev server is
setup the same was as the production one.
However, the problem I saw yesterday does not exist. I don't
understand how that's possible.
I was hoping to replicate the problem to give me an opportunity
to debug.
This does sound very strange, and I'd also be very interested to
figure out what's going on. If you have a chance to restart your
production guacd instance with debug logging turned on ("-L debug"
flag) and reproduce the issues, I'd be interested to see if anything
shows up in the logs.
Here's an even more strange issue -- I rebooted the hardware, and
started again with Guac 1.6.0 in production, and this time, that
problem did not occur. I connected to many hosts without any hanging
interface. I still don't see how that's possible.
However, the problem gets more strange. We have various servers where
I've set say, 50 user max limit with 1 user connection allowed per
user. When I was switched over to 1.6.0 in production, I opened up a
connection to one server, and it worked fine. Through the
ctrl-alt-shift menu, I switched back to home and opened up another
connection. That worked fine. I tried to switch back to the first
one, and got the error that I've exceeded the maximum number of
connections allowed. I checked that I was only logged in once. I
tried to go to the other host, and the same thing happened! I waited
a minute or two and I was able to connect again to my existing session
with no error. I tried with a separate non-admin account as well,
and same problem. I then had to switch production back to 1.5.5 again
in my second failed upgrade attempt.
I've been on my development server guac 1.6.0 testbed all morning, and
I have switched back and forth between various connections multiple
times, and it's all working just fine the way it is supposed to.
Literally the only difference between the two is that the development
server isn't as powerful as the production server. Production server
is a 32 core AMD EPYC with 384 GB memory, where-as the dev one has 8
cores and 8G memory. It's easy enough to switch production back to
1.6.0 again to try it again when things are quiet, but I don't think
I'll be as lucky this time.
I had a chance to set production back to 1.6.0 this morning, and
replicated the issue.
I took a guacd debug log, but I'm not really sure that it shows
anything. I connected to one host, and then went back to home, and
tried to connect back, and got the error. I did the same thing with
another host, and the same behaviour was present. Again, on my devel
platform there's no problem doing that.
I put the debug here: https://www.eecs.yorku.ca/~jas/guac-1.6.0-debug.txt
However, on another note, on 1.6.0, when I am moving windows
around, they are leaving remnants on the background. Login to
the same system with 1.5.5 does not do this.
See the 1.6.0 image here after moving a terminal window around:
This is likely related to the re-working of the graphics code,
although I thought we had squashed all of those bugs prior to the
full 1.6.0 release. Can you confirm you're running the actual 1.6.0
(after 1.6.0-RC3) and not a slightly earlier 1.6.0 release candidate
(-RC1 or -RC2)? Otherwise we'll likely need to open and track a bug
for this.
Running the actual 1.6.0. Set your background to black and see if you
see the problem.
Jason.
Jason.
