[Mongrel] Mongrel process unexpectedly dying

Tue, 18 Jul 2006 09:13:54 -0700

We tried to give Mongrel a go running our application which has moderate traffic. We got mongrel up and running easy enough but 3 times in a short period(2hours) mongrel just died with the following error when we went live to production with it. As you can see we are running mongrel-0.3.13.3.

/usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:576:in `peeraddr': Transport endpoint is not connected - getpeername(2) (Errno::ENOTCONN)

Is this a bug or a configuration problem of some sort on our end? I did some googling on the error and did not find anything.

We also get a large number of not fatal messages that maybe someone can enlighten me on. What would cause this message, and what does that client that caused this warning see?

Tue Jul 18 01:15:00 EDT 2006: BAD CLIENT (65.34.163.249): Invalid HTTP format, parsing fails

Thanks for your time.

-Dallas
sportspyder.com 
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users

Reply via email to