"Exec format error" (Windows)

Rails
1

Hey again :slight_smile:

I have this weird issue on Windows. I’ve installed mongrel_cluster and
friends, and I’m trying to get a cluster up and running. Here’s my
mongrel_cluster.yml:

port: 8000
environment: production
address: 127.0.0.1
pid_file: log/mongrel.pid
servers: 10
cwd: c:/railstest
docroot: public
log_file: log/mongrel.log

I’ve tried different versions, all yield the same result that you can
see in this command prompt dump:

C:\railstest>mongrel_rails cluster::start
Starting 10 Mongrel servers…
c:/ruby/lib/ruby/gems/1.8/gems/mongrel_cluster-0.2.1/lib/mongrel_cluster/init.rb:53:in
``’: Exec format error - mongrel_rails start -d -e production -p 8000
-a 127.0.0.1 -l log/mongrel.log -P log/mongrel.8000.pid -c c:/railstest
-r public (Errno::ENOEXEC)
from
c:/ruby/lib/ruby/gems/1.8/gems/mongrel_cluster-0.2.1/lib/mongrel_cluster/init.rb:53:in
start' from c:/ruby/lib/ruby/gems/1.8/gems/mongrel_cluster-0.2.1/lib/mongrel_cluster/init.rb:31:inupto’
from
c:/ruby/lib/ruby/gems/1.8/gems/mongrel_cluster-0.2.1/lib/mongrel_cluster/init.rb:31:in
start' from c:/ruby/lib/ruby/gems/1.8/gems/mongrel_cluster-0.2.1/lib/mongrel_cluster/init.rb:95:inrun’
from
c:/ruby/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/command.rb:211:in
run' from c:/ruby/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:231 from c:/ruby/bin/mongrel_rails:19:inload’
from c:/ruby/bin/mongrel_rails:19

And here’s the interesting part. If I copy/paste the exec line from the
output above, and execute it, mongrel_rails starts:

C:\railstest>mongrel_rails start -d -e production -p 8000 -a 127.0.0.1
-l log/mongrel.log -P log/mongrel.8000.pid -c c:/railstest -r public
** WARNING: Win32 does not support daemon mode.
** Daemonized, any open files are closed. Look at log/mongrel.8000.pid
and log/mongrel.log for info.
** Starting Mongrel listening at 127.0.0.1:8000
** Starting Rails with production environment…
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready. INT => stop (no restart).
** Mongrel available at 127.0.0.1:8000

So what gives? It seems there’s something flaky about the way the
commands are given to the system by mongrel_cluster? I dunno. Anybody
have any idea?

Thanks in advance,
Daniel :slight_smile: