Hello,
I can confirm Weston's observations. I could reproduce it by connecting 59 times to to an RDP desktop with SSH enabled. On the 60th attempt it did not work anymore (I might have got the count wrong by 1, so it could have very well also been after the 58th attempt).
On the failing attempts there is the following in docker host's dmesg:
[Fri Jan 12 08:54:09 2024] guacd[2454882]: segfault at 8 ip 7fe9c9b5a7a2 sp 7fe9c6c4b0b8 error 4 in ld-musl-x86_64.so.1[7fe9c9b18000+4c000]
[Fri Jan 12 08:54:09 2024] Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1
[Fri Jan 12 08:54:40 2024] guacd[2455844]: segfault at 8 ip 7fe9c9b5a7a2 sp 7fe9c6c4b0b8 error 4 in ld-musl-x86_64.so.1[7fe9c9b18000+4c000]
[Fri Jan 12 08:54:40 2024] Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1
[Fri Jan 12 08:55:10 2024] guacd[2456174]: segfault at 8 ip 7fe9c9b5a7a2 sp 7fe9c6c620b8 error 4 in ld-musl-x86_64.so.1[7fe9c9b18000+4c000]
[Fri Jan 12 08:55:10 2024] Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1
[Fri Jan 12 08:55:40 2024] guacd[2456750]: segfault at 8 ip 7fe9c9b5a7a2 sp 7fe9c6c620b8 error 4 in ld-musl-x86_64.so.1[7fe9c9b18000+4c000]
[Fri Jan 12 08:55:40 2024] Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1
[Fri Jan 12 08:56:42 2024] guacd[2457875]: segfault at 8 ip 7fe9c9b5a7a2 sp 7fe9c6c620b8 error 4 in ld-musl-x86_64.so.1[7fe9c9b18000+4c000]
[Fri Jan 12 08:56:42 2024] Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1
[Fri Jan 12 08:58:39 2024] guacd[2460389]: segfault at 8 ip 7fe9c9b5a7a2 sp 7fe9c6c620b8 error 4 in ld-musl-x86_64.so.1[7fe9c9b18000+4c000]
[Fri Jan 12 08:58:39 2024] Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b
guacd's docker logs on a failing connection:
guacd[1]: INFO: Creating new client for protocol "rdp"
guacd[1]: INFO: Connection ID is "$d39d01e0-5101-4d79-bd8d-a8620c389efa"
guacd[1800]: WARNING: FreeRDP initialization may fail: Writability of the current user's home directory ("/home/guacd") could not be determined: Read-only file system
guacd[1800]: INFO: No security mode specified. Defaulting to security mode negotiation with server.
guacd[1800]: INFO: Resize method: display-update
guacd[1800]: INFO: No clipboard line-ending normalization specified. Defaulting to preserving the format of all line endings.
guacd[1800]: INFO: User "@ad5b9532-c914-4fc0-be0f-3e7a247157c7" joined connection "$d39d01e0-5101-4d79-bd8d-a8620c389efa" (1 users now present)
guacd[1800]: ERROR: SSH handshake failed.
guacd[1]: INFO: Connection "$d39d01e0-5101-4d79-bd8d-a8620c389efa" removed.
More info on my environment in my thread in this mailing list on Tuesday, January 9, 2024 8:03:04 PM GMT+1.
I added a nightly "docker restart guacd" cronjob to the host as a quick workaround.
Best wishes
Michael
Gesendet: Freitag, 12. Januar 2024 um 02:42 Uhr
Von: "Nick Couchman"
An: user@guacamole.apache.org
Betreff: Re: Major bug message log in guacd 1.5.4
On Thu, Jan 11, 2024 at 5:42 PM Weston Thayer wrote:
Overall. Our test is just 1 user re-connecting to the same VM over RDP over and over.
Thanks for clarifying. FWIW, I'm running Guacamole 1.5.4 (native build/install), on CentOS 7 (FreeRDP 2.2.0), and I've gone way past the 58th successive connection without hitting this issue.
-Nick
-
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org