# "Exec format error" (Windows)

**URL:** <https://www.ruby-forum.com/t/exec-format-error-windows/77495>\
**Category:** Rails\
**Created:** [November 28, 2006, 1:10pm UTC](https://www.ruby-forum.com/t/exec-format-error-windows/77495 "2006-11-28T13:10:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\
**Post date:** [November 28, 2006, 1:10pm UTC](https://www.ruby-forum.com/t/exec-format-error-windows/77495/1 "2006-11-28T13:10:47Z")

</div>

Hey again 🙂

## 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:in`upto’ 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:in`run’ 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:in`load’ 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 🙂