On Thursday, 8 May 2014 00:57:36 UTC+2, Strahinja Kustudić wrote:
You could set an environment variable:
>
> ANSIBLE_KEEP_REMOTE_FILES=1
>
> and run ansible again. Once it fails, see what files were executed, log
> into the remote host and run the failed python script with:
>
> python -m trace --trace script.py
>
Thanks for this tip. I did exactly as you describe, and ran the script on
the host. To my surprise, it did what it was supposed to! The last few
lines from the trace output show:
--- modulename: encoder, funcname: _iterencode_dict
encoder.py(281): if markers is not None:
encoder.py(282): del markers[markerid]
encoder.py(368): return ''.join(chunks)
{"state": "stopped", "changed": true, "name": "hdfs-sync"}
service(2146): sys.exit(0)
The service stopped running, so the script did its work. I don't understand
why I get an error from ansible on my laptop then. Any ideas developers?
Anand
--
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/29a2b12b-4252-4f8c-ba95-5df25bdab65a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
