| Summary: | Enable high resolution timestamps for qpidd logs using QMF and a qpidd option. | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Raghu Udiyar <rudiyar> | |
| Component: | qpid-cpp | Assignee: | Chuck Rolke <crolke> | |
| Status: | CLOSED ERRATA | QA Contact: | mick <mgoulish> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 2.1 | CC: | iboverma, jross, lzhaldyb, mgoulish, rchidamb | |
| Target Milestone: | 3.0 | Keywords: | FutureFeature, Triaged | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | qpid-cpp-0.22-2 | Doc Type: | Enhancement | |
| Doc Text: |
It is now possible to enable or disable high resolution log time stamps while the broker is running. If time stamps are set to low resolution then many issues cannot be diagnosed effectively. Restarting the broker to enable high resolution time stamps was often not an option for users.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 957963 (view as bug list) | Environment: | ||
| Last Closed: | 2014-09-24 15:03:44 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Bug Depends On: | ||||
| Bug Blocks: | 957963 | |||
|
Comment 3
Justin Ross
2013-02-14 20:35:28 UTC
Fixed with r1445358 NOTE: since this was new functionality, I only verified it in new packages.
No need do anything with old packages.
To use this functionality:
vi /etc/qpid/qpidd.conf
log-time=1
log-enable=info+
log-to-file=/var/lib/qpidd/771830.log
qpid-tool
# now you are running qpid-tool
# you might have to do this next command a few times before answer.
# It takes a while to get all the info from the broker.
list broker
# see this:
# 114 14:03:39 - amqp-broker
# my broker's number is 114
call 114 setLogHiresTimestamp 1
# Now look at the log file and verify that it has started using
# highres time stamps. ( You might need to do something to get the
# broker to log a few more lines. i.e. start another qpid-tool. )
call 114 setLogHiresTimestamp 0
# Now look at the logfile again, and verify that it has *stopped*
# using highres.
Packages I used during verification:
cyrus-sasl-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-devel-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-gssapi-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-lib-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-md5-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-plain-2.1.23-13.el6_3.1.x86_64
perl-qpid-0.22-5.el6.x86_64
python-qpid-0.22-4.el6.noarch
python-qpid-qmf-0.22-9.el6.x86_64
python-saslwrapper-0.22-3.el6.x86_64
qpid-cpp-client-0.22-11.el6.x86_64
qpid-cpp-client-devel-0.22-11.el6.x86_64
qpid-cpp-client-devel-docs-0.22-11.el6.noarch
qpid-cpp-client-rdma-0.22-11.el6.x86_64
qpid-cpp-client-ssl-0.22-11.el6.x86_64
qpid-cpp-debuginfo-0.22-11.el6.x86_64
qpid-cpp-server-0.22-11.el6.x86_64
qpid-cpp-server-devel-0.22-11.el6.x86_64
qpid-cpp-server-ha-0.22-11.el6.x86_64
qpid-cpp-server-rdma-0.22-11.el6.x86_64
qpid-cpp-server-ssl-0.22-11.el6.x86_64
qpid-cpp-server-store-0.22-11.el6.x86_64
qpid-cpp-server-xml-0.22-11.el6.x86_64
qpid-cpp-tar-0.22-11.el6.noarch
qpid-java-client-0.22-5.el6.noarch
qpid-java-common-0.22-5.el6.noarch
qpid-java-example-0.22-5.el6.noarch
qpid-proton-c-0.4-2.2.el6.x86_64
qpid-proton-c-devel-0.4-2.2.el6.x86_64
qpid-proton-debuginfo-0.4-2.2.el6.x86_64
qpid-qmf-0.22-9.el6.x86_64
qpid-qmf-debuginfo-0.22-9.el6.x86_64
qpid-qmf-devel-0.22-9.el6.x86_64
qpid-snmpd-1.0.0-12.el6.x86_64
qpid-snmpd-debuginfo-1.0.0-12.el6.x86_64
qpid-tests-0.22-4.el6.noarch
qpid-tools-0.22-3.el6.noarch
rh-qpid-cpp-tests-0.22-11.el6.x86_64
ruby-qpid-0.7.946106-2.el6.x86_64
saslwrapper-0.22-3.el6.x86_64
saslwrapper-devel-0.22-3.el6.x86_64
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. http://rhn.redhat.com/errata/RHEA-2014-1296.html |