From: nobu@... Date: 2019-09-14T07:23:59+00:00 Subject: [ruby-core:94935] [Ruby master Bug#16162] Resque::DirtyExit - Child process received unhandled signal (You may have encountered a bug in the Ruby interpreter or extension libraries) Issue #16162 has been updated by nobu (Nobuyoshi Nakada). It happens inside ���grpc��� extension library. Have you asked them? ---------------------------------------- Bug #16162: Resque::DirtyExit - Child process received unhandled signal (You may have encountered a bug in the Ruby interpreter or extension libraries) https://bugs.ruby-lang.org/issues/16162#change-81550 * Author: e.kostandini@forward.al (Ervin Kostandini) * Status: Feedback * Priority: Normal * Assignee: * Target version: * ruby -v: * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- My background jobs are all failing with the following error Resque::DirtyExit Child process received unhandled signal. After I restart the server they work for some minutes and then start failing. If I run the single jobs from Resque-schedule, they work fine. My background jobs are all failing with the following error Resque::DirtyExit Child process received unhandled signal. After I restart the server they work for some minutes and then start failing. If I run the single jobs from Resque-schedule, they work fine. Below is a part of the output of the resque-pool.stderr.log: I've tried reducing the number of jobs to only one that only logs to a file, but the error persists. I've also tried rebuilding the AWS server instance and the redis instance but the error is still there. System details: - Server instance: AWS linux version ( 4.14.88-72.76.amzn1.x86_64) - Resque version: 1.27.4 - Redis: AWS elastic cache - ruby: 2.3.8 - rails: 4.2 Details: https://stackoverflow.com/questions/57869424/resque-error-dirtyexit-child-process-received-unhandled-signal ---Files-------------------------------- resque-pool.stderr.log (1.85 MB) -- https://bugs.ruby-lang.org/ Unsubscribe: