Add faq note about ssh ServerAliveInterval (#55568)
parent
a89a2cf33f
commit
76dba7aa4f
|
@ -96,6 +96,13 @@ With earlier versions of Ansible, it was necessary to configure a
|
|||
suitable `ProxyCommand` for one or more hosts in `~/.ssh/config`,
|
||||
or globally by setting `ssh_args` in `ansible.cfg`.
|
||||
|
||||
.. _ssh_serveraliveinterval:
|
||||
|
||||
How do I get Ansible to notice a dead target in a timely manner?
|
||||
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
|
||||
|
||||
You can add ``-o ServerAliveInterval=NumberOfSeconds`` in ``ssh_args`` from ``ansible.cfg``. Without this option, SSH and therefore Ansible will wait until the TCP connection times out. Another solution is to add ``ServerAliveInterval`` into your global SSH configuration. A good value for ``ServerAliveInterval`` is up to you to decide; keep in mind that ``ServerAliveCountMax=3`` is the SSH default so any value you set will be tripled before terminating the SSH session.
|
||||
|
||||
.. _ec2_cloud_performance:
|
||||
|
||||
How do I speed up management inside EC2?
|
||||
|
|
Loading…
Reference in New Issue