Hi Nick, I changed the SSL Inspection profile on the Firewall to disregard Guacamole. In doing so it does feel a bit more stable but unfortunately received another one after the change, which means on to the segfaults I go.
Im struggling though to get my Core Dump files to even show up. I will do some more digging on getting those working, and then will forward the results. Thanks, Corey From: Nick Couchman <vn...@apache.org> Sent: Tuesday, May 28, 2024 9:30 AM To: user@guacamole.apache.org Subject: Re: Help with seemingly random RDP disconnects On Tue, May 28, 2024 at 9:17 AM Corey Faehrmann <cfaehrm...@gchi.com.invalid<mailto:cfaehrm...@gchi.com.invalid>> wrote: Looks like a segfault did occur according to dmesg. This is the output: [ 386.612493] guacd[4711]: segfault at 7fadd03c45f0 ip 00007fadd03c45f0 sp 00007fadc06dcc68 error 14 likely on CPU 1 (core 0, socket 0) [ 386.612510] Code: Unable to access opcode bytes at 0x7fadd03c45c6. If you can track down the core dump file and get a stack trace, that would be helpful in figuring out what's going on. The Gucamole server does infact have a Firewall performing SSL inspection on the traffic. This could be the culprit, since you mention it I suppose you have had issues with this in the past? Maybe - it depends on if that firewall is messing with the traffic at all - sometimes "inspection" also means that it's doing things like trying to shut down streams that it thinks aren't used. I think we've seen this in the past specifically with the Websocket traffic - sometimes L7/Application Aware firewalls try to optimize and manage things in a way that isn't terribly friendly to Guacamole. You can try excluding the Guacamole traffic from the inspection/optimization/etc. and see if that helps. It's also possible that it is not related at all, and that you'll still need to track down the cause of that Segfault... -Nick ________________________________ AVISO DE CONFIDENCIALIDAD: El contenido de este correo, asi como sus archivos adjuntos estan protegidos por el secreto profesional, son confidenciales y son para el uso exclusivo del (de los) destinatario(s) deseado(s). Si usted no es el destinatario deseado del presente correo y sus archivos adjuntos o si este mensaje le ha sido enviado por error, por favor notifiquelo de inmediato al remitente mediante un correo de respuesta y despues elimine este correo y cualquier archivo adjunto. Si usted no es el destinatario deseado, por medio del presente se le notifica que queda estrictamente prohibido cualquier uso, difusion, copia o almacenamiento de este correo y/o sus archivos adjuntos. Para informacion acerca del tratamiento y derechos relativos a datos personales, usted puede consultar el Aviso de Privacidad publicado en nuestra pagina de Internet. ________________________________ CONFIDENTIALITY NOTICE: The contents of this email and any attachments is privileged, confidential and solely for the use of the intended addressee(s). If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or storage of this message and/or its attachments is strictly prohibited. For information of the treatment and rights related to personal data, you can consult the Privacy Policy published in our website. ________________________________
