From f5befa5ab4ce98e30eba57f7f81dfeab548c78ce Mon Sep 17 00:00:00 2001 From: John R Barker Date: Tue, 17 Apr 2018 13:22:43 +0100 Subject: [PATCH] Correct formatting (#38874) (#38877) (cherry picked from commit 3d3781db5719a83d21b189a61480dee1f4418ffc) --- .../network/user_guide/network_debug_troubleshooting.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/docsite/rst/network/user_guide/network_debug_troubleshooting.rst b/docs/docsite/rst/network/user_guide/network_debug_troubleshooting.rst index cd9c2510617..f7c36f812e2 100644 --- a/docs/docsite/rst/network/user_guide/network_debug_troubleshooting.rst +++ b/docs/docsite/rst/network/user_guide/network_debug_troubleshooting.rst @@ -95,7 +95,7 @@ From the log notice: If the log reports the port as ``None`` this means that the default port is being used. A future Ansible release will improve this message so that the port is always logged. -Because the log files are verbose, you can use grep to look for specific information. For example, once you have identified the ```pid`` from the ``creating new control socket for host`` line you can search for other connection log entries:: +Because the log files are verbose, you can use grep to look for specific information. For example, once you have identified the ``pid`` from the ``creating new control socket for host`` line you can search for other connection log entries:: grep "p=28990" $ANSIBLE_LOG_PATH @@ -396,8 +396,9 @@ For example: Suggestions to resolve: -Increase value of presistent connection idle timeout. -.. code-block:: yaml +Increase value of persistent connection idle timeout: + +.. code-block:: sh export ANSIBLE_PERSISTENT_CONNECT_TIMEOUT=60