Thank you Sean and Nick for your answers. The instructions for HA will be very useful although I will never been close to the number of connections you are handling!
The version I used was the Docker image with release 1.5.5 As the segmentation faults were most of the time happening in ld-musl-x86_64.so.1, a colleague suspected an issue with Alpine as musl is used instead of glibc. Thus I built a Docker guacd image based on Debian 12. I based myself on the Dockerfile associated with the release 1.5.5 and edited the list of packages accordingly. Running the exact same load test with the same docker configuration, we could reach 80 concurrent sessions (then the VM used to launch the selenium instances could not handle the load anymore!) without any error message in the system logs of the server. Considering that element, are you still interested in the stack trace with 1.5.5 on Alpine? Or should I build a Docker guacd image based on Alpine and another one based on Debian 12 with release 1.6.0 to compare? Best regards, Paul From: Nick Couchman <vn...@apache.org> Sent: Tuesday, December 10, 2024 8:23 PM To: user@guacamole.apache.org Subject: Re: ***UNCHECKED*** RE: Maximum number of simultaneous RDP connections On Fri, Dec 6, 2024 at 2:06 PM HASENOHR Paul <paul.hasen...@ec.europa.eu.invalid<mailto:paul.hasen...@ec.europa.eu.invalid>> wrote: Dear Nick, As promised, I ran some further tests. With the help of a colleague, we could reproduce the issue on a test instance (max 59 concurrent RDP connections). Thanks, Paul - I'll try to take a look at some point before too long - the day job is keeping me rather busy these days :-/. You provided the core dumps, but those likely aren't going to be any good to me - if you can actually use gdb to analyze those dumps on the system where you built and ran guacd, and provide the full stack trace (bt or back trace), that'll help track down the issue you're seeing. Also, I looked back through the e-mails and don't see a specific mention of the version you're running - if you're running 1.5.4 or 1.5.5, and can try with 1.6.0 (you'll have to clone the git repo and build from source), that would be great. I don't know for sure that it will be fixed - I would hope that the issue you're seeing was actually fixed in 1.5.5 with GUACAMOLE-1920 (https://issues.apache.org/jira/browse/GUACAMOLE-1920<https://urldefense.com/v3/__https:/issues.apache.org/jira/browse/GUACAMOLE-1920__;!!DOxrgLBm!BXw4F3224dCJhNXtKkMgMVLrongrG2ohcrykFnTTry5S9FHRu_6D1CHU2_wa7iBX4EjtQgTClYbCcj1FBri-$>), but you aren't the only one reporting this behavior (https://issues.apache.org/jira/browse/GUACAMOLE-1998<https://urldefense.com/v3/__https:/issues.apache.org/jira/browse/GUACAMOLE-1998__;!!DOxrgLBm!BXw4F3224dCJhNXtKkMgMVLrongrG2ohcrykFnTTry5S9FHRu_6D1CHU2_wa7iBX4EjtQgTClYbCcnXDqo2u$>). -Nick
