Cracked it! It absolutely was down to errors in the script that I was just 
missing: one I'd inherited from where I'd copied it from (the sqlite3 
command) and another of my own doing that was attempting to change a 
property in a file that didn't exist yet.

Thank you sooooooo much for all your help and for pushing me to see this 
through proper style :D

This playbook is gonna rock hard!


On Wednesday, 20 August 2014 19:42:37 UTC+1, Michael DeHaan wrote:
>
> I mean this by "the way in which something fails".
>
> Yeah, I have no idea here.
>
> Your script returned a non-zero exit code and no output, which is all 
> ansible knows.   It would depend on the behavior of the script.   And that 
> script may not have proper error handling to say why what was called in 
> that script died.
>
> I'd start by adding extra output to your script, etc.
>
>
>
>
> On Wed, Aug 20, 2014 at 2:38 PM, Dan Bohea <[email protected] <javascript:>
> > wrote:
>
>> OK, good to rule the PATH out then.
>>
>> Not sure what you mean by failure mode but here's the -vvvv output for 
>> the task that tries to run the script in case that helps. As you can see, 
>> "stderr" and "stdout" don't seem to have anything to say.
>>
>> TASK: [osx | Execute .osx] 
>> **************************************************** 
>>
>> <127.0.0.1> REMOTE_MODULE command ./osx.sh --ansible #USE_SHELL
>>
>> <127.0.0.1> EXEC ['/bin/sh', '-c', 'mkdir -p 
>> $HOME/.ansible/tmp/ansible-tmp-1408559599.6-238488648926013 && chmod a+rx 
>> $HOME/.ansible/tmp/ansible-tmp-1408559599.6-238488648926013 && echo 
>> $HOME/.ansible/tmp/ansible-tmp-1408559599.6-238488648926013']
>>
>> <127.0.0.1> PUT /var/folders/5d/ry1gfqbx0rs8bmpy7lw0909w0000gn/T/tmpjDc9QL 
>> TO /Users/danbohea/.ansible/tmp/ansible-tmp-1408559599.6-238488648926013/
>> command
>>
>> <127.0.0.1> EXEC ['/bin/sh', '-c', u'LANG=en_US.UTF-8 
>> LC_CTYPE=en_US.UTF-8 /usr/bin/python 
>> /Users/danbohea/.ansible/tmp/ansible-tmp-1408559599.6-238488648926013/command;
>>  
>> rm -rf 
>> /Users/danbohea/.ansible/tmp/ansible-tmp-1408559599.6-238488648926013/ 
>> >/dev/null 2>&1']
>>
>> changed: [127.0.0.1] => {"changed": true, "cmd": "./osx.sh --ansible", 
>> "delta": "0:00:01.105129", "end": "2014-08-20 11:33:20.811287", "rc": 0, 
>> "start": "2014-08-20 11:33:19.706158", "stderr": "", "stdout": ""}
>>
>>  -- 
>> 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] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ansible-project/d0e5319d-88b9-4523-9a0e-5d672b0756a7%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/ansible-project/d0e5319d-88b9-4523-9a0e-5d672b0756a7%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/6b666300-dee6-4e45-999e-6a73cf7efa4b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to