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 1340375 - Backport DISPATCH-154 to Satellite / qpid-dispatch-router
Summary: Backport DISPATCH-154 to Satellite / qpid-dispatch-router
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: katello-agent
Version: 6.1.8
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Sanket Jagtap
URL:
Whiteboard:
Depends On:
Blocks: 1388545
TreeView+ depends on / blocked
 
Reported: 2016-05-27 08:30 UTC by Pavel Moravec
Modified: 2021-08-30 10:43 UTC (History)
7 users (show)

Fixed In Version: qpid-dispatch-0.4-17
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1388545 (view as bug list)
Environment:
Last Closed: 2016-11-10 08:13:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA DISPATCH-154 0 None None None 2016-05-27 08:31:45 UTC
Red Hat Bugzilla 1312419 0 high CLOSED Memory leak and occasional segfault in qdrouterd when (un)installing a package from Satellite6 2021-08-30 10:44:01 UTC
Red Hat Knowledge Base (Solution) 1605633 0 None None None 2016-05-27 08:32:04 UTC
Red Hat Product Errata RHBA-2016:2699 0 normal SHIPPED_LIVE Satellite 6.2.4 Async Bug Release 2016-11-10 13:12:22 UTC

Internal Links: 1312419

Description Pavel Moravec 2016-05-27 08:30:56 UTC 
Description of problem:
When there is a DNS issue failing to resolve Satellite/Capsule's FQDN, an attempt to create an outbound connection from a qdrouterd causes segfault. See:

https://issues.apache.org/jira/browse/DISPATCH-154

for details (artificial reproducer provided there) and for the fix as well.

Please backport DISPATCH-154 to Satellite, e.g. together with bz1312419 (another segfault in qdrouterd, also with a fix).


Version-Release number of selected component (if applicable):
qpid-dispatch-router-0.4-11.el7.x86_64


How reproducible:
100%


Steps to Reproduce:
Either follow DISPATCH-154 or directly for Satellite:
1. Stop hostname resolution (stop DNS, purge /etc/hosts,..) such that "ping $(hostname -f)" wont work
2. run:
service qdrouterd restart
sleep 10
service qdrouter status


Actual results:
qdrouterd would fail and segfault


Expected results:
qdrouterd trying to reconnect to the FQDN it cant resolve


Additional info:
Comment 14 Bryan Kearney 2016-09-14 11:42:45 UTC 
Moving to 6.3 wwith https://bugzilla.redhat.com/show_bug.cgi?id=1353458, moving to POST so that we catch it.
Comment 16 jcallaha 2016-10-11 19:02:19 UTC 
Verified in Satellite 6.2.3 Snap 2.

Again followed the steps outlined in the jira, with configuration outlined in #11. No longer seeing the issue in qdrouterd status.

