[Mongrel] random cpu spikes, EBADF errors

Robert Mela rob at robmela.com
Mon Oct 29 16:27:49 EDT 2007


 > When mongrel was working, it should send the reply back to LSWS 
before closing the socket.

There's a string prepared for the purpose in mongre.rb

    ERROR_503_RESPONSE="HTTP/1.1 503 Service Unavailable\r\n\r\nBUSY".freeze

It's a one-liner to send that to the socket before calling close.

Zachary Powell wrote:
> Hi All,
>
> Follow up to the CPU/EBADF issue I was having with lsws:
>
>  
> http://www.litespeedtech.com/support/forum/showthread.php?t=1012&goto=newpost 
> <http://www.litespeedtech.com/support/forum/showthread.php?t=1012&goto=newpost>
> Here is the message that has just been posted:
> ***************
> The problem is on mongrel side. As shown in the strace output, file 
> handle 5 is the reverse proxy connection from LSWS to mongrel. Mongrel 
> read the request, then it closed the connection immediately without 
> sending back anything, then try to close it again with result EBADF, 
> because the file descriptor has been closed already.
>
> When mongrel was working, it should send the reply back to LSWS before 
> closing the socket.
>
> The root cause of the problem is on Mongrel side, however, LSWS should 
> fail the request after a few retries. We will implement that in our 
> 3.3 release.
> ***************
>
>  
> Zach

-------------- next part --------------
A non-text attachment was scrubbed...
Name: rob.vcf
Type: text/x-vcard
Size: 116 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20071029/194db8f5/attachment.vcf 


More information about the Mongrel-users mailing list