unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Matt Mongeau <halogenandtoast@gmail.com>
To: unicorn general mailing list <mongrel-unicorn@rubyforge.org>
Subject: Re: Unicorn Nginx Issue
Date: Tue, 13 Oct 2009 13:34:21 -0400	[thread overview]
Message-ID: <91d915350910131034t5dabb51eo5cde67397612f9f4@mail.gmail.com> (raw)
In-Reply-To: <91d915350910131027g6a3e9704r5becf0d2e7402e39@mail.gmail.com>

Got it working, I had a bad value in my config.

I had
listen '/Users/mattmongeau/projects/test/unicorn/tmp/sockets/unicorn.sock',
:backlog => 1024
I guess I needed
listen 'unix:/Users/mattmongeau/projects/test/unicorn/tmp/sockets/unicorn.sock',
:backlog => 1024

Thanks for the help.

On Tue, Oct 13, 2009 at 1:27 PM, Matt Mongeau <halogenandtoast@gmail.com> wrote:
> Hi Brian,
>
> my /etc/hosts file has an entry like this:
>
> 127.0.0.1 unicorn.local
>
> some further debugging...
> this works:
> unicorn_rails  -E production -l unix:tmp/sockets/unicorn.sock -D
> this does not:
> unicorn_rails  -E development -l unix:tmp/sockets/unicorn.sock -D
>
> On Tue, Oct 13, 2009 at 1:20 PM, Brian Ketelsen <bketelsen@gmail.com> wrote:
>>
>>
>> On Oct 13, 2009, at 12:57 PM, Matt Mongeau wrote:
>>
>>> 2009/10/13 12:34:22 [error] 1007#0: *62 connect() to
>>> unix:/Users/user/projects/test/unicorn/tmp/sockets/unicorn.sock failed
>>> (61: Connection refused) while connecting to upstream, client:
>>> 127.0.0.1, server: unicorn.local, request: "GET / HTTP/1.1", upstream:
>>>
>>> "http://unix:/Users/user/projects/test/unicorn/tmp/sockets/unicorn.sock:/",
>>> host: "unicorn.local"
>>>
>>> ps -aux shows that the workers are created
>>> and ls -la show srwxrwxrwx  1 mattmongeau  staff    0 Oct 13 12:51
>>> unicorn.sock=
>>>
>>> Any suggestions on what I am doing wrong. I running OSX 10.6.1, with
>>> nginx installed from passenger (nginx version: nginx/0.6.37)
>>>
>>> Thanks, Matt
>>> _______________________________________________
>>
>>
>>
>> You must have a host entry in /etc/hosts or in NetInfo for unicorn.local -
>> do you have it set to "localhost" or to 127.0.0.1?  I've seen issues in Mac
>> OS where I had to explicitly use 127.0.0.1 instead of localhost, and the
>> error messages looked similar.
>>
>> Brian
>> _______________________________________________
>> mongrel-unicorn mailing list
>> mongrel-unicorn@rubyforge.org
>> http://rubyforge.org/mailman/listinfo/mongrel-unicorn
>>
>

  reply	other threads:[~2009-10-13 17:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 16:57 Unicorn Nginx Issue Matt Mongeau
2009-10-13 17:20 ` Brian Ketelsen
2009-10-13 17:27   ` Matt Mongeau
2009-10-13 17:34     ` Matt Mongeau [this message]
2009-10-13 18:53       ` Eric Wong
2009-10-13 19:03         ` Matt Mongeau
2009-10-13 19:43           ` Eric Wong
2009-10-13 20:11             ` Matt Mongeau

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=91d915350910131034t5dabb51eo5cde67397612f9f4@mail.gmail.com \
    --to=halogenandtoast@gmail.com \
    --cc=mongrel-unicorn@rubyforge.org \
    /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).