Henrik Nyh <hen...@barsoom.se> wrote: > We get errors like this one a few times a day: > > Apr 13 12:16:31 app1 unicorn.log: E, [2014-04-13T12:16:31.302011 > #17269] ERROR -- : reaped #<Process::Status: pid 17300 SIGABRT (signal > 6)> worker=2 > > We use Unicorn 4.8.2, Ruby 2.1.1 and a Ruby on Rails app. > It doesn't seem to happen at any obvious time, like during or just > after deploys. > > We were previously on Ruby 1.9.3 with Unicorn 4.8.0. Then we had > almost the same issue but with SIGIOT, I believe. Then we upgraded > Ruby to 2.1.1. I believe that's when it changed to SIGABRT. Then we > upgraded Unicorn to 4.8.2 with no improvement. > > We're not sure how to debug this - any suggestions on either what the > problem could be, or how to debug it?
This is may be a bug in a C extension RubyGem or even Ruby itself. Do you get core dumps + backtraces or any other error messages in the logs? Which OS/distribution is this? Since you see SIGABRT/SIGIOT and not SIGSEGV, you might be crashing inside the SIGSEGV handler of Ruby itself. Can you also try --enable-debug-env when you ./configure Ruby? Thanks in advance for any more info you can provide! (Btw, please keep everybody Cc:-ed since the mailing list is going in that direction, and rubyforge.org isn't very reliable in its final days. New ML announcement in a few days). _______________________________________________ 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
