Weird error - stream closed

Hi all,

few days ago mongrel start crashing on one of my sites, i upgraded to
latest version (1.0.1) but problem still exists.

When i try to load page in browser random elements are missing or page
is blank (empty html). In mongrel.log i’m getting:

Mon Oct 22 01:10:47 +0200 2007: ERROR: stream closed
Mon Oct 22 01:10:47 +0200 2007: ERROR: closed stream
Mon Oct 22 01:10:47 +0200 2007: ERROR: stream closed
Error sending file /usr/local/www/ibn/public/javascripts/dragdrop.js:
closed stream

and most interesting one:
!!! UNHANDLED EXCEPTION! Invalid argument. TELL ZED HE’S A MORON.

any ideas what is causing that ?

Thanks and best regards,
Bostjan

Hi,

i upgraded to mongrel 1.0.2 and it doesn’t start. I run it like:
mongrel_rails start -B
** Starting Mongrel listening at :3000
** Installing debugging prefixed filters. Look in log/mongrel_debug for
the files.
** Starting Rails with development environment…

it creates files in debug dir, but no mongrel.log or mongrel.pid. I also
noticed that it doesn’t start listening on specified port.

any ideas ?

Regards,
Bostjan

Hi Bostjan,

Can you upgrade your Mongrel to the RC from
http://mongrel.rubyforge.org/releases/ and then report back? It has
better error logging.

Evan

Does it work without -B?

Evan

After a lot of errors those errors i get:

Mon Oct 22 14:33:55 +0200 2007: ERROR: stream closed
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:580:
[BUG] Segmentation fault
ruby 1.8.6 (2007-03-13) [i386-freebsd6]

maybe that helps

no it doesn’t

funny thing is, mongrel_cluster works fine, so i’ll stick to it for
now :slight_smile:

regards,
bostjan

Maybe I broke it. For Mongrel 1.0.2, if you go into the gem directory
and run “ruby test/test_ws.rb”, do the tests pass?

What do you mean by “mongrel_cluster” works fine? What version of
mongrel? What output do you get compared to “mongrel_rails”?

Evan