Without specifics, how much memory, cpu, and net bandwidth it is
impossible to determine what is sufficient. The fact that starting a second
server allows you to double does suggest a software limitation.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Sun, 27 Jul 2025, geek 2gether wrote:
Date: Sun, 27 Jul 2025 23:03:28 -0400
From: geek 2gether <[email protected]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: SSH Connection Limit of 60 per guacd
Thank you for sharing. Do you mind providing the specs of your server? Is
the guacd running separately from guacamole client ? If so what’s the
specs? Ram and CPU? What’s the network speed between guacd and the client?
On Sun, Jul 27, 2025 at 11:00 PM Alex_Yin <[email protected]> wrote:
Hello, I am doing stress testing on my own guacamole and found that one
guacd can only connect to 60 ssh connections. When it exceeds 60, it will
display "SSH handshake failed” (port 81 is the mapping of port 22). When I
use 2 guacds to connect (using elb for load balancing), the upper limit is
120.
My guacd is deployed on a centos 7.9 server. I see that the establishment
of ssh uses the “libssh2_session_handshake" function, but the number of fds
on the server should be sufficient. I want to know what causes this 60
limit.
Alex_Yin
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
