Btw, for anyone curious, the issue was that I accidentally created a 
directory at this location:
/usr/local/bin/service

Ansible was attempting to use this for the service executable. Both of 
Brian's tips made this clear.

Thanks again!

On Wednesday, January 22, 2014 2:18:46 PM UTC-5, Paul Pearcy wrote:
>
> Thank you Brian!
>
> Both your tips were very helpful in showing why things were broken. The 
> help is much appreciated.
>
> Best Regards,
> Paul
>
> On Friday, January 17, 2014 4:08:50 PM UTC-5, Brian Coca wrote:
>>
>> Probably the service has no status option(not LSB required) and the 
>> service name does not match the executable. 
>>
>> Try using pattern=<executable> so the service module has something it can 
>> determine status from.
>>
>> If that fails: export ANSIBLE_KEEP_REMOTE_FILES=1 and run the command, 
>> then you'll have the full python script on the remote server and you can 
>> run in debug mode.
>>
>> Brian Coca
>>  
>

-- 
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].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to