unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Paul Sponagl <paul@sponagl.de>
Cc: mongrel-unicorn@rubyforge.org
Subject: Re: Unicorn
Date: Mon, 6 Jul 2009 16:16:46 -0700	[thread overview]
Message-ID: <20090706231646.GA22306@dcvr.yhbt.net> (raw)
In-Reply-To: <218F5913-4D49-4F6C-B334-CF264120D61A@sponagl.de>

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

  reply	other threads:[~2009-07-06 23:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06  8:21 Unicorn Paul Sponagl
2009-07-06 23:16 ` Eric Wong [this message]
2009-07-07  8:23   ` Unicorn Paul Sponagl
2009-07-07 20:48     ` Unicorn Eric Wong
     [not found]       ` <CE7F2AC4-4088-44ED-A5FF-2A41FE2B61EF@sponagl.de>
     [not found]         ` <20090708220413.GA32416@dcvr.yhbt.net>
2009-07-09  8:06           ` Unicorn Paul Sponagl
2009-07-09 10:10             ` Unicorn Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090706231646.GA22306@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=mongrel-unicorn@rubyforge.org \
    --cc=paul@sponagl.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).