Bug 8346 - Client dies with PeekNamedPipe error in log
Summary: Client dies with PeekNamedPipe error in log
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
Depends on:
Reported: 2024-05-17 08:49 CEST by Pierre Ossman
Modified: 2024-05-21 13:34 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2024-05-17 08:49:37 CEST
We've got a few reports where the client pops up the error message "Your connection to the server was unexpectedly shut down.", but the session continues working. In the log, we can see this error:

> 2024-05-16T17:15:12: ServiceProcess: PeekNamedPipe error 1450
> 2024-05-16T17:15:12: Last line was repeated 6 time(s).
> 2024-05-16T17:15:12: The SSH process unexpectedly exited before VNC viewer process.

It seems something breaks in the communication with ssh, and tlclient therefore (incorrectly) assumes that ssh has died.

1450 is ERROR_NO_SYSTEM_RESOURCES, which Microsoft describes as "Insufficient system resources exist to complete the requested service.". So it sounds like something is seriously amiss with these client devices. The users are not reporting anything else that suggests the machine is bogged down, though.

Note You need to log in before you can comment on or make changes to this bug.