Some random points from another Capistrano novice: 0. It sounds like your svn call fails because it can't name resolve the repository 1. validate your name resolution forward and reverse: nslookup `hostname` nslookup $MY_IP_ADDRESS nslookup www.xxxx.com nslookup mysql.xxxxx.com
2. Are you mixing Mac OS X and Linux? I had some problems with name resolution of .local suffixes that were cured by prepending .local to the start of my DNS search path 3. I've found that an effective way to diagnose cap stuff is to use virtual machines for my remote hosts (both Parallels and MS Virtual Server) Peter On Mar 22, 2007, at 4:01 PM, Kev wrote: > > Ok, I've removed all prefixes from my application so it should not > matter whether it is www.xxxxx.com or mysql.xxxxx.com . I've tried > running the cap migrate as rake deploy, as that allows me to --trace. > > Here's the trace output - it's a little more helpful than before, but > I can't make sense of it at all : ( > > /Users/Kev/Rails/svn/mint/config/boot.rb:29:Warning: require_gem is > obsolete. Use gem instead. > ** Invoke deploy (first_time) > ** Invoke remote:deploy (first_time) > ** Execute remote:deploy > Capistrano/Rake integration is deprecated. > Please invoke the 'cap' command directly: `cap deploy' > * executing task deploy > * executing task update > ** transaction: start > * executing task update_code > * querying latest revision... > ssh: home: No address associated with nodename > svn: Connection closed unexpectedly > *** [update_code] transaction: rollback > * [update_code] rolling back > * executing "rm -rf /home/xxxxxx/mint/releases/20070322195055" > servers: ["www.xxxxxx.com"] > Password: > [www.xxxxxx.com] executing command > command finished > rake aborted! > Could not determine latest revision > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/scm/ > subversion.rb:24:in `latest_revision' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > configuration.rb:62:in `initialize' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > configuration.rb:88:in `call' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > configuration.rb:88:in `[]' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > configuration.rb:235:in `method_missing' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/scm/ > subversion.rb:63:in `checkout' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > recipes/standard.rb:80:in `load' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > actor.rb:159:in `instance_eval' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > actor.rb:159:in `update_code' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > recipes/standard.rb:145:in `load' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > actor.rb:430:in `transaction' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > recipes/standard.rb:144:in `load' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > actor.rb:159:in `instance_eval' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > actor.rb:159:in `update' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > recipes/standard.rb:178:in `load' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > actor.rb:159:in `instance_eval' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > actor.rb:159:in `deploy' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > cli.rb:268:in `send' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > cli.rb:268:in `execute_recipes!' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > cli.rb:268:in `each' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > cli.rb:268:in `execute_recipes!' > /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/capistrano/ > cli.rb:239:in `execute!' > /Users/Kev/Rails/svn/mint/config/../lib/tasks/capistrano.rake:18:in > `cap' > /Users/Kev/Rails/svn/mint/config/../lib/tasks/capistrano.rake:29 > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:399:in `call' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:399:in > `execute' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:399:in `each' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:399:in > `execute' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:369:in > `invoke' > /usr/local/lib/ruby/1.8/thread.rb:135:in `synchronize' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:362:in > `invoke' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:376:in > `invoke_prerequisites' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:1021:in > `each' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:1021:in > `send' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:1021:in > `each' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:375:in > `invoke_prerequisites' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:368:in > `invoke' > /usr/local/lib/ruby/1.8/thread.rb:135:in `synchronize' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:362:in > `invoke' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:1935:in `run' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:1935:in > `each' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/lib/rake.rb:1935:in `run' > /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.2/bin/rake:7 > /usr/local/bin/rake:16:in `load' > /usr/local/bin/rake:16 > > God damn it's so nearly there!!! Is "ssh: home: No address associated > with nodename " the problem? > > Kev > > On Mar 22, 4:57 pm, "Kev" <[EMAIL PROTECTED]> wrote: >> Hmmm and I've just noticed - my sql database is on the dreamhost >> server at mysql.xxxxxxxxx.com - could this be causing a problem? >> >> On Mar 22, 4:08 pm, "Kev" <[EMAIL PROTECTED]> wrote: >> >>> Thanks for the help so far! I've managed to get everything up on >>> mydreamhostsvn (there must have been a problem with my router at >>> home, >>> as I'm on another wireless point and have uploaded fine using the >>> nuby >>> on rails tips ... >> >>> Keith - I didn't know that the svn repository needed to be the same >>> name as the original name you generated the rails app with? I've >>> changed my deploy.rb as follows >> >>> set :user, 'xxxxxxxxx' >>> set :application, "www.xxxxxx.com" >>> #set :repository, "file:///home/#{user}/svn/#{application}" >>> # NOTE: If file:/// doesn't work for you, try this: >>> set :repository, "svn+ssh://home/#{user}/svn/mint" >> >>> role :web, application >>> role :app, application >>> role :db, application, :primary => true >> >>> set :deploy_to, "/home/#{user}/mint" >>> # set :svn, "/path/to/svn" # defaults to searching the PATH >>> set :use_sudo, false >> >>> desc "Restart the FCGI processes on the app server as a regular >>> user." >>> task :restart, :roles => :app do >>> run "#{current_path}/script/process/reaper -- >>> dispatcher=dispatch.fcgi" >>> end >> >>> Although I have kept the application name the same, I've changed the >>> deploy_to location to match the original name of the rails app, but >>> when the web/app/db roles are set to the name of the rails app I >>> get a >>> cannot connect error. >> >>> I've renamed the application location on the server to match the >>> original name of the rails app ("mint") and now the ... do I need to >>> create thesymlinkmyself? My current error when running cap migrate >>> is >> >>> * executing task migrate >>> * executing "cd /home/xxxxxx/mint/current && rake >>> RAILS_ENV=production db:migrate" >>> servers: ["www.xxxxxxxx.com"] >>> Password: >>> [www.xxxxxx.com] executing command >>> ** [out ::www.xxxxxxx.com] bash: line 1: cd: /home/xxxxxxxx/mint/ >>> current: No such file or directory >>> command finished >>> command "cd /home/xxxxxxx/mint/current && rake RAILS_ENV=production >>> db:migrate" failed onwww.xxxxxxxx.com >> >>> It just seems like thesymlinkisn't playing nice! >> >>> Jamis - Thanks for the help here, on top of how much help I've >>> already >>> received from your excellent blog! >> >>> On Mar 22, 2:32 pm, Jamis Buck <[EMAIL PROTECTED]> wrote: >> >>>> Kev, >> >>>> Note that, unless you are using a third-party Capistrano extension, >>>> Capistrano 1.4.1 and earlier do not support local svn repositories. >>>> The repository must be accessible by both the local host, and the >>>> remote host. If you need to deploy from a local repository, or (in >>>> general) a repository that the remote host cannot access, you might >>>> want to check out the custom subversion module that wolfmanjm has >>>> written for Capistrano. You should be able to search this group to >>>> find references to it. >> >>>> - Jamis >> >>>> On Mar 22, 2007, at 5:12 AM, Kev wrote: >> >>>>> Trying to deploy my first rails app todreamhostusing subversion >>>>> and >>>>> capistrano and I'm having a nightmare! >> >>>>> I've been using bothhttp://wiki.dreamhost.com/index.php/Capistrano >>>>> andhttp://nubyonrails.topfunky.com/pages/shovel_dreamhosttowalkme >>>>> through, but every single step has been a horrible obstacle. >> >>>>> I've created a svn repository locally (as it kept hanging when >>>>> trying >>>>> to create it online) and checked it out locally. I'm now >>>>> working from >>>>> that directory, and my deploy.rb looks like this >> >>>>> set :user, 'xxxxxxx' >>>>> set :application, "www.xxxxxxx.com" >> >>>>> set :repository, "file:///Users/Kev/Rails/svn/#{application}" >>>>> # NOTE: If file:/// doesn't work for you, try this: >>>>> #set :repository, "svn+ssh://home/#{user}/svn/mint" >> >>>>> role :web, application >>>>> role :app, application >>>>> role :db, application, :primary => true >> >>>>> set :deploy_to, "/home/#{user}/#{application}" >>>>> # set :svn, "/path/to/svn" # defaults to searching the >>>>> PATH >>>>> set :use_sudo, false >> >>>>> desc "Restart the FCGI processes on the app server as a regular >>>>> user." >>>>> task :restart, :roles => :app do >>>>> run "#{current_path}/script/process/reaper -- >>>>> dispatcher=dispatch.fcgi" >>>>> end >> >>>>> desc "Remove the 'current' thatdreamhostleaves lying around" >>>>> #this >>>>> is here after everything else had failed >>>>> task :after_setup do >>>>> delete "#{current_path}", :recursive => true >>>>> end >> >>>>> I can do cap setup fine, but then when I go to do cap deploy I >>>>> get the >>>>> following error >> >>>>> [www.xxxxxxx.com] executing command >>>>> ** [out ::www.xxxxxxx.com] bash: line 1: cd: /home/xxxxxx/ >>>>> www.xxxxxx.com/current:Nosuchfile or directory >>>>> command finished >>>>> command "cd /home/xxxxxx/www.xxxxxx.com/current&&rake >>>>> RAILS_ENV=production db:migrate" failed onwww.xxxxxx.com >> >>>>> It seems as if thesymlinkis not being created ... At what stage >>>>> does >>>>> capistrano create the symbolic link? At setup or migrate? >>>>> Because it's >>>>> doing neither for me and when I try to run capsymlinkI get >> >>>>> Password: >>>>> [www.xxxxxxx.com] executing command >>>>> command finished >>>>> /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/lib/ >>>>> capistrano/ >>>>> configuration.rb:226:in `join': can't convert nil into String >>>>> (TypeError) >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> lib/ >>>>> capistrano/configuration.rb:226:in `release_path' >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> lib/ >>>>> capistrano/actor.rb:560:in `send' >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> lib/ >>>>> capistrano/actor.rb:560:in `method_missing' >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> lib/ >>>>> capistrano/actor.rb:411:in `current_release' >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> lib/ >>>>> capistrano/recipes/standard.rb:128:in `load' >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> lib/ >>>>> capistrano/actor.rb:159:in `instance_eval' >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> lib/ >>>>> capistrano/actor.rb:159:in `symlink' >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> lib/ >>>>> capistrano/cli.rb:268:in `send' >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> lib/ >>>>> capistrano/cli.rb:268:in `execute_recipes!' >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> lib/ >>>>> capistrano/cli.rb:268:in `each' >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> lib/ >>>>> capistrano/cli.rb:268:in `execute_recipes!' >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> lib/ >>>>> capistrano/cli.rb:239:in `execute!' >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> lib/ >>>>> capistrano/cli.rb:12:in `execute!' >>>>> from /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.0/ >>>>> bin/ >>>>> cap:11 >>>>> from /usr/local/bin/cap:18:in `load' >>>>> from /usr/local/bin/cap:18 >> >>>>> Could this be the root of the problem? I've already tried >>>>> leaving the >>>>> after_setup task from deploy, in fact that was only added after >>>>> I'd >>>>> spent a day trying to get it to work unsuccessfully. Any help is >>>>> greatly appreciated! > > > > Peter Booth [EMAIL PROTECTED] 917 445 5663 --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---