独角兽错误:"ERROR -- : reaped #<Process::Status: pid 12345 SIGABRT (signal 6)>工人=2" [英] Unicorn error: "ERROR -- : reaped #<Process::Status: pid 12345 SIGABRT (signal 6)> worker=2"

查看:47
本文介绍了独角兽错误:"ERROR -- : reaped #<Process::Status: pid 12345 SIGABRT (signal 6)>工人=2"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们每天都会遇到这样的错误(有时不止一次):

We get errors like this one daily (sometimes more than once):

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

我们将 Unicorn 4.8.2 与 Ruby on Rails 应用一起使用.

We use Unicorn 4.8.2 with a Ruby on Rails app.

它似乎不会在任何明显的时间发生,例如在部署期间或之后.

It doesn't seem to happen at any obvious time, like during or just after deploys.

我们不知道如何调试这个问题——关于问题可能是什么或如何调试它有什么建议吗?

We're not sure how to debug this – any suggestions on either what the problem could be, or how to debug it?

推荐答案

事实证明这只是我们的监视器在进程执行时执行了kill -6"(SIBABRT)使用了太多内存,所以我们暂时超过了这个限制.

Turns out it was simply that our monit did a "kill -6" (SIBABRT) when the process used too much memory, so we bumped that limit for now.

我们还没有研究为什么它会使用这么多内存.

We've yet to research why it used that much memory.

这篇关于独角兽错误:&quot;ERROR -- : reaped #&lt;Process::Status: pid 12345 SIGABRT (signal 6)&gt;工人=2"的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