I used bundled resources sometimes ago and I have same problem (I think).
I read init.rb and I commented lines 54..57 (create bundle directory and
copy resources).
Regards!
John Woodward escribió:
I'm playing with the mongrel clustering, and am having a problem
getting 2 mongrels to start up reliably.
This should be a pretty simple cluster, with just 2 instances running.
My mongrel config (mongrel_cluster.yml) looks like:
cwd: /deployment/installed/myapp/current
log_file: log/mongrel.log
port: "8000"
environment: production
address: 127.0.0.1 <http://127.0.0.1>
pid_file: tmp/pids/mongrel.pid
servers: 2
When I start up the pack with the command:
mongrel_rails cluster::start -C
/deployment/installed/myapp/current/config/mongrel_cluster.yml
I see (with a quick ps) two mongrels, one of which then dies with the
follow error in the log file:
** Daemonized, any open files are closed. Look at
tmp/pids/mongrel.8000.pid and log/mongrel.8000.log for info.
** Starting Mongrel listening at 127.0.0.1:8000 <http://127.0.0.1:8000>
** Starting Rails with production environment...
deployment/installed/ruby/lib/ruby/1.8/fileutils.rb:243:in `mkdir':
File exists -
/deployment/installed/myapp/releases/20080130211150/public/bundles
(Errno::EEXIST)
from
/deployment/installed/ruby/lib/ruby/1.8/fileutils.rb:243:in `fu_mkdir'
from
/deployment/installed/ruby/lib/ruby/1.8/fileutils.rb:172:in `mkdir'
from
/deployment/installed/ruby/lib/ruby/1.8/fileutils.rb:171:in `each'
from
/deployment/installed/ruby/lib/ruby/1.8/fileutils.rb:171:in `mkdir'
from
/deployment/installed/myapp/releases/20080130211150/vendor/plugins/bundled_resource-0.9/lib/bundled_resource.rb:38:in
`create_public_bundle_directory'
from
/deployment/installed/myapp//releases/20080130211150/vendor/plugins/bundled_resource-0.9/init.rb:57:in
`evaluate_init_rb'
from
deployment/installed/ruby/lib/ruby/gems/1.8/gems/rails-2.0.2/lib/rails/plugin.rb:79:in
`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:in
`silence_warnings'
... 21 levels...
from
/deployment/installed/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel/command.rb:212:in
`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:in `load'
from /deployment/installed/ruby/bin/mongrel_rails:19
It looks to me as if both mongrels are starting up, but the deployment
of the "bundled_resource" from each mongrel is ending up with the app
stomping on itself.
I've not found any indication of a similar problem searching the net,
or the forums (or the bug tracker).
Has anybody else seen similar behavior? Is there a workaround available?
Thanks!
john
BTW: my currently isntalled gems include:
bash-2.05b$ gem list
*** LOCAL GEMS ***
actionmailer (2.0.2)
actionpack (2.0.2)
activerecord (2.0.2)
activeresource (2.0.2)
activesupport (2.0.2)
capistrano (2.1.0)
cgi_multipart_eof_fix (2.5.0)
daemons (1.0.9)
fastthread (1.0.1)
gem_plugin (0.2.3)
highline (1.4.0)
mongrel (1.1.3)
mongrel_cluster (1.0.5)
needle (1.3.0)
net-sftp (1.1.0)
net-ssh (1.1.2)
rails (2.0.2)
rake (0.8.1)
------------------------------------------------------------------------
_______________________________________________
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
--
Rafael Garcia Ortega
begin:vcard
fn;quoted-printable:Rafael Garc=C3=ADa Ortega
n;quoted-printable:Garc=C3=ADa Ortega;Rafael
org:ASPgems S.L.
email;internet:[EMAIL PROTECTED]
tel;work:692686533
x-mozilla-html:FALSE
url:http://www.aspgems.com
version:2.1
end:vcard
_______________________________________________
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
