cap deploy, cap deploy:cold fails on ubuntu hardy
Reported by George | August 5th, 2008 @ 03:11 AM
Hi,
using capistrano version 2.4.3
cap deploy and cap deploy:cold fails on ubuntu hardy with the following error messages:
executing "find /var/www/xxxx/releases/20080805090103/public/images /var/www/xxxx/releases/20080805090103/public/stylesheets /var/www/xxxx/releases/20080805090103/public/javascripts -exec touch -t 200808050904.16 {} ';'; true"
servers: ["xxxx"]
[xxxxx] executing command
*** [err :: xxxxx] find: /var/www/xxxxx/releases/20080805090103/public/images: No such file or directory
*** [err :: xxxxx] find: /var/www/xxxxx/releases/20080805090103/public/stylesheets: No such file or directory
*** [err :: xxxxx] find: /var/www/xxxxx/releases/20080805090103/public/javascripts: No such file or directory
command finished
- executing `deploy:symlink'
- executing "rm -f /var/www/xxxxx/current && ln -s /var/www/xxxxx/releases/20080805090103 /var/www/xxxx/current"
servers: ["xxxx"]
[xxxx] executing command
command finished
** transaction: commit
- executing `deploy:migrate'
- executing "ls -x /var/www/xxxx/releases"
servers: ["xxxx"]
[xxxx] executing command
command finished
- executing "cd /var/www/xxxx/releases/20080805090103; rake RAILS_ENV=production db:migrate"
servers: ["xxxx"]
[xxxx] executing command
*** [err :: xxxx] rake aborted!
*** [err :: xxxx] No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)
*** [err :: xxxx] /usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:2143:in `raw_load_rakefile'
*** [err :: xxxx] (See full trace by running task with --trace)
command finished
it seems like Capistrano is running from the wrong directory, i.e the upper one after extraction. It does not run from the actual application directory
how can i resolve the problem?
Comments and changes to this ticket
-
Jamis Buck August 19th, 2008 @ 09:22 AM
- → Tag changed from to cap:deploy error support-request
- → State changed from new to invalid
This is not the appropriate forum for troubleshooting. Please post questions of this nature to the Capistrano mailing list (http://groups.google.com/group/c.... If it does turn out to be a bug in Capistrano, then it would be appropriate to post here with an explanation of why it is a bug and how to reproduce it (and a patch to fix it, if at all possible). Thanks!
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
