On Tue, May 28, 2024 at 9:17 AM Corey Faehrmann <[email protected]> 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 >
