Hide Forgot
Description of problem: When investigating pulp or gofer issues, it is often valuable to know qpid broker queue statistics - ideally both queue stats and also subscription stats (to see if some consumer acquired messages and got stuck). That means, add: qpid-stat --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 -q qpid-stat --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 -u to foreman-debug commands to collect, both on Sat and Caps Version-Release number of selected component (if applicable): foreman-debug-1.7.2.46-1.el7sat.noarch How reproducible: 100% Steps to Reproduce: 1. take foreman-debug 2. find qpid-stat -q / qpid-stat -u output there Actual results: No such output Expected results: To collect that output Additional info:
Upstream bug component is Content Management
Upstream bug component is Packaging
Moving to POST since upstream bug http://projects.theforeman.org/issues/12678 has been closed ------------- Pavel Moravec As I understood, katello related stuff in foreman-debug should be placed to katello-debug.sh script. Since I am unable to find the script on github, posting the patch here: --- /usr/share/katello/script/katello-debug.sh 2015-12-03 10:42:38.701491316 +0100 +++ /usr/share/katello/script/katello-debug.sh.new 2015-12-03 10:42:33.566497422 +0100 @@ -56,6 +56,8 @@ if [ $NOGENERIC -eq 0 ]; then add_files /etc/qpid/* add_files /etc/qpidd.conf fi +add_cmd "qpid-stat --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 -q" "qpid_stat_queues" +add_cmd "qpid-stat --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 -u" "qpid_stat_subscriptions" # Gofer add_files /etc/gofer
We now have these 2 files in the foreman-debug. foreman-debug-a2yvh]# ll qpid_stat_* -rw-r--r--. 1 root root 13257 Apr 12 05:28 qpid_stat_queues -rw-r--r--. 1 root root 17382 Apr 12 05:28 qpid_stat_subscriptions VERIFIED withy sat62-snap7
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:1500