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 2022/01/05 19:14:00 UTC
[jira] [Commented] (GUACAMOLE-1489) segfault in ld-musl-x86_64.so.1
[ https://issues.apache.org/jira/browse/GUACAMOLE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469496#comment-17469496 ]
Nick Couchman commented on GUACAMOLE-1489:
------------------------------------------
First, I think it unlikely that this has anything to do with guacd, as the segfault mentions ld-musl-x86_64.so.1, which appears to be an alternative libc implementation. I suspect the issue is in that library instead of guacd, though I could be wrong.
In any case, we'll need more information in order to debug:
* Platform, including Linux distro/version
* Full stack dump of the segfault, or the coredump file, if you're comfortable sharing that
*
> segfault in ld-musl-x86_64.so.1
> -------------------------------
>
> Key: GUACAMOLE-1489
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1489
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
> Affects Versions: 1.3.0
> Reporter: Fabian Dellwing
> Priority: Minor
> Attachments: Dockerfile
>
>
> We monitor segfaults on our production systems running guacd in a docker container.
>
> The dumped code is always the same:
> {code:java}
> Jan 4 14:40:57 mbCONNECT24-20eu kernel: [7287279.905091] guacd[615093]: segfault at 7f387a5169fd ip 00007f38838fe812 sp 00007f387b1b12a8 error 4 in ld-musl-x86_64.so.1[7f38838f0000+48000]
> Jan 4 14:40:57 mbCONNECT24-20eu kernel: [7287279.905099] Code: 74 16 48 89 46 08 48 8b 00 48 89 06 48 89 70 08 48 8b 46 08 48 89 30 c3 48 89 76 08 48 89 36 48 89 37 c3 40 f6 c7 0f 74 01 f4
> <44> 8a 47 fd 0f b7 57 fe 44 89 c1 41 83 e0 1f 83 e1 1f 80 7f fc 00
> Jan 4 14:42:01 mbCONNECT24-20eu kernel: [7287343.789327] guacd[670686]: segfault at 7f387a9909cd ip 00007f38838fe812 sp 00007f387c1612a8 error 4 in ld-musl-x86_64.so.1[7f38838f0000+48000]
> Jan 4 14:42:01 mbCONNECT24-20eu kernel: [7287343.789334] Code: 74 16 48 89 46 08 48 8b 00 48 89 06 48 89 70 08 48 8b 46 08 48 89 30 c3 48 89 76 08 48 89 36 48 89 37 c3 40 f6 c7 0f 74 01 f4
> <44> 8a 47 fd 0f b7 57 fe 44 89 c1 41 83 e0 1f 83 e1 1f 80 7f fc 00
> Jan 4 14:47:18 mbCONNECT24-20eu kernel: [7287660.843128] guacd[949168]: segfault at 7f388008942d ip 00007f38838fe812 sp 00007f3880b062a8 error 4 in ld-musl-x86_64.so.1[7f38838f0000+48000]
> Jan 4 14:47:18 mbCONNECT24-20eu kernel: [7287660.843133] Code: 74 16 48 89 46 08 48 8b 00 48 89 06 48 89 70 08 48 8b 46 08 48 89 30 c3 48 89 76 08 48 89 36 48 89 37 c3 40 f6 c7 0f 74 01 f4
> <44> 8a 47 fd 0f b7 57 fe 44 89 c1 41 83 e0 1f 83 e1 1f 80 7f fc 00
> Jan 4 14:47:18 mbCONNECT24-20eu kernel: [7287661.348174] guacd[949330]: segfault at 7f3878c54a6d ip 00007f38838fe812 sp 00007f387b1312a8 error 4 in ld-musl-x86_64.so.1[7f38838f0000+48000]
> Jan 4 14:47:18 mbCONNECT24-20eu kernel: [7287661.348180] Code: 74 16 48 89 46 08 48 8b 00 48 89 06 48 89 70 08 48 8b 46 08 48 89 30 c3 48 89 76 08 48 89 36 48 89 37 c3 40 f6 c7 0f 74 01 f4
> <44> 8a 47 fd 0f b7 57 fe 44 89 c1 41 83 e0 1f 83 e1 1f 80 7f fc 00
> Jan 4 14:49:13 mbCONNECT24-20eu kernel: [7287776.210961] guacd[1045174]: segfault at 7f38784f767d ip 00007f38838fe812 sp 00007f387c56d2a8 error 4 in ld-musl-x86_64.so.1[7f38838f0000+48000]
> Jan 4 14:49:13 mbCONNECT24-20eu kernel: [7287776.210968] Code: 74 16 48 89 46 08 48 8b 00 48 89 06 48 89 70 08 48 8b 46 08 48 89 30 c3 48 89 76 08 48 89 36 48 89 37 c3 40 f6 c7 0f 74 01 f4
> <44> 8a 47 fd 0f b7 57 fe 44 89 c1 41 83 e0 1f 83 e1 1f 80 7f fc 00
> Jan 4 14:56:56 mbCONNECT24-20eu kernel: [7288238.825172] guacd[1472562]: segfault at 7f38788eba7d ip 00007f38838fe812 sp 00007f387b7432a8 error 4 in ld-musl-x86_64.so.1[7f38838f0000+48000]
> Jan 4 14:56:56 mbCONNECT24-20eu kernel: [7288238.825179] Code: 74 16 48 89 46 08 48 8b 00 48 89 06 48 89 70 08 48 8b 46 08 48 89 30 c3 48 89 76 08 48 89 36 48 89 37 c3 40 f6 c7 0f 74 01 f4
> <44> 8a 47 fd 0f b7 57 fe 44 89 c1 41 83 e0 1f 83 e1 1f 80 7f fc 00{code}
> Docker:
> {code:java}
> Client:
> Version: 18.03.1-ce
> API version: 1.37
> Go version: go1.9.5
> Git commit: 9ee9f40
> Built: Thu Apr 26 07:17:13 2018
> OS/Arch: linux/amd64
> Experimental: false
> Orchestrator: swarm
> Server:
> Engine:
> Version: 18.03.1-ce
> API version: 1.37 (minimum version 1.12)
> Go version: go1.9.5
> Git commit: 9ee9f40
> Built: Thu Apr 26 07:15:27 2018
> OS/Arch: linux/amd64
> Experimental: false{code}
> Linux Kernel version is 5.4.
> Dockerfile provided as attachment.
>
> So far we were not able to reproduce the error on our dev server. More logging on production servers ist sadly not possible.
>
> As far as we can tell, they guacd service is usable perfectly fine. Segfault might be happening at the end of a connection.
>
> If you need more information, feel free to ask. Will do my best to provide it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)