I posted this to the rails list before by mistake, and only later realized that there is a specific mongrel list. Uff, I got lost. I had mongrel_cluster 0.1working fine, even with capistrano (my own hack). Then came mongrel_cluster 0.1.1 and I tried to set it up, but somehow I messed up things and nothing worked anymore. So here is what I did: on production machine: (debian linux, rails 1.1) ------------------------------ - installing mongrel_cluster 0.1.1 on development machine**: (windows XP, raills 1.1) ----------------------------------------------------------------------- - inststalling mongrel_cluster 0.1.1 - recreating config file: mongrel_rails cluster::configure - modifying configfile manually to make it look like this: (will be more the one server later) --- num-procs: 1024 docroot: public timeout: 120 cwd: /home/me/sites/myapp/current log_file: log/mongrel.log port: 3000 config_script: debug: false environment: production servers: 1 pid_file: log/mongrel.pid address: 0.0.0.0 mime_map: - deploy.rb: commented out my old restart and spinner tasks and added: require ''mongrel_cluster/recipes'' - deployment: rake deploy (fails because config file is at: /home/me/sites/myapp/current/config/mongrel_cluster.yml) ... executing "mongrel_rails cluster::restart -C /home/me/sites/myapp/config/mongrel_cluster.yml" ... then I thought I could give "cap -a configure_mongrel_cluster" a try, hoping it would put things into the right order, but I got this: ** [out :: xx.xx.xx.xx] !!! Path to log file not valid: log/mongrel.log ** [out :: xx.xx.xx.xx] cluster::configure reported an error. Use -h to get help. So what is wrong with the way I approached capistrano mongrel_cluster ? regards -- Roberto Saccon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060504/b8cdbcb6/attachment.htm
Hi Robert:> > then I thought I could give "cap -a configure_mongrel_cluster" a > try, hoping it would put things into the right order, but I got this: > > ** [out :: xx.xx.xx.xx] !!! Path to log file not valid: log/ > mongrel.log > ** [out :: xx.xx.xx.xx] cluster::configure reported an error. Use - > h to get help.This was a problem with 0.1, but should be resolved in 0.1.1. I changed cluster::configure to not validate log paths. Double check the version with " gem list mongrel_cluster" please. Thanks, Bradley ------ Rails Machine Simplified Ruby on Rails application deployment http://railsmachine.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060504/05b27404/attachment.htm
ok, I uninstalled 0.1 to make absolutely sure that 0.1.1 is running and did all configuration steps again and now it even got worse: after deploying the "current" symlink points to a nonexistent "config". Bradley, can you show a simple, but working example of what needs to be configured at the develpment machine and what needs to be done at the production machine (if anything at all) ? Then I hopefullyI can figure out what I am doing wrong. On 5/4/06, bradley taylor <bradley at railsmachine.com> wrote:> > Hi Robert: > > > then I thought I could give "cap -a configure_mongrel_cluster" a try, > hoping it would put things into the right order, but I got this: > > ** [out :: xx.xx.xx.xx] !!! Path to log file not valid: log/mongrel.log > ** [out :: xx.xx.xx.xx] cluster::configure reported an error. Use -h to > get help. > > > This was a problem with 0.1, but should be resolved in 0.1.1. > > I changed cluster::configure to not validate log paths. Double check the > version with " gem list mongrel_cluster" please. > > Thanks, > Bradley > > ------ > Rails Machine > Simplified Ruby on Rails application deployment > http://railsmachine.com > > > > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > >-- Roberto Saccon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060505/cc66630e/attachment.htm
Hi Roberto:> > Bradley, can you show a simple, but working example of what needs > to be configured at the develpment machine and what needs to be > done at the production machine (if anything at all) ? Then I > hopefullyI can figure out what I am doing wrong.***deploy.rb*** require ''mongrel_cluster/recipes'' role :web, "10.0.1.5" role :app, "10.0.1.5" role :db, "10.0.1.5", :primary => true set :application, "animal_shelter" set :deploy_to, "/var/apps/#{application}" # /var/apps/ is owned by deploy set :user, "deploy" set :repository, "your_repository_here" set :use_sudo, false *** server *** No configuration needed. *** dev machine *** First deployment: cap -a setup cap -a configure_mongrel_cluster cap -a cold_deploy Subsequent deployments: svn commit -m "more software" cap -a deploy> ok, I uninstalled 0.1 to make absolutely sure that 0.1.1 is running > and did all configuration steps again and now it even got worse: > after deploying the "current" symlink points to a nonexistent > "config". >By default the config file is written to deploy_to/config. It looks like your deploy_to variable contains "current" as configure_mongrel_cluster writes to deploy_to/config/ mongrel_cluster.yml. deploy_to should be the root directory of your deployment. Feel free to send me a censored version of your deploy.rb and I''ll talk a look for anything unusual. Thanks, Bradley ------ Rails Machine Simplified Ruby on Rails application deployment http://railsmachine.com
Bradley, thanks for the example. A new day and a new look at my code relvealed that I was using deploy_to before setting it... works like a charm now .. On 5/5/06, bradley taylor <bradley at railsmachine.com> wrote:> > Hi Roberto: > > > > > Bradley, can you show a simple, but working example of what needs > > to be configured at the develpment machine and what needs to be > > done at the production machine (if anything at all) ? Then I > > hopefullyI can figure out what I am doing wrong. > > ***deploy.rb*** > > require ''mongrel_cluster/recipes'' > > role :web, "10.0.1.5" > role :app, "10.0.1.5" > role :db, "10.0.1.5", :primary => true > > set :application, "animal_shelter" > > set :deploy_to, "/var/apps/#{application}" # /var/apps/ is owned by > deploy > set :user, "deploy" > set :repository, "your_repository_here" > set :use_sudo, false > > *** server *** > No configuration needed. > > *** dev machine *** > First deployment: > cap -a setup > cap -a configure_mongrel_cluster > cap -a cold_deploy > > Subsequent deployments: > svn commit -m "more software" > cap -a deploy > > > > ok, I uninstalled 0.1 to make absolutely sure that 0.1.1 is running > > and did all configuration steps again and now it even got worse: > > after deploying the "current" symlink points to a nonexistent > > "config". > > > > By default the config file is written to deploy_to/config. It looks > like your deploy_to variable contains "current" as > configure_mongrel_cluster writes to deploy_to/config/ > mongrel_cluster.yml. deploy_to should be the root directory of your > deployment. > > Feel free to send me a censored version of your deploy.rb and I''ll > talk a look for anything unusual. > > Thanks, > Bradley > > ------ > Rails Machine > Simplified Ruby on Rails application deployment > http://railsmachine.com > > > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >-- Roberto Saccon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060505/fb2311ed/attachment.htm