We came across the same problem yesterday. It seemed to start happening after upgrading to Capistrano 2.3.0. Perhaps a regression? We found some earlier information about this problem. Apparently, one of the Capistrano tasks runs as user "app" by default, rather than as the specified user.
We had to add "set :runner, 'username'" to our Capistrano script to make it work again. I think "set :runner, user" should do the trick, too. -Mirko On May 7, 1:14 pm, "Mark A. Richman" <[EMAIL PROTECTED]> wrote: > I am using `cap servers:setup` with the railsmachine gem, and I get > this error: > > * executing `servers:setup' > * executing `deploy:setup' > * executing "umask 02 && mkdir -p /var/www/apps/myproject /var/www/ > apps/myproject/releases /var/www/apps/myproject/shared /var/www/apps/ > myproject/shared/system /var/www/apps/myproject/shared/log /var/www/ > apps/myproject/shared/pids" > servers: ["localhost"] > Password: > [localhost] executing command > ** [out :: localhost] sudo: no passwd entry for app! > command finished > > Any suggestions? > > Thanks, > Mark --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
