Perhpas I have a misunderstanding here

When you say " no connection is involved"

If I'm right it is possible to ssh from a server to itself - shown by a new
shell and the ability to exit back to the previous shell - or am I mistaken
and it's somehow ignoring that

Is this not what ansible is doing if you run a playbook on the same server
(without delegate_to or local connection)?

That would seem to be what's happening from the ssh output (broken pipe)
but I may be completely turned around in my understanding here (?)

On Fri, 25 Jun 2021 at 22:19, needabettername <[email protected]> wrote:

> Thanks Brian
>
> Not quite sure I understand, it's the output I'm trying to get (more of)
> to understand why it's failing.
>
> In case it helps at all
>
>
> Here's the play 2 created that it fails on. This is fine to run directly
> through ansible-playbook, just not through that play1
>
> - hosts: nott
>   become: yes
>   vars_files:
>     - /$LINUX_PLAYBOOKS/paperless/mont_nott_vars.yml
>   tasks:
>   roles:
>     # - geerlingguy.postgresql
>     - paperless-ng
>     # - geerlingguy.nginx
>
>
> Here's the section of play 1
>   # post_tasks:
>   - name: run the play - $LINUX_PLAYBOOKS/paperless/{{play_filename}}
>     import_playbook: $LINUX_PLAYBOOKS/paperless/{{play_filename}}
>     register: playoutput
>     ignore_errors: yes
>     # delegate_to: 127.0.0.1
>     become: yes
>     # debugger: on_failed
>
>   - name: get debug output
>     debug:
>       var: playoutput
>
> Does that help, or is there something else I can run to get more detail
> from that mysterious " See stdout/stderr for the exact error"
> That's what the debug var playoutput should provide isn't it ??
>
> On Friday, 25 June 2021 at 15:18:51 UTC+1 Brian Coca wrote:
>
>> The import would not fail with connection issues, no connection is
>> involved, what is failing is a task, but you are not providing enough
>> output to determine which task it is.
>>
>> --
>> ----------
>> Brian Coca
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Ansible Project" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/ansible-project/iTafYTAtEIA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/49307f93-581d-469a-aaf9-cfefc0138466n%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/49307f93-581d-469a-aaf9-cfefc0138466n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAO-qrLaVRu%3DjPDGCUSivQotouYUFheTWhJTn8XOO0hz%3DuS9Rig%40mail.gmail.com.

Reply via email to