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:
Moving to 6.3 wwith https://bugzilla.redhat.com/show_bug.cgi?id=1353458, moving to POST so that we catch it.
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.
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]: ...
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