Write failed: Broken pipe
It’s usually because the SSHD on the server sees that a connection has been closed at some point without a message, and then the client side breaks.
There are three solutions:
Add the following configuration in /etc/ssh/sshd_config of the server: ClientAliveInterval 60
2 if it is difficult to change the server, you can change the client setting: add config file in ~/.ssh/ folder, and add the following configuration: ServerAliveInterval 10, tell the SSH client to send a “keep-alive” packet to the other side every 10 seconds.
3 If you only want to use it temporarily for one operation, you can add an argument to the login command: sSH-O ServerAliveInterval=10 [email protected].
Original: http://blog.csdn.net/hongchangfirst/article/details/51308366
Author: hongchangfirst
Hongchangfirst homepage: http://blog.csdn.net/hongchangfirst
Read More:
- java.net.SocketException: Broken pipe (Write failed)
- Failed sending reply to debugger: Broken pipe
- E / Art: failed sending reply to debugger: a solution to broken pipe
- Python TCP socket programming: send returns broken pipe error?
- Solution to Tomcat’s broken pipe error
- [How to Fix] dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
- dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
- ansible Q&A: Failed to connect to the host via ssh: ssh_exchange_identification and Authentication or per
- C language write() function analysis: write failed bad address
- [Error resolution] paramiko.ssh_exception.SSHException: Error reading SSH protocol banner setting
- Dm7 Dameng database dmrman reports an error OS_ pipe2_ conn_ Server open failed solution
- Failed to restart ssh.service: Unit not found.
- Centos Failed to Modify the port of SSH: error: Bind to port 27615 on 0.0.0.0 failed: Permission denied.
- Cloning failed using an SSH key for authentication
- Solve ssh error: shell request failed on channel 0
- Solve the problem of keyboard interactive authentication with the SSH2 server failed
- Rsync: failed to exec SSH: no such error in remote Rsync
- Could not write JSON: write javaBean error, fastjson version x.x.x, class
- SSH suddenly fails to log in, and an error is reported: failed to start openssh daemon
- EEROR:Windows named pipe error: The system cannot find the file specified. (code:2)