Fresh install on Debian Etch - Mongrel immediately hangs

Hi,

I just did a clean install of

Ruby 1.8.5
Rubygems 0.9.0

and the Mongrel and Mongrel_Cluster gems.

I used only the Debian Etch package manager, nothing compiled myself.

Now, on a testapp when I do a script/server, I get the:

** Ruby version is not up-to-date; loading cgi_multipart_eof_fix

warning. But it’s not serving my app. Ruby is immediately on 100% CPU
load (and 0.7% memory) and stays there.

When I press CTRL-C on the console I started the server from, I get

=> Booting Mongrel (use ‘script/server webrick’ to force WEBrick)
=> Rails application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server

but still, nothing is served and Ruby process at 100% CPU.

Trying to do a mongrel_rails -B to debug it produces no debug log. The
hang is very immediate.

Nothing in any logs.

Please help me!

I had the same error a few days ago. Installing ruby 1.8.6 (from source)
fixed my problem. However: You may need to install gem
cgi_multipart_eof_fix

bye
rubyphunk

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

did you tried to use mongrel from backports.org (1)? Mongrel Debian
package
removes this fix because Debian’s ruby already has this included.
Just add backports.org entry to your /etc/apt/sources.list file:
deb http://www.backports.org/debian etch-backports main contrib non-free

And apt-get into it :smiley:

  1. Debian -- Error

Cheers,

filipe {
@ icewall.org
GPG 1024D/A6BA423E
Jabber [email protected]
}
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD4DBQFHRxLXmKFbPqa6Qj4RAn4OAJdRj6JPaPb1BPnX2vGH2EuRJCQ9AJ93TXLz
up/4syuaSEeXGNHDYilJSg==
=0ykp
-----END PGP SIGNATURE-----

On Dec 17, 2007 6:15 AM, Paolo C. [email protected] wrote:
[…]

I’ve found that mongrel tries to require some library repeatedly,
because it gets an unrelated exception while trying to load it. For me,
the missing library was actually fastthread, and installing it solved
the problem.
To find out what is the actual error, add a print statement after line 8
in lib/mongrel/gems.rb.

Hope that helps,

Paolo, you can confirm this behavior happens also with “mongrel_rails”
and not just script/server?


Luis L.
Multimedia systems

A common mistake that people make when trying to design
something completely foolproof is to underestimate
the ingenuity of complete fools.
Douglas Adams

Luis L. wrote:

On Dec 17, 2007 6:15 AM, Paolo C. [email protected] wrote:
[…]

I’ve found that mongrel tries to require some library repeatedly,
because it gets an unrelated exception while trying to load it. For me,
the missing library was actually fastthread, and installing it solved
the problem.
To find out what is the actual error, add a print statement after line 8
in lib/mongrel/gems.rb.

Hope that helps,

Paolo, you can confirm this behavior happens also with “mongrel_rails”
and not just script/server?

Yes, it did happen. After installing fastthread, I can’t reproduce it
anymore if I uninstall it. mongrel_rails now exits with a clean
backtrace when started without fastthread installed, and script/server
runs webrick instead.
I don’t know what exactly was causing the problem… maybe a wrong
installed version of fastthread? The exception caught in
lib/mongrel/gems.rb:8 was:
‘no such file to load – fastthread’ - sorry, I didn’t save the
backtrace.

Paolo C.

I just had the same exact problem with the same solution. The wrong
platform
of fastthread was installed, which was causing mongrel to spin. That
should
probably dump with a stacktrace instead of spinning, I’ll see if I can
learn
enough mongrel to write a patch.

Emmett

On Mon, Dec 17, 2007 at 2:43 AM, Paolo C. [email protected]

Benny Beesnus wrote:

Hi,

I just did a clean install of

Ruby 1.8.5
Rubygems 0.9.0

and the Mongrel and Mongrel_Cluster gems.

I used only the Debian Etch package manager, nothing compiled myself.

Now, on a testapp when I do a script/server, I get the:

** Ruby version is not up-to-date; loading cgi_multipart_eof_fix

warning. But it’s not serving my app. Ruby is immediately on 100% CPU
load (and 0.7% memory) and stays there.

When I press CTRL-C on the console I started the server from, I get

=> Booting Mongrel (use ‘script/server webrick’ to force WEBrick)
=> Rails application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server

but still, nothing is served and Ruby process at 100% CPU.

Trying to do a mongrel_rails -B to debug it produces no debug log. The
hang is very immediate.

I’ve found that mongrel tries to require some library repeatedly,
because it gets an unrelated exception while trying to load it. For me,
the missing library was actually fastthread, and installing it solved
the problem.
To find out what is the actual error, add a print statement after line 8
in lib/mongrel/gems.rb.

Hope that helps,

Paolo C.