I think we have solved this issue. It was simply that monit did a "kill -6" (SIBABRT) when the process used too much memory, so we bumped that limit for now. D'oh. We've yet to research why it used that much memory.
On Tue, Apr 15, 2014 at 10:00 AM, Henrik Nyh <[email protected]> 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? __ http://bogomips.org/unicorn-public/ - [email protected] please quote as little as necessary when replying
