Não é possível iniciar o unicórnio na porta 80 usando capistrano

cap production unicorn:start falha com o seguinte erro, tentando iniciar meu aplicativo rails na porta 80.

 F, [2013-06-14T04:33:51.420113 #13986] FATAL -- : error adding listener addr=0.0.0.0:80 /home/ec2-user/apps/bdr_prod/shared/bundle/ruby/2.0.0/gems/unicorn-4.6.2/lib/unicorn/socket_helper.rb:147:in `initialize': Permission denied - bind(2) (Errno::EACCES) from /home/ec2-user/apps/bdr_prod/shared/bundle/ruby/2.0.0/gems/unicorn-4.6.2/lib/unicorn/socket_helper.rb:147:in `new' from /home/ec2-user/apps/bdr_prod/shared/bundle/ruby/2.0.0/gems/unicorn-4.6.2/lib/unicorn/socket_helper.rb:147:in `bind_listen' from /home/ec2-user/apps/bdr_prod/shared/bundle/ruby/2.0.0/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:229:in `listen' from /home/ec2-user/apps/bdr_prod/shared/bundle/ruby/2.0.0/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:773:in `block in bind_new_listeners!' from /home/ec2-user/apps/bdr_prod/shared/bundle/ruby/2.0.0/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:773:in `each' from /home/ec2-user/apps/bdr_prod/shared/bundle/ruby/2.0.0/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:773:in `bind_new_listeners!' from /home/ec2-user/apps/bdr_prod/shared/bundle/ruby/2.0.0/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:141:in `start' from /home/ec2-user/apps/bdr_prod/shared/bundle/ruby/2.0.0/gems/unicorn-4.6.2/bin/unicorn:126:in `' from /home/ec2-user/apps/bdr_prod/shared/bundle/ruby/2.0.0/bin/unicorn:23:in `load' from /home/ec2-user/apps/bdr_prod/shared/bundle/ruby/2.0.0/bin/unicorn:23:in `' 

set use_sudo true retorna o seguinte erro

 * executing "sudo -p 'sudo password: ' rm -rf /home/ec2-user/apps/bdr_prod/releases/20130517085418" servers: ["64.433.69.129"] [ec2-user@64.433.69.129] executing command *** [err :: ec2-user@64.433.69.129] sudo *** [err :: ec2-user@64.433.69.129] : *** [err :: ec2-user@64.433.69.129] sorry, you must have a tty to run sudo *** [err :: ec2-user@64.433.69.129] command finished in 1542ms 

Eu tive problemas com isso antes, e tive que adicionar isso ao meu deploy.rb :

 default_run_options[:pty] = true 

Para executar o comando ssh sudo no servidor remoto, desabilite ‘require tty’ no servidor remoto

Corre:

~$ sudo visudo

Editar: / etc / sudoers

# Desativar “ssh hostname sudo”, porque mostrará a senha em claro.

# Você precisa executar “ssh -t hostname sudo”.

# comment require tty

# Defaults requiretty

Referência: http://www.lansweeper.com/kb/39/TTY-Required-error-during-linux-scanning.html