Monitoring, Management & Location Tracking

What to do when we get "Write failed: Broken pipe" error during a putty session to Airwave

Aruba Employee
Problem:

 

Getting "Write failed: Broken pipe" error during a putty session to Airwave



Diagnostics:

 

It’s possible that your server closes connections that are idle for too long. Another reason would be IP address Conflict.



Solution

 

If its related to server closing the connection, we can update either the client alive interval or the server alive interval.

ServerAliveInterval
         Sets a timeout interval in seconds after which if no data has
         been received from the server, ssh(1) will send a message through
         the encrypted channel to request a response from the server.  The
         default is 0, indicating that these messages will not be sent to
         the server.  This option applies to protocol version 2 only.

 ClientAliveInterval
         Sets a timeout interval in seconds after which if no data has
         been received from the client, sshd(8) will send a message
         through the encrypted channel to request a response from the
         client.  The default is 0, indicating that these messages will
         not be sent to the client.  This option applies to protocol
         version 2 only.

To update your server (and restart your sshd) execute the below command on Airwave CLI,

# echo "ClientAliveInterval 60" | sudo tee -a /etc/ssh/sshd_config

 

However, if its related to IP conflict, Check where the client and the server are getting their IP address. If you keep ping server.example.com running, does it help make the connection last longer? If so, you have an IP address conflict.

Version history
Revision #:
2 of 2
Last update:
3 weeks ago
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: