Oops. I had other problems that needed fixing first. I was missing the
net-ssh gem from the gem install net-ssh on all the poroduction servers.
So now I just have a problem getting the migration to work. I'm still
troubleshooting that myself but just in case here's my command and my error:
> cap production1 migrate
returns:
* executing task production1
* executing task migrate
* executing "cd /website/bankspower/current && rake RAILS_ENV=production
db:migrate"
servers: ["172.x.x.x"]
Password: ***
[172.x.x.x] executing command
** [out :: 172.x.x.x] (in /website/bankspower/releases/20070405175714)
** [out :: 172.x.x.x]
/website/bankspower/releases/20070405175714/config/boot
.rb:29:Warning: require_gem is obsolete. Use gem instead.
** [out :: 172.x.x.x] rake aborted!
** [out :: 172.x.x.x] Mysql::Error: Table
'bankspower_production.schema_info'
doesn't exist: SELECT version FROM schema_info
** [out :: 172.x.x.x]
** [out :: 172.x.x.x] (See full trace by running task with --trace)
command finished
command "cd /website/bankspower/current && rake RAILS_ENV=production
db:migrate
" failed on 172.x.x.x
Anyway, still working on it.
Thanks,
Raul
----- Original Message -----
From: "Raul" <[EMAIL PROTECTED]>
To: <>
Sent: Thursday, April 05, 2007 8:36 AM
Subject: Capistrano problem deploying to production database only server
> Hi all. I have a Capistrano recipe that is deploying great to my test
> server and 3 production servers. On the test server I have mySQL and
> Rails running together. Deploy_with_migrations works great on this
> machine. My produciton servers are Rails app only and I have a dedicated
> mySQL server. Deploy works great without a :db value but if I add the :db
> to the list then the deployment chokles while trying to write the app
> files to that server. I didn't even have ruby on rails installed on that
> machine. So I tried to create a new task with only the :db value and run
> that task with a simple migrate just to get my database tables in place
> (the database itself is already created) and it still chokes. Task "test"
> works like a dream, "production1" fails, "production2" and "production3 "
> work. I had all the production machines in one task at first as :web,
> :web2 and :web3 but it didn't seem to like that. In any case, seperating
> them confirmed that access and connectivity are working. Here's my
> capistrano recipe, which can probably use a ton of improvement anyway:
>
> require "mongrel_cluster/recipes"
>
>
> set :application, "bankspower"
>
> set :repository, "svn://172.16.1.23:48000/#{application}/trunk"
>
> set :deploy_to, "/website/#{application}"
>
> set :mongrel_conf, "#{current_path}/config/mongrel_cluster.yml"
>
> set :user, "rrubio"
>
> set :checkout, "export"
>
> set :keep_releases, "3"
>
>
>
> task :test do
>
>
> set :rails_env, :test
>
>
>
>
> role :web, "172.16.1.23"
>
> role :app, "172.16.1.23"
>
> role :db, "172.16.1.23", :primary => true
>
> end
>
>
>
> task :production1 do
>
> set :rails_env, :production
>
> set :mongrel_conf, "#{current_path}/config/production/mongrel_cluster.yml"
>
> role :web, "192.168.168.31"
>
> role :app, "192.168.168.31"
>
> role :db, "172.16.1.30" , :primary => true
>
>
>
>
> end
>
>
>
> task :production3 do
>
> set :rails_env, :production
>
> set :mongrel_conf, "#{current_path}/config/production/mongrel_cluster.yml"
>
> role :web, "192.168.168.33"
>
> role :app, "192.168.168.33"
>
> end
>
>
> task :production_db, :roles => :db do
>
> set :rails_env, :production
>
>
>
> role :db, "172.16.1.30", :primary => true
>
> end
>
>
>
> Thanks for any assistance!
>
> Raul
>
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Deploying Rails" group.
To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---
