Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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).
Comment 3Tanya Tereshchenko
2017-11-23 21:20:41 UTC
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).
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