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.
Bug 1530692 - qdrouterd segfault when processing bursts of goferd requests
Summary: qdrouterd segfault when processing bursts of goferd requests
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Qpid
Version: 6.2.11
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: Unspecified
Assignee: Mike Cressman
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-03 16:13 UTC by Satellite Program
Modified: 2021-12-10 15:31 UTC (History)
8 users (show)

Fixed In Version: qpid-dispatch-0.8.0-16.el7sat
Doc Type: Bug Fix
Doc Text:
When several goferd client connections tried to use qdrouterd on Satellite to link to qpidd, qdrouterd experienced a segmentation fault. This is now fixed.
Clone Of: 1491160
Environment:
Last Closed: 2018-02-21 12:58:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3251561 0 None None None 2018-01-03 16:13:46 UTC
Red Hat Product Errata RHBA-2018:0338 0 normal SHIPPED_LIVE Red Hat Satellite 6.3 Tools 2018-02-21 19:30:02 UTC

Comment 2 Roman Plevka 2018-01-15 15:37:55 UTC
VERIFIED
satellite-6.3.0-23.0.el7sat.noarch (snap 31)

I crafted a rhel docker image by installing katello-ca certs on it + installing katello-agent package from dogfood repo (without registering to satellite).

- every docker container built from this image runs the following script:

```
subscription-manager register --org="$ORG" --environment="Library" $AUTH
while [ ! -f /tmp/docker-handle/start ]; do
        echo "waiting"
        sleep 0.1
done
echo "Starting goferd in foreground."
goferd -f
```

there's a semaphore file checking (/tmp/docker-handle/start), allowing me to start multiple containers and make them start gofer at the same time, by touching the file inside the mounted share.

i started up the containers in the following loop:
```
for  i in {1..50};do
    sudo docker run -d -v /dev/log:/dev/log -v /tmp/docker-handle:/tmp/docker-handle -t rplevka-6.3
done
```

after they all started up, all appropriate host records appeared on satellite and there were no more /rhsm requests running, i touched the 'start' file, which made all containers to start the gofer, which created pulp.agent* queues at the same time.

i was verifying everything by watching number of queues:

qpid-stat --ssl-certificate /etc/pki/katello/certs/java-client.crt --ssl-key /etc/pki/katello/private/java-client.key -b "amqps://localhost:5671" -q | grep -c pulp.agent

and also monitoring logs.

Comment 5 errata-xmlrpc 2018-02-21 12:58:46 UTC
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:0338


Note You need to log in before you can comment on or make changes to this bug.