Looks like the problem is this:

   ssh: connect to host 192.168.1.151 port 22: Operation timed out

Also, note that rake integration is deprecated, and is entirely gone  
in cap2. You should be using 'cap' directly, rather than via rake.

- Jamis

On Jun 13, 2007, at 2:21 PM, charlie caroff wrote:

>
>> Where is deploy.rb located? What directory are you in when you run
>> "cap setup"?
>
> Sorry -- didn't see your message until after I posted.
>
> I seem to be getting through most of rake deploy now.  The script
> seems to be connecting to my server, and trying to move my working
> copy to it -- but it fails at the end:
>
> rake deploy --trace
> (in /usr/home/charlie/project/trunk)
> ** 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...
>   * executing "if [[ ! -d /u/apps/project/releases/20070613201720 ]];
> then\n              svn co --no-auth-cache   -q -r3 svn+ssh://
> 192.168.1.151/usr/home/svn/repository/project /u/apps/project/ 
> releases/
> 20070613201720 &&\n              (test -e /u/apps/project/
> revisions.log || (touch /u/apps/project/revisions.log && chmod 666 /u/
> apps/project/revisions.log)) && echo `date +\"%Y-%m-%d %H:%M:%S\"`
> $USER 3 20070613201720 >> /u/apps/project/revisions.log;\n
> fi"
>     servers: ["www.project.com"]
>     [www.project.com] executing command
>  ** [out :: www.project.com] ssh: connect to host 192.168.1.151 port
> 22: Operation timed out
>  ** [out :: www.project.com] svn: Connection closed unexpectedly
>     command finished
> *** [update_code] transaction: rollback
>   * [update_code] rolling back
>   * executing "rm -rf /u/apps/project/releases/20070613201720"
>     servers: ["www.project.com"]
>     [www.project.com] executing command
>     command finished
> command "if [[ ! -d /u/apps/project/releases/20070613201720 ]]; then\\
> \n              svn co --no-auth-cache   -q -r3 svn+ssh://
> 192.168.1.151/usr/home/svn/repository/project /u/apps/project/ 
> releases/
> 20070613201720 &&\\\n              (test -e /u/apps/project/
> revisions.log || (touch /u/apps/project/revisions.log && chmod 666 /u/
> apps/project/revisions.log)) && echo `date +\"%Y-%m-%d %H:%M:%S\"`
> $USER 3 20070613201720 >> /u/apps/project/revisions.log;\\
> \n            fi" failed on www.project.com
>
>
> Charlie
>
>>
>> - Jamis
>>
>> On Jun 13, 2007, at 12:07 PM, charlie caroff wrote:
>>
>>
>>
>>> Hi,
>>
>>> I am struggling with understanding how deploy.rb works.  I'm  
>>> using svn
>>> +ssh.  I'm running capistrano 1.4.1 for FreeBSD ports.  I'm not  
>>> using
>>> a web server.
>>
>>> I get this error when I try to run cap setup:
>>
>>> /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.4.1/lib/capistrano/
>>> actor.rb:545:in `execute_on_servers': The setup task is only run for
>>> servers matching {:desc=>"Set up the expected application directory
>>> structure on all boxes", :except=>{:no_release=>true}}, but no  
>>> servers
>>> matched (RuntimeError)
>>
>>> My repository is on my local machine, at /home/svn/repository
>>
>>> My project is called "project", and is at /home/charlie/project/ 
>>> trunk
>>
>>> My remote server is atwww.project.com, and on that machine, is  
>>> stored
>>> at /home/charlie/project
>>
>>> Here are my lines from deploy.rb:
>>
>>> set :application, "project"
>>> set :repository, "svn+ssh//192.168.1.151/home/svn/repository/ 
>>> project/"
>>
>>> role :web, "www.project.com"
>>> role :app, "www.project.com"
>>> role :db,  "www.project.com", :primary => true
>>
>>> I'd really appreciate a point in the right direction.
>>
>>> Charlie
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to