Page 1 of 1

ssh client early "broken pipe" failure

Posted: Thu Mar 22, 2018 6:59 pm
by Paul Gilmartin
(This concerns ssh client, not the more commonly discussed server.)
(This has no problem with a MacOS client, but there I see no
"Sending env LANG = en_US.UTF-8".)
from command ssh -vvoPort=2222 192.168.0.3 "date":
...
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/pi/.ssh/id_rsa
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug2: input_userauth_pk_ok: fp e8:fa:03:28:b3:65:04:c1:aa:2c:73:05:fa:35:a2:aa
debug1: Authentication succeeded (publickey).
Authenticated to 192.168.0.3 ([192.168.0.3]:2222).
debug2: fd 5 setting O_NONBLOCK
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug2: callback start
debug2: fd 3 setting TCP_NODELAY
debug2: client_session2_setup: id 0
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug2: channel 0: request env confirm 0
debug1: Sending command: date
debug2: channel 0: request exec confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
Write failed: Broken pipe

Thanks,
gil