Bug 868881
| Summary: | qpidd logging: too many JournalInactive messages by default - request for logging level change info -> debug or change periodicity | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Frantisek Reznicek <freznice> |
| Component: | qpid-cpp | Assignee: | Chuck Rolke <crolke> |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Zhaldybin <lzhaldyb> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | Development | CC: | esammons, iboverma, jross, lzhaldyb, mcressma, rdassen |
| Target Milestone: | 2.3 | Keywords: | EasyFix |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qpid-cpp-0.18-7 | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
JournalInactive messages appear when certain broker scheduling algorithms are triggered and the user is running at INFO log level. There is nothing a customer can do to stop the scheduling triggers and there is no convenient way to turn the JournalInactive messages off.
Consequence:
The user log file is filled with repetitive JournalInactive messages.
Fix:
The priority of the JournalInactive log messages is lowered to DEBUG level and the message frequency is lowered from 12/second to 1/second. If the broker is running at INFO log level the JournalInactive messages may be selectively re-enabled by using switch: --log-enable debug+:Timer
Result:
The users log file is not cluttered with JournalInactive messages.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-06 18:52:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 785156 | ||
|
Description
Frantisek Reznicek
2012-10-22 11:19:25 UTC
These statements are not produced by store code. Rather they are qpid::sys::TimerWarnings. Gordon Sim reduced the severity from Warning to Info in September, 2011. http://mail-archives.apache.org/mod_mbox/qpid-commits/201109.mbox/%3C20110908172735.BB50B23889EB@eris.apache.org%3E It looks like the journal tasks are perpetually late which is not surprising based on the job that they do. To fix this for Journal would be an across the board change for all qpid tasks. Patched upstream at r1045316. The patch demotes TimerWarning messages, which produce the JournalInactive messages above, to debug level and, if enabled, prints each message once per minute. This patch affects all TimerWarning messages and not just JournalInactive messages. To a customer these messages are alarming and of dubious value. These messages may be of interest to a diagnostic engineer some day and are enabled selectively by using broker switch: --log-enable debug+:Timer Tested on RHEL5.9 and RHEL6.3 (both i386 and x86_64). The issue has been fixed, the JournalInactive log message has 'debug' level now. Packages used for testing: RHEL5.9 python-qpid-0.18-4.el5 python-qpid-qmf-0.18-12.el5 qpid-cpp-client-0.18-12.el5 qpid-cpp-client-devel-0.18-12.el5 qpid-cpp-client-devel-docs-0.18-12.el5 qpid-cpp-client-ssl-0.18-12.el5 qpid-cpp-server-0.18-12.el5 qpid-cpp-server-cluster-0.18-12.el5 qpid-cpp-server-devel-0.18-12.el5 qpid-cpp-server-ssl-0.18-12.el5 qpid-cpp-server-store-0.18-12.el5 qpid-cpp-server-xml-0.18-12.el5 qpid-java-client-0.18-5.el5 qpid-java-common-0.18-5.el5 qpid-java-example-0.18-5.el5 qpid-qmf-0.18-12.el5 qpid-qmf-devel-0.18-12.el5 qpid-tools-0.18-7.el5 RHEL6.3 python-qpid-0.18-4.el6 python-qpid-qmf-0.18-12.el6_3 qpid-cpp-client-0.18-12.el6_3 qpid-cpp-client-devel-0.18-12.el6_3 qpid-cpp-client-devel-docs-0.18-12.el6_3 qpid-cpp-server-0.18-12.el6_3 qpid-cpp-server-cluster-0.18-12.el6_3 qpid-cpp-server-devel-0.18-12.el6_3 qpid-cpp-server-store-0.18-12.el6_3 qpid-cpp-server-xml-0.18-12.el6_3 qpid-java-client-0.18-5.el6 qpid-java-common-0.18-5.el6 qpid-java-example-0.18-5.el6 qpid-qmf-0.18-12.el6_3 qpid-qmf-devel-0.18-12.el6_3 qpid-tools-0.18-7.el6_3 -> VERIFIED 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/RHSA-2013-0561.html |