i'm experiencing quite few of these in production logs:
e, [2016-01-24t20:34:44.862096 #21631] error -- : reaped #<process::status: pid 23077 sigkill (signal 9)> worker=10 e, [2016-01-24t20:34:44.862282 #21631] error -- : worker=12 pid:23064 timeout (61s > 60s), killing e, [2016-01-24t20:34:44.876932 #21631] error -- : reaped #<process::status: pid 23064 sigkill (signal 9)> worker=12 i, [2016-01-24t20:34:44.895914 #23619] info -- : worker=12 ready
i'm using both new relic , honeybadger track errors, since unicorn worker get's killed, cannot figure out requests taking long.
i tried implementing middleware described in this blog post, throws following error when testing out in local dev:
i, [2016-01-24t21:22:08.453846 #63197] info -- : [cc042b92-0530-4c9c-9503-73bba529fe20] completed 200 ok in 1061ms (views: 1016.8ms | activerecord: 3.8ms) f, [2016-01-24t21:22:08.458914 #63197] fatal -- : [cc042b92-0530-4c9c-9503-73bba529fe20] threaderror (killed thread): config/initializers/log_before_timeout.rb:19:in `run' config/initializers/log_before_timeout.rb:19:in `call'
what can fix this? alternatively, there better way inspecting this?
btw did not used default rails server (webbrick) test locally.
Comments
Post a Comment