Stuck connections to etserver, with infinite "Shutting down sentry" messages

[offbyone]

Connecting from my macOS client to my linux server, the client is just "sticking" and not ever finishing a connection. Even Ctrl-C and Ctrl-\ don't quit it, only closing the terminal tab or sending a kill signal from outside the process does.

Looking at the logs, I see what looks like a successful connection in the etclient log, and then tens of thousands of "Shutting down sentry" messages in the stderr log:

$ et --version
et version 6.2.9

$ head /tmp/etclient-stderr-2025-05-07_21-51-25.log
Setting up and starting sentry
Shutting down sentry
Shutting down sentry
Shutting down sentry
Shutting down sentry
... 

$ wc -l /tmp/etclient-stderr-2025-05-07_21-51-25.log
 1855934 /tmp/etclient-stderr-2025-05-07_21-51-25.log

$ ssh prime
Last login: Fri Apr 25 04:50:00 2025 from 100.113.157.9

offby1 in 🌐 prime in ~
❯ /usr/bin/etserver --version
et version 6.2.4

I updated the remote server, too, just in case, and even with 6.2.9 I still see the same issue.

Here's a client log:

etclient-2025-05-07_21-51-25.log

I'm able to ssh to the hosts, and port 2022 is open:

$ nc -vz prime 2022
Connection to prime port 2022 [tcp/down] succeeded!

I've been tailing the et.service logs on the destination, though, and I don't see any activity there.

[offbyone]

I got some logging from the server as well:

May 08 05:18:22 prime etserver[2404113]: [INFO 2025-05-08 05:18:22,201 etserver-main TerminalServerMain.cpp:192] In child, about to start server.
May 08 05:18:22 prime etserver[2404113]: [INFO 2025-05-08 05:18:22,201 etserver-main TcpSocketHandler.cpp:224] Listening on 0.0.0.0:2022/2/1/6
May 08 05:18:22 prime etserver[2404113]: [INFO 2025-05-08 05:18:22,201 etserver-main TcpSocketHandler.cpp:224] Listening on 0.0.0.0:2022/10/1/6
May 08 05:18:22 prime etserver[2404113]: [INFO 2025-05-08 05:18:22,201 etserver-main TerminalServer.cpp:23] Creating server
May 08 05:18:49 prime etserver[2404113]: [WARNING 2025-05-08 05:18:49,973 server-clientHandler ServerConnection.cpp:127] Error handling new client: Failed a call to readAll
May 08 05:18:50 prime etserver[2404113]: [INFO 2025-05-08 05:18:50,007 etserver-main UserTerminalRouter.cpp:20] Listening to id/key FIFO
May 08 05:18:50 prime etserver[2404113]: [INFO 2025-05-08 05:18:50,007 etserver-main UserTerminalRouter.cpp:30] Connected
May 08 05:18:50 prime etserver[2404113]: [INFO 2025-05-08 05:18:50,020 server-clientHandler ServerConnection.cpp:76] Got client with id: pYaIZAZjeFsA912o
May 08 05:18:50 prime etserver[2404113]: [INFO 2025-05-08 05:18:50,020 server-clientHandler ServerConnection.cpp:104] New client.  Setting up connection
May 08 05:18:50 prime etserver[2404113]: [INFO 2025-05-08 05:18:50,026 128466026497728 TerminalServer.cpp:411] RUNNING TERMINAL
May 08 05:18:50 prime etserver[2404113]: [INFO 2025-05-08 05:18:50,026 128466026497728 PortForwardHandler.cpp:67] Creating pipe at /tmp/et_forward_sock_NltsC9/sock
May 08 05:18:50 prime etserver[2404113]: [INFO 2025-05-08 05:18:50,042 pYaIZAZjeFsA912o TerminalServer.cpp:363] Got terminal info
May 08 05:18:50 prime etserver[2404113]: [INFO 2025-05-08 05:18:50,216 pYaIZAZjeFsA912o ForwardSourceHandler.cpp:22] Tunnel /tmp/et_forward_sock_NltsC9/sock -> /private/tmp/com.apple.launchd.IwuntCDIYz/Listeners socket created with fd 13

[offbyone]

I've upgraded et to 6.2.9 on the server host and the same thing continues.

[offbyone]

I've now confirmed the issue both over my tailscale tailnet and directly over the LAN.

et from one linux host to the other works et from my macOS laptop to either linux host does not.