Guacamole - unable to allocate a TLS value for currentThread #9717
Unanswered
jbufasttrack
asked this question in
Q&A
Replies: 1 comment 3 replies
-
@jbufasttrack could you do the following test with your setup:
|
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We're using Guacamole 1.5.4 which incorporates FreeRDP 2.11.4. When creating multiple connection attempts via RDP we can consistently get our setup into a state where FreeRDP throws the Major bug, unable to allocate a TLS value for currentThread error:
FreeRDP/winpr/libwinpr/thread/thread.c
Line 439 in 87557b1
The error occurs when we do exactly 59 connections. This results in a SSL_CTX_new failed error and after this every connection attempt throws the "unable to allocate a TLS value for currentThread" error.
The only way to get out of this state is to restart the server / docker image. This gives you another 59 connections before throwing the same error again.
We're currently looking at the code for both FreeRdp and Guacamole, but at the moment our prime suspect is that a change from Debian to Alpine for building dependencies in Guacamole might have changed some default limits / variables in FreeRDP.
Have any others experienced the same behavior or have any explanations as to what might be causing and environment to throw the above errors? And also how to prevent this?
We also have a thread open with the Guacamole team: https://www.mail-archive.com/[email protected]/msg12474.html as it's currently not entirely clear if this is a Guacamole or FreeRDP issue.
Any assistance will be hugely appreciated.
Beta Was this translation helpful? Give feedback.
All reactions