2012-05-13 22 views
9

Estaba siguiendo el Railscast en Despliegue a un VPS y todo funciona sin problemas hasta que intento ejecutar cap deploy. Parece que falla al intentar encontrar un directorio. Aquí está el mensaje de error:Error al implementar con Capistrano

* executing `deploy' 
triggering before callbacks for `deploy' 
* executing `deploy:check_revision' 
* executing `deploy:update' 
** transaction: start 
* executing `deploy:update_code' 
updating the cached checkout on all servers 
executing locally: "git ls-remote [email protected]:markprovan/dropwall_rails.git master" 
command finished in 2531ms 
* executing "if [ -d /home/deployer/apps/dropwall_rails/shared/cached-copy ]; then cd /home/deployer/apps/dropwall_rails/shared/cached-copy && git fetch -q origin && git fetch -- tags -q origin && git reset -q --hard 9407f1feb2ea5b1c4a0666196bdcbb9ad888563e && git clean -q -d -x -f; else git clone -q [email protected]:markprovan/dropwall_rails.git /home/deployer/apps/dropwall_rails/shared/cached-copy && cd /home/deployer/apps/dropwall_rails/shared/cached-copy && git checkout -q -b deploy 9407f1feb2ea5b1c4a0666196bdcbb9ad888563e; fi" 
servers: ["209.61.142.61"] 
Password: 
[209.61.142.61] executing command 
** [209.61.142.61 :: out] The authenticity of host 'github.com (207.97.227.239)' can't be established. 
** RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48. 
** Are you sure you want to continue connecting (yes/no)? 
** [209.61.142.61 :: out] yes 
** Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts. 
command finished in 2655ms 
copying the cached version to /home/deployer/apps/dropwall_rails/releases/20120513204913 
* executing "cp -RPp /home/deployer/apps/dropwall_rails/shared/cached-copy /home/deployer/apps/dropwall_rails/releases/20120513204913 && (echo 9407f1feb2ea5b1c4a0666196bdcbb9ad888563e > /home/deployer/apps/dropwall_rails/releases/20120513204913/REVISION)" 
servers: ["209.61.142.61"] 
[209.61.142.61] executing command 
** [out :: 209.61.142.61] cp: cannot create directory `/home/deployer/apps/dropwall_rails/releases/20120513204913': No such file or directory 
command finished in 482ms 
*** [deploy:update_code] rolling back 
* executing "rm -rf /home/deployer/apps/dropwall_rails/releases/20120513204913; true" 
servers: ["209.61.142.61"] 
[209.61.142.61] executing command 
command finished in 479ms 
failed: "sh -c 'cp -RPp /home/deployer/apps/dropwall_rails/shared/cached-copy /home/deployer/apps/dropwall_rails/releases/20120513204913 && (echo 9407f1feb2ea5b1c4a0666196bdcbb9ad888563e > /home/deployer/apps/dropwall_rails/releases/20120513204913/REVISION)'" on 209.61.142.61 

He pasado siglos en esto y parece que no puedo encontrar dónde me estoy equivocando.

Respuesta

23

¿Has ejecutado cap deploy:setup y cap deploy:check? Estos deberían resaltar una gran cantidad de problemas comunes.

El error que causa la falla anterior, sin embargo, parece un problema de permisos.

cp: cannot create directory `/home/deployer/apps/dropwall_rails/releases/20120513204913': No such file or directory 

Asegúrese de que la carpeta exista y de que el usuario de implementación tenga los permisos correctos para manipularla.

0

El problema de los privilegios puede ser causado por el comportamiento de Capistrano use_sudo por defecto.

Esto puede ser anulado por los siguientes parámetros de configuración: conjunto: use_sudo, falsa

Lo extraño es que si este parámetro no se establece en false, Capistrano utilizará para algunos comandos sudo y no utilizar para otros. Me parece como un insecto.

Cuestiones relacionadas