I added a bunch of (more) granular-level issues to http://projects.theforeman.org/issues/3511 tracker.
Cheers, -d On Wed, Nov 22, 2017 at 2:13 PM, Dmitri Dolguikh <witlessb...@gmail.com> wrote: > On Wed, Nov 22, 2017 at 9:33 AM, James Shewey <jdshe...@gmail.com> wrote: > >> You may not be getting an ABRT because ruby was patched some time ago to >> catch this ABRT and a handler was created to make this a non-fatal error >> (ruby used to just core dump - see https://bugzilla.redhat.com/sh >> ow_bug.cgi?id=717709). I suspect that is why you aren't seeing the >> expected signal further down the stack. >> > > This doesn't explain the behaviour I'm seeing -- an exception would be > caught and logged, and foreman would continue to run. I'm seeing the app > exit without any stacktraces or core-dumps. I'm not using system ruby > either. > > -d > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
