Looks like the app user does not exist. Try logging in manually as the user.
>
> Any ideas?
>
> Thanks,
> jeremy
> >
>
--
=================
Michael Hale
mike...@gmail.com
m: 919.961.7171
jabber: mike...@gmail.com
------------------------------
>
> On Tue, May 13, 2008 at 4:49 PM, jeremy*pinnix <jpi...@gmail.com>
> wrote:
>>
>> I've used dep1 for quite a while, and have just decided to give
>> dep2 a
>> try.
>>
>> Initial stack creation worked just fine. However, upon the initial
>> "cap deploy:setup" I am getting an error at the following stage of
>> the
>> deploy script:
>>
>> * executing `deploy:setup'
>> * executing "umask 02 && mkdir -p /var/www/apps/xxxxxx /var/www/
>> apps/
>> xxxxxx/releases /var/www/apps/xxxxxx/shared /var/www/apps/xxxxxx/
>> shared/system /var/www/apps/xxxxxx/shared/log /var/www/apps/xxxxxx/
>> shared/pids"
>> servers: ["xx.xxx.xxx.xxx"]
>> [xx.xxx.xxx.xxx] executing command
>> ** [out :: xx.xxx.xxx.xxx] sudo: no passwd entry for app!
>
> Looks like the app user does not exist. Try logging in manually as
> the user.
>
>>
>> Any ideas?
>>
>> Thanks,
>> jeremy
>>>
>>
>
>
use:
set :runner, “deploy” (or whatever user you are running as for your
deploy)
in your deploy.rb