Geek Answers Handbook

Capistrano fails while trying to deploy Rails agent manifest

I am trying to deploy a Rails application that worked successfully earlier, but Capistrano works during deployment. I do not believe that I changed anything other than changing the Rails application code itself and updating some stones (i.e., the deploy.rb file is identical to the once working setup.)

Here the line in which it appears does not work:

executing "cp -- /u/apps/myapp/shared/assets/manifest.yml /u/apps/myapp/releases/unable/assets_manifest.yml"

Note that the directory that he is trying to copy is called unable . As if he can't get a new name / release date or something else? And even earlier, he does this without errors:

 executing "cd -- /u/apps/myapp/releases/20130507041223 && bundle exec rake RAILS_ENV=production RAILS_GROUPS=assets assets:precompile"

The rest of the interesting conclusion is this:

 ** cp: cannot create regular file `/u/apps/myapp/releases/unable/assets_manifest.yml' ** No such file or directory failed: "rvm_path=$HOME/.rvm/ $HOME/.rvm/bin/rvm-shell 'default' -c 'cp -- /u/apps/myapp/shared/assets/manifest.yml /u/apps/myapp/releases/unable/assets_manifest.yml'"

UPDATE: This seems to be a bug in Capistrano 2.15.4. The problem decreased to version 2.14.2. I have described the error here in detail:

https://github.com/capistrano/capistrano/issues/468

+8
ruby-on-rails capistrano
source share
2 answers

This seems to be a bug in Capistrano 2.15.4. The transition to version 2.14.2 fixes the problem. See https://github.com/capistrano/capistrano/issues/468

+6
source share

There was the same problem with 2.15.4. This was due to the fact that I changed my hostname to something invalid - every time I was told that "it was not possible to resolve the host", which for some reason raised this version of the cap. It seems that setting the hostname to the correct setting has been sorted.

0
source share

More articles:


All Articles