You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Nick Couchman (Jira)" <ji...@apache.org> on 2020/04/08 12:28:00 UTC

[jira] [Commented] (GUACAMOLE-1016) guacd[5450]: segfault at... error 4 in libguac-client-rdp.so

    [ https://issues.apache.org/jira/browse/GUACAMOLE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078230#comment-17078230 ] 

Nick Couchman commented on GUACAMOLE-1016:
------------------------------------------

[~Chamberland]: Can you please provide more detail on this - under what conditions you see the segfault?

You can bump up the logging level for guacd by running it with the "-L debug" flag.  Log messages are, by default, logged to your normal syslog environment - so, /var/log/messages or journalctl on most systems.  If you're running in docker they'll  For a segfault I would also suggest running gdb with guacd so that you can get the stack trace.  You'd do something like:

gdb /path/to/guacd -L debug -f
set follow-fork-mode child
go

And then when it segfaults you should get the full stack trace.

> guacd[5450]: segfault at... error 4 in libguac-client-rdp.so
> ------------------------------------------------------------
>
>                 Key: GUACAMOLE-1016
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1016
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacd
>    Affects Versions: 1.1.0
>            Reporter: Martin
>            Priority: Minor
>
> SERVER.domain kernel: [556999.879168] guacd[5450]: segfault at 7fcce933801c ip 00007fcd8aabb7db sp 00007fcd24ff8ce0 error 4 in libguac-client-rdp.so.0.0.0[7fcd8aaaf000+17000]
>  
> Can we look for other logs (more details) somewhere ?
> EDIT:
> Apache error_log:
> [mpm_event:error] [pid 762:tid 139741530629248] AH00484: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting
>  
> There is 200 concurents users connected.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)