Link to home
Create AccountLog in
Avatar of dsgray
dsgray

asked on

What is the meaning of the subversion error message "200 OK" and how can it be resolved?

I am trying to deploy a Rails website using Capistrano and Subversion on a shared host.  After I deployed the application from a subversion repository, I received an error message due to an incorrect configuration setting within the files of the application, and I am hoping to deploy a new version of the application that has been submitted to the repository.

When I try to deploy the site another time, I receive the error message below.  Yet, I am able to access the repository through a browser.  Could you tell me what may be the source of the error and how to resolve it?  The error is similar to what is described in the forum at the site below:

http://discussion.dreamhost.com/showflat.pl?Cat=&Board=forum_troubleshooting&Number=91494
[bostoncluster.org] executing command
 ** [bostoncluster.org :: err] svn: PROPFIND request failed on '/bostoncluster/trunk/rails_space'
 ** svn: PROPFIND of '/bostoncluster/trunk/rails_space' : 200 OK (http://bostoncluster.org)
    command finished
*** [deploy:update_code] rolling back

Open in new window

SOLUTION
Avatar of Michel Plungjan
Michel Plungjan
Flag of Denmark image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
I am getting an authentication prompt at
http://bostoncluster.org/bostoncluster/trunk/rails_space

and then I get



    * Phusion Passenger

Ruby on Rails version '1.1.6' not found
The application /mnt/local/home/dsgray/bstncluster/releases/20080806014719 requires Ruby on Rails version 1.1.6, which is not installed. Please install it with the following command:

sudo gem install rails --version 1.1.6

Powered by Phusion Passenger, mod_rails / mod_rack for Apache.
Avatar of dsgray
dsgray

ASKER

Thank you, mplungian.

A main question is why I would be able to access the subversion repository through the browser at http://svn.bostoncluster.org/bostoncluster/ but receive an error when trying to perform a deployment with Capistrano.  Do you know why I may be receiving the PROPFIND error message?  I only started to receive this message after successfully deploying the application once, and I'd like to redeploy to solve the error message you included in the previous post.

David
ASKER CERTIFIED SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Avatar of dsgray

ASKER

I tried to change the :domain setting from bostoncluster.org to svn.bostoncluster.org, but that does not seem to resolve the problem.  The current deploy.rb file is below.  Are there changes you would suggest?  I'm almost sure that the :repository specification has been designated as being in the svn.bostoncluster.org domain.

Thank you,

David
#############################################################
## General
#############################################################
set :application, "bostoncluster"
 
 
#############################################################
## Servers 
#############################################################
 
set :use_sudo, false    # Dreamhost does not support sudo
set :user, "user"  # Dreamhost SSH User
set :password, "password"
set :domain, "svn.bostoncluster.org"
set :rails_env, "production"
set :group_writable, false
 
role :app, domain
role :web, domain
role :db, domain, :primary => true
 
 
#############################################################
## Subversion
#############################################################
 
 
# keeps a local checkout of the repository on the server to get faster deployments
 
set :scm, :subversion
set :scm_user, "user"   # Sets 'my_svn_user' instead, if you are using different name than your app.
set :scm_auth_cache, true  # Prompts for password once
set :scm_password, Proc.new { Capistrano::CLI.password_prompt("SCM password for #{scm_user}:") }
set :repository,  "http://svn.bostoncluster.org/bostoncluster/trunk"
set :deploy_to, "/home/#{user}/bstncluster"
# keeps a local checkout of the repository on the server to get faster deployments
set :deploy_via, :remote_cache
 
 
 
#############################################################
## Tasks
#############################################################
 
namespace :deploy do
  desc "Restart Application (using tmp/restart.txt)"
  task :restart_passenger do
    run "touch #{current_path}/tmp/restart.txt"
  end
 
  desc "Restarts your application."
  task :restart do
    restart_passenger
  end
 
  desc "Link shared files"
  #task :before_symlink do
  before :symlink do
    run "rm -drf #{release_path}/public/uploads"
    run "ln -s #{shared_path}/uploads #{release_path}/public/uploads"
    run "rm -f #{release_path}/config/database.yml"
    run "ln -s #{shared_path}/database.yml #{release_path}/config/database.yml"
  end
end

Open in new window

Avatar of dsgray

ASKER

I believe the source of the error is the line "set :deploy_via, :remote_cache".  I removed the setting and was able to deploy.  Perhaps the line resulted in setting the repository location as being in the bostoncluster.org domain, instead of the svn.bostoncluster.org domain, where the repository was located when the first successful deployment occurred?

Thank you, hoboslobo and mplungjan.