unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Henrik Nyh <henrik@barsoom.se>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Cc: aaron@ktheory.com
Subject: Re: Workers reaped with SIGABRT - how to debug?
Date: Wed, 16 Apr 2014 09:08:06 +0200	[thread overview]
Message-ID: <CADBUp+1xAhRnOCBJ4w+ESDCX+e-_cKVpAStjgaX3_65AL_QU2g@mail.gmail.com> (raw)
In-Reply-To: <CADBUp+2TcpzdLoUa3HAAyR_Yf2ufGG2RiO66nRy5ywRPWLtQYw@mail.gmail.com>

> Henrik, we had the same problem after upgrading to Ruby 2.1.1. My
> coworker Tieg Zaharia tracked it down to this bug with
> BigDecimal#to_d:
>
> https://bugs.ruby-lang.org/issues/9657
>
> He discusses a workaround (using BigDecimal coercion instead of #to_d).
>
> Worked for us.

Thank you! We'll look into that. We've definitely seen that error in CI.

I couldn't find any segfaults in our production logs by the way, but
I'm still not sure exactly where they would go. Have looked in our
production.log (at the default prod log level) and the unicorn.log.

(Sidenote: I think you have to CC everyone, not just reply to the
list, or it only goes to the web archives.)
_______________________________________________
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

  parent reply	other threads:[~2014-04-16  7:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15  8:00 Workers reaped with SIGABRT - how to debug? Henrik Nyh
2014-04-15  8:43 ` Eric Wong
2014-04-15  9:05   ` Henrik Nyh
2014-04-15 10:34     ` Aaron Suggs
2014-04-16  7:08     ` Henrik Nyh [this message]
2014-04-28  9:25 ` Henrik Nyh
2014-04-28 10:41   ` 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=CADBUp+1xAhRnOCBJ4w+ESDCX+e-_cKVpAStjgaX3_65AL_QU2g@mail.gmail.com \
    --to=henrik@barsoom.se \
    --cc=aaron@ktheory.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).