ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

fixed a syntax problem that was preventing a warning box from being displayed

Browse source
This commit is contained in:
David Newswanger 2017-08-07 15:50:53 -04:00 committed by Toshio Kuratomi
parent 3b0e9ded91
commit ebb1d75ee0
1 changed files with 18 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

37
docs/docsite/rst/network_debug_troubleshooting.rst
View file

@ -36,7 +36,7 @@ Errors generally fall into one of the following categories:
* Not using ``connection: local`` * Not using ``connection: local``
.. warning: ``unable to open shell` .. warning:: ``unable to open shell``
The ``unable to open shell`` message is new in Ansible 2.3, it means that the ``ansible-connection`` daemon has not been able to successfully The ``unable to open shell`` message is new in Ansible 2.3, it means that the ``ansible-connection`` daemon has not been able to successfully
talk to the remote network device. This generally means that there is an authentication issue. See the "Authentication and connection issues" section talk to the remote network device. This generally means that there is an authentication issue. See the "Authentication and connection issues" section
@ -508,39 +508,38 @@ Add `authorize: yes` to the task. For example:
.. delete_to not honoured .. delete_to not honoured
---------------------- ----------------------
FIXME Do we get an error message FIXME Do we get an error message
FIXME Link to howto FIXME Link to howto
fixmes fixmes
====== ======
Error: "number of connection attempts exceeded, unable to connect to control socket" Error: "number of connection attempts exceeded, unable to connect to control socket"
------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------
**Platforms:** Any **Platforms:** Any
This occurs when Ansible wasn't able to connect to the remote device and obtain a shell with the timeout. This occurs when Ansible wasn't able to connect to the remote device and obtain a shell with the timeout.
This information is available when ``ANSIBLE_LOG_PATH`` is set see (FIXMELINKTOSECTION): This information is available when ``ANSIBLE_LOG_PATH`` is set see (FIXMELINKTOSECTION):
.. code-block:: yaml .. code-block:: yaml
less $ANSIBLE_LOG_PATH less $ANSIBLE_LOG_PATH
2017-03-10 15:32:06,173 p=19677 u=fred | connect retry timeout expired, unable to connect to control socket 2017-03-10 15:32:06,173 p=19677 u=fred | connect retry timeout expired, unable to connect to control socket
2017-03-10 15:32:06,174 p=19677 u=fred | persistent_connect_retry_timeout is 15 secs 2017-03-10 15:32:06,174 p=19677 u=fred | persistent_connect_retry_timeout is 15 secs
2017-03-10 15:32:06,222 p=19669 u=fred | fatal: [veos01]: FAILED! => { 2017-03-10 15:32:06,222 p=19669 u=fred | fatal: [veos01]: FAILED! => {
Suggestions to resolve: Suggestions to resolve:
Do stuff For example: Do stuff For example:
.. code-block:: yaml .. code-block:: yaml
Example stuff Example stuff