Re: Unicorn

[Paul Sponagl <paul@sponagl.de>]

Hi Eric,

unicorn does not close the connection on osx after sending the content.
(It acts as the client would send a Connection: Keep-Alive)
The connection will be aborted by nginx after about 60
secs and the content will be send out.

Macintosh:~> telnet 127.0.0.1 3001
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
GET / HTTP/1.1

HTTP/1.1 200 OK
Date: Tue, 07 Jul 2009 08:11:17 GMT
Status: 200 OK
Connection: close
X-Runtime: 293
ETag: "2659d611050f70fc65c6c052687e5a13"
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=0, must-revalidate
Content-Length: 24328
...
the rest of the content



Hope that helps to track it down further.

Best
Paul


Am 07.07.2009 um 01:16 schrieb Eric Wong:

> Paul Sponagl <paul@sponagl.de> wrote:
>> Hi Eric,
>>
>> the Featurelist sounds great !
>>
>> I was using qrp for a long time and now i am eagerly awaiting a
>> production ready release of unicorn :)
>>
>> Btw. I tried it on OS-X with -l /tmp/thin.0.sock and it took a  
>> while for
>> nginx to spit out the page...
>>
>> ... (60: Operation timed out) while reading upstream, client:  
>> 127.0.0.1,
>> server: w..., request: "GET / HTTP/1.1", upstream: "http://unix
>> :/tmp/thin.0.sock:/" ...
>>
>> but finally it appeared  (for now it is not development ready for  
>> me ;)
>> But this evening i'll give it a try with tcp sockets.
>
> Weird.  I'm doubtful TCP sockets would solve your problems but let me
> know if it fixes it.  UNIX and TCP sockets follow exactly the same  
> code
> paths once the server is running so I'm not sure what could be the  
> issue
> (especially since you're sending a body-less GET request).  Maybe OSX
> has some weird rules/bugs with UNIX sockets (I've heard of issues with
> FIFOs on OSX), but I don't have access to an OSX machine.
>
> Is your "GET / HTTP/1.1" request supposed to be taking over 60s?  60
> seconds is the default (and IMHO very conservative) timeout for when
> Unicorn decides to terminate a request.
>
> 0.8.1 should actually be considered production-ready.  It doesn't
> support chunked transfer-encoding; but otherwise it's been running
> fine for some internal APIs for quite a while now.
>
>> thank you for your efforts in this great project and all the best
>
> Thanks for giving it a shot!
>
> -- 
> Eric Wong
>
> 
>
>


!DSPAM:4a53088a5179781588283!