I’m playing with the mongrel clustering, and am having a problem getting
mongrels to start up reliably.
This should be a pretty simple cluster, with just 2 instances running.
mongrel config (mongrel_cluster.yml) looks like:
When I start up the pack with the command:
mongrel_rails cluster::start -C
I see (with a quick ps) two mongrels, one of which then dies with the
error in the log file:
** Daemonized, any open files are closed. Look at
and log/mongrel.8000.log for info.
** Starting Mongrel listening at 127.0.0.1:8000
** Starting Rails with production environment…
deployment/installed/ruby/lib/ruby/1.8/fileutils.rb:243:in `mkdir’: File
fu_mkdir' from /deployment/installed/ruby/lib/ruby/1.8/fileutils.rb:172:inmkdir’
each' from /deployment/installed/ruby/lib/ruby/1.8/fileutils.rb:171:inmkdir’
evaluate_init_rb' from /deployment/installed/ruby/lib/ruby/gems/1.8/gems/activesupport-2.0.2/lib/active_support/core_ext/kernel/reporting.rb:11:insilence_warnings’
... 21 levels... from
run' from /deployment/installed/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.3 /bin/mongrel_rails:281 from /deployment/installed/ruby/bin/mongrel_rails:19:inload’
It looks to me as if both mongrels are starting up, but the deployment
the “bundled_resource” from each mongrel is ending up with the app
I’ve not found any indication of a similar problem searching the net, or
forums (or the bug tracker).
Has anybody else seen similar behavior? Is there a workaround
BTW: my currently isntalled gems include:
bash-2.05b$ gem list
*** LOCAL GEMS ***