From: Eric Wong <normalperson@yhbt.net>
To: George <lists@SouthernOhio.net>
Cc: mongrel-unicorn@rubyforge.org, Matt Smith <matt@nearapogee.com>,
Joel Nimety <jnimety@continuity.net>
Subject: Re: app error: Socket is not connected (Errno::ENOTCONN)
Date: Fri, 27 Apr 2012 19:51:00 +0000 [thread overview]
Message-ID: <20120427195100.GA322@dcvr.yhbt.net> (raw)
In-Reply-To: <CACsAZRR=NP4O+EB0koAr0aeUwth=M+5aQnA8vtVLEXqFHd=jnA@mail.gmail.com>
George <lists@SouthernOhio.net> wrote:
> Just fyi, my dev logs are now rife with these: http://j.mp/IezMAu
>
> Will plug your patch in, but will have to figure out another option for
> heroku deployment.
Is this affecting your heroku deployment? What OS/kernel version
are you running? From what Joel and Matt say, it could be more likely
to trigger on *BSD-based systems.
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2012-04-27 19:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 14:36 app error: Socket is not connected (Errno::ENOTCONN) Joel Nimety
2012-04-27 15:08 ` Matt Smith
2012-04-27 18:59 ` Eric Wong
2012-04-27 19:12 ` Joel Nimety
2012-04-27 19:32 ` Eric Wong
2012-04-27 19:45 ` Matt Smith
2012-04-27 19:47 ` Matt Smith
2012-04-27 19:47 ` Joel Nimety
2012-04-27 19:33 ` Matt Smith
[not found] ` <CACsAZRR=NP4O+EB0koAr0aeUwth=M+5aQnA8vtVLEXqFHd=jnA@mail.gmail.com>
2012-04-27 19:51 ` Eric Wong [this message]
2012-04-27 19:53 ` Eric Wong
2012-04-27 20:30 ` Matt Smith
2012-04-27 21:15 ` Eric Wong
[not found] ` <CACsAZRQqVZsLGYdS+=FU7zi=dhsqif8xRH7pK7h5Ocms8Jc3FA@mail.gmail.com>
2012-04-27 21:16 ` Eric Wong
2012-04-27 22:14 ` Matt Smith
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=20120427195100.GA322@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=jnimety@continuity.net \
--cc=lists@SouthernOhio.net \
--cc=matt@nearapogee.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).