[root@rhsm-qe-1 workstation]# service qdrouterd restart && sleep 10 && service qdrouterd status
Redirecting to /bin/systemctl restart  qdrouterd.service
Redirecting to /bin/systemctl status  qdrouterd.service
● qdrouterd.service - Qpid Dispatch router daemon
   Loaded: loaded (/usr/lib/systemd/system/qdrouterd.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2016-10-11 15:01:33 EDT; 10s ago
 Main PID: 2644 (qdrouterd)
   Memory: 9.7M
   CGroup: /system.slice/qdrouterd.service
           └─2644 /usr/sbin/qdrouterd -c /etc/qpid-dispatch/qdrouterd.conf

Oct 11 15:01:33 rhsm-qe-1.rhq.lab.eng.bos.redhat.com qdrouterd[2644]: Tue Oct 11 15:01:33 2016 ROUTER (info) Configured Address: prefix=/ phase=0 fanout=QD_SCHEMA_FIXEDADDRESS_FA..._MULTIPLE
Oct 11 15:01:33 rhsm-qe-1.rhq.lab.eng.bos.redhat.com qdrouterd[2644]: Tue Oct 11 15:01:33 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:5647 role=normal
Oct 11 15:01:33 rhsm-qe-1.rhq.lab.eng.bos.redhat.com qdrouterd[2644]: Tue Oct 11 15:01:33 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:5646 role=inter-router
Oct 11 15:01:33 rhsm-qe-1.rhq.lab.eng.bos.redhat.com qdrouterd[2644]: Tue Oct 11 15:01:33 2016 CONN_MGR (info) Configured on-demand connector: rhsm-qe-1.rhq.lab.eng.bos.redhat.co...me=broker
Oct 11 15:01:33 rhsm-qe-1.rhq.lab.eng.bos.redhat.com qdrouterd[2644]: Tue Oct 11 15:01:33 2016 ROUTER (info) Configured Link-route-pattern: prefix=pulp. dir=both connector=broker
Oct 11 15:01:33 rhsm-qe-1.rhq.lab.eng.bos.redhat.com qdrouterd[2644]: Tue Oct 11 15:01:33 2016 ROUTER (info) Configured Link-route-pattern: prefix=qmf. dir=both connector=broker
Oct 11 15:01:33 rhsm-qe-1.rhq.lab.eng.bos.redhat.com qdrouterd[2644]: Tue Oct 11 15:01:33 2016 CONN_MGR (info) Starting on-demand connector: broker
Oct 11 15:01:33 rhsm-qe-1.rhq.lab.eng.bos.redhat.com qdrouterd[2644]: Tue Oct 11 15:01:33 2016 SERVER (info) Operational, 12 Threads Running
Oct 11 15:01:35 rhsm-qe-1.rhq.lab.eng.bos.redhat.com qdrouterd[2644]: Tue Oct 11 15:01:35 2016 ROUTER (info) Activating Prefix 'pulp.' for routed links to 'broker'
Oct 11 15:01:35 rhsm-qe-1.rhq.lab.eng.bos.redhat.com qdrouterd[2644]: Tue Oct 11 15:01:35 2016 ROUTER (info) Activating Prefix 'qmf.' for routed links to 'broker'
Hint: Some lines were ellipsized, use -l to show in full.
Comment 18 Sanket Jagtap 2016-11-03 11:06:35 UTC 
Build : Satellite 6.2.4 snap 1

rpm -qa | grep dispatch
qpid-dispatch-router-0.4-18.el7sat.x86_64
libqpid-dispatch-0.4-18.el7sat.x86_64


Using the reproducer steps in the jira https://issues.apache.org/jira/browse/DISPATCH-154

Added a bogus entry in config file and restarted service , No longer able to reproduce the issue

service qdrouterd status
Redirecting to /bin/systemctl status  qdrouterd.service
● qdrouterd.service - Qpid Dispatch router daemon
   Loaded: loaded (/usr/lib/systemd/system/qdrouterd.service; enabled; vendor pr
eset: disabled)
   Active: active (running) since Thu 2016-11-03 04:43:34 EDT; 6s ago
 Main PID: 23938 (qdrouterd)
   CGroup: /system.slice/qdrouterd.service
           └─23938 /usr/sbin/qdrouterd -c /etc/qpid-dispatch/qdrouterd.conf

Nov 03 04:43:34 abc.redhat.com qdrouterd[23938]: ...
Nov 03 04:43:35 abc.redhat.com qdrouterd[23938]: ...
Nov 03 04:43:35 abc.redhat.com qdrouterd[23938]: ...
Nov 03 04:43:35 abc.redhat.com qdrouterd[23938]: ...
Nov 03 04:43:35 abc.redhat.com qdrouterd[23938]: ...
Nov 03 04:43:35 abc.redhat.com qdrouterd[23938]: ...
Nov 03 04:43:35 abc.redhat.com qdrouterd[23938]: ...
Nov 03 04:43:35 abc.redhat.com qdrouterd[23938]: ...
Nov 03 04:43:36 abc.redhat.com qdrouterd[23938]: ...
Nov 03 04:43:36 abc.redhat.com qdrouterd[23938]: ...
Comment 20 errata-xmlrpc 2016-11-10 08:13:14 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-2016:2699
Note You need to log in before you can comment on or make changes to this bug.