Bug 7598 - Client can hang with "Connecting to agent..." if local socket is unresponsive
Summary: Client can hang with "Connecting to agent..." if local socket is unresponsive
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-03 12:49 CET by Pierre Ossman
Modified: 2024-11-11 15:58 CET (History)
0 users

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pierre Ossman cendio 2020-12-03 12:49:46 CET 
When the client connects it tries to check that all local ports it needs (for local devices) are unused. This process can currently hang if there is something unresponsive on one of those ports as we do a connect() to that port.

Unfortunately we don't log anything at this part, so the only thing the user sees is that the client hangs with "Connection to agent 1.2.3.4..." in the status bar.

We should at least have a short timeout here, or ideally not use connect() at all. Can't we use bind()?


I saw this on a Windows 10 laptop here where something has gone terribly wrong and I have lots of connections stuck in TIME_WAIT. There is nothing listening on the port tested (62596) in this case, but all those dead connections are probably somehow still causing things to lock up.
Comment 1 Pierre Ossman cendio 2024-11-11 15:58:23 CET 
This happened now again, this time with the Windows 10 machine in the lab. Again, lots of sockets in TIME_WAIT.
Note You need to log in before you can comment on or make changes to this bug.