1 votes

Terminer les connexions SSH qui se bloquent ou deviennent inactives

J'ai rencontré des cas où une connexion SSH sur mon système d'exploitation Linux devient inactive, se fige et reste ouverte. Cela finit par provoquer une bombe à fourche et les messages d'erreur suivants :

/etc/profile.d/locallib.sh: fork: retry: No child processes
/etc/profile.d/locallib.sh: fork: Resource temporarily unavailable
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 254) at io.c(226) [sender=3.1.1]

Les configurations suivantes seront mises en place dans ~/.ssh/ssh_config empêcher ces connexions SSH inopérantes ?

Host *
ClientAliveCountMax 3
ClientAliveInterval 0

2voto

paxri01 Points 126

Je crois que les paramètres que vous recherchez sont les suivants :

  ServerAliveInterval 120
  ServerAliveCountMax 2

De man ssh_config :

 ServerAliveCountMax
         Sets the number of server alive messages (see below) which may be sent
         without ssh(1) receiving any messages back from the server.  If this
         threshold is reached while server alive messages are being sent, ssh
         will disconnect from the server, terminating the session.  It is
         important to note that the use of server alive messages is very dif
         ferent from TCPKeepAlive (below).  The server alive messages are sent
         through the encrypted channel and therefore will not be spoofable.
         The TCP keepalive option enabled by TCPKeepAlive is spoofable.  The
         server alive mechanism is valuable when the client or server depend on
         knowing when a connection has become inactive.

         The default value is 3.  If, for example, ServerAliveInterval (see
         below) is set to 15 and ServerAliveCountMax is left at the default, if
         the server becomes unresponsive, ssh will disconnect after approxi
         mately 45 seconds.

 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.

SistemesEz.com

SystemesEZ est une communauté de sysadmins où vous pouvez résoudre vos problèmes et vos doutes. Vous pouvez consulter les questions des autres sysadmins, poser vos propres questions ou résoudre celles des autres.

Powered by:

X