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/19 18:04:00 UTC
[jira] [Closed] (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:all-tabpanel ]
Nick Couchman closed GUACAMOLE-1016.
------------------------------------
Resolution: Invalid
Closing this out because I believe this is an environmental issue imposed by systemd limits and not something wrong with guacd.
> 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.
>
> EDIT:
> we just receive this message (dmesg) minute ago
> Apr 8 08:26:17 server.domain kernel: [602080.063555] cgroup: fork rejected by pids controller in /system.slice/guacd.service
> Just found...
> A process limit set by systemd has been hit and new processes cannot be forked.
> Users cannot connect anymore, those that are connecte can still work RDP. We are looking how to increase the "process limit" value.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)