What logs and information to provide when opening a support case to qpid broker?
Environment
- MRG Messaging
Issue
What information (logs, configuration files, commands outputs) is in general recommended to provide to Red Hat support to speed-up initial investigation when opening a case to MRG Messaging / qpid broker (for cases reporting some problem with the broker)?
Resolution
If the problem is or can be broker related:
Provide:
- qpid logs (either as specified by
log-to-fileor - if not logging so -/var/log/messages) - either sosreport that contains most of usefull data (but also lots of uninportant for further investigation), or run below commands, ignore potential errors and provide final tarball:
mkdir /tmp/qpidProblem
cd /tmp/qpidProblem
rpm -qa > installed-packages
cp /etc/qpidd.conf .
cp /etc/sasl2/qpidd.conf sasl2-qpidd.conf
cp /etc/corosync/corosync.conf .
cp /etc/cluster/cluster.conf .
cp /var/log/cluster cluster.log
/usr/bin/qpid-config queues > qpid-config_queues.txt
/usr/bin/qpid-config exchanges > qpid-config_exchanges.txt
/usr/bin/qpid-config exchanges -r > qpid-config_bindings.txt
/usr/bin/qpid-config exchanges -b >> qpid-config_bindings.txt
/usr/bin/qpid-stat -g > qpid-stat-q.txt
/usr/bin/qpid-stat -m > qpid-stat-m.txt
/usr/bin/qpid-stat -e > qpid-stat-e.txt
/usr/bin/qpid-stat -q > qpid-stat-q.txt
/usr/bin/qpid-stat -u > qpid-stat-u.txt
/usr/bin/qpid-stat -c > qpid-stat-c.txt
/usr/bin/qpid-route route map > qpid-route_map.txt
/usr/bin/qpid-cluster > qpid-cluster.txt
/usr/bin/qpid-cluster -C > qpid-cluster-C.txt
ls -lR /var/lib/qpidd > ls-lR_var_lib_qpidd.txt
cd ..
tar cvzf qpidProblem-`hostname -s`.tar.gz qpidProblem
If the problem is or can be a client related:
Provide:
- client logs
- client setting (connection settings / connection URL, startup parameters like JVM qpid arguments)
If the problem is related to a broker journal
Follow this KCS article
SBR
Product(s)
Components
Category
Tags
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.