From 76dba7aa4f5fa2dfd561add2771d7b8d123bdbf1 Mon Sep 17 00:00:00 2001 From: Klaas Demter Date: Wed, 1 May 2019 19:04:40 +0200 Subject: [PATCH] Add faq note about ssh ServerAliveInterval (#55568) --- docs/docsite/rst/reference_appendices/faq.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/docsite/rst/reference_appendices/faq.rst b/docs/docsite/rst/reference_appendices/faq.rst index 8e03f4c9f5f..7a4c91bae0e 100644 --- a/docs/docsite/rst/reference_appendices/faq.rst +++ b/docs/docsite/rst/reference_appendices/faq.rst @@ -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?