Sure, here's the output. Also, thanks I'll change the vars
PLAY [webservers]
*************************************************************
GATHERING FACTS
***************************************************************
ok: [ec2-67-202-54-100.compute-1.amazonaws.com]
TASK: [ensure log directory]
**************************************************
[DEPRECATION WARNING]: Legacy variable substitution, such as using ${foo}
or
$foo instead of {{ foo }} is currently valid but will be phased out and has
been out of favor since version 1.2. This is the last of legacy features on
our
deprecation list. You may continue to use this if you have specific needs
for
now. This feature will be removed in version 1.6. Deprecation warnings can
be
disabled by setting deprecation_warnings=False in ansible.cfg.
ok: [ec2-67-202-54-100.compute-1.amazonaws.com]
TASK: [deploy code from repository]
*******************************************
ok: [ec2-67-202-54-100.compute-1.amazonaws.com]
TASK: [install dependencies into virtualenv]
**********************************
ok: [ec2-67-202-54-100.compute-1.amazonaws.com]
TASK: [create supervisor program config]
**************************************
ok: [ec2-67-202-54-100.compute-1.amazonaws.com]
TASK: [create nginx site config]
**********************************************
ok: [ec2-67-202-54-100.compute-1.amazonaws.com]
TASK: [link nginx config]
*****************************************************
ok: [ec2-67-202-54-100.compute-1.amazonaws.com]
TASK: [start app]
*************************************************************
failed: [ec2-67-202-54-100.compute-1.amazonaws.com] => {"failed": true}
msg: pile: ERROR (no such process)
FATAL: all hosts have already failed -- aborting
PLAY RECAP
********************************************************************
to retry, use: --limit @/home/achumbley/deploy.retry
ec2-67-202-54-100.compute-1.amazonaws.com : ok=7 changed=0
unreachable=0 failed=1
On Thursday, February 13, 2014 8:40:23 AM UTC-5, Michael DeHaan wrote:
>
> Can I see the output so I can see the error at the point it occurs?
>
> BTW, quick note -- I should point out that you are still using $old
> variables
>
> Variables should be using the Jinja2 style as denoted on docs.ansible.com,
> i.e. {{ variable }}
>
> In 1.4.X, these emit deprecation warnings, and they will be no longer be
> supported in 1.6. (1.5 releases in less than a month, so 1.6 will follow
> in a couple more)
>
>
>
>
> On Wed, Feb 12, 2014 at 8:37 PM, Alex Chumbley <[email protected]<javascript:>
> > wrote:
>
>>
>>
>> On Wednesday, February 12, 2014 6:58:37 PM UTC-5, Alex Chumbley wrote:
>>
>>> Whenever I try to deploy my app using ansible-playbook, it fails on
>>> start app since it says "ERROR (no such process)".
>>>
>>> Can't understand why this is happening. Anyone know good docs on this
>>> stuff or know the answer?
>>>
>> --
>> 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:>
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
--
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.
