Bug 2758

Summary:	Connection to xx.xx.xx.xx port 22: Broken pipe
Product:	Portable OpenSSH	Reporter:	jg
Component:	ssh	Assignee:	Assigned to nobody <unassigned-bugs>
Status:	CLOSED WONTFIX
Severity:	enhancement	CC:	djm, dtucker
Priority:	P5
Version:	7.2p2
Hardware:	Other
OS:	Linux

Description jg 2017-08-12 20:28:11 AEST

Hello
Similar to bug 2750

Often I see this style of message below from various connections on different computers, from my stable Ethernet connection, to my AWS server and other servers.


$ ssh -i "j.pem" ubuntu@ec2-xx-xx-xx-xx.eu-west-1.compute.amazonaws.com
ubuntu@ip-xx-xx-xx-xx:~/$

<after a few hours>

packet_write_wait: Connection to xx.xx.xx.xx port 22: Broken pipe
$

Could that just say "Connection closed" please ? eg.

"Connection closed xx.xx.xx.xx port 22"

I'm not sure if the IP and port are relavent to include in the message, but anyway, something clearer than "Broken pipe"

Regards, Jonny

Comment 1 Darren Tucker 2017-08-12 20:41:16 AEST

(In reply to jg from comment #0)
[...]
> packet_write_wait: Connection to xx.xx.xx.xx port 22: Broken pipe
> $
> 
> Could that just say "Connection closed" please ? eg.

Is that being triggered by a TCP reset?  If so the message seems appropriate.

"Connection closed" means it was deliberately closed be either client or server (ie TCP FIN).  Using it when something else breaks the connection seems like a lie.

Comment 2 jg 2017-08-13 07:14:46 AEST

Hello
Sorry I don't know the reason the connection had a pipe error.

Even "Connection lost" would sound good.


Although in English, "closed" doesn't mean deliberately closed.

Comment 3 Damien Miller 2018-01-05 14:54:45 AEDT

The error indicates the exact condition that caused the connection to drop using one of the system error messages (see "man errno"). To change it to something different would be to lose information.

Comment 4 jg 2018-01-08 04:32:08 AEDT

Why not put something user-friendly first then?

eg add "lost"

Connection lost to xx.xx.xx.xx port 22: Broken pipe

Comment 5 Damien Miller 2018-04-06 14:27:07 AEST

Sorry, like I said - the message indicates the exact error case that caused the connection to be dropped. It's useful information and worth keeping.

Comment 6 Damien Miller 2021-04-23 14:55:51 AEST

closing resolved bugs as of 8.6p1 release