A small correction: segfault can rarely happen also when pulp.task queue delivers no message. But with much lower probability than when the queue is in use (and I think the more msgs are sent there, the higher the probability is).

It's a dup of BZ#1510589 but description here is much more specific and contains a reproducer. Can we close BZ#1510589 as a dup of this BZ and not the other way around?

(In reply to Tanya Tereshchenko from comment #3)
> It's a dup of BZ#1510589 but description here is much more specific and
> contains a reproducer. Can we close BZ#1510589 as a dup of this BZ and not
> the other way around?

I havent realized there is already a BZ :( Sorry for DUP, close which one you prefer.

Few more observations:
- segfault happens also on "service httpd reload" (not force-reload specific)
- sometimes it seems the probability of hitting the segfault grows over the execution time of httpd service

My further understanding is the segfaulting process is one of:

apache   15093  4.2  0.4 1162584 74024 ?       Sl   17:58   0:00 (wsgi:pulp)     -DFOREGROUND

running before "service httpd restart" is executed. Since all those processes are killed and re-spawned by the service reload, there should not be much (if any) harm if a process segfaults just before it would be shut down (until it is in a middle of an operation, but backtraces show it is idle).

*** Bug 1510589 has been marked as a duplicate of this bug. ***

The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.

The Pulp upstream bug priority is at High. Updating the external tracker on this bug.

The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.

The Pulp upstream bug status is at POST. Updating the external tracker on this bug.

The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.

All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.

The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1950