Bug 1233694
| Summary: | Quota: Porting logging messages to new logging framework | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Susant Kumar Palai <spalai> |
| Component: | quota | Assignee: | Susant Kumar Palai <spalai> |
| Status: | CLOSED ERRATA | QA Contact: | Anil Shah <ashah> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | rhgs-3.1 | CC: | annair, ashah, hchiramm, nsathyan, rgowdapp, rhs-bugs, storage-qa-internal, vagarwal |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-07-29 05:06:22 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: | 1202842 | ||
|
Description
Susant Kumar Palai
2015-06-19 12:26:13 UTC
Backport of upstream master patch http://review.gluster.org/#/c/7574/ Below logs messages are not available in the patch.
[@dhcp-0-189 quota]$ grep -r "gf_log " *
src/quota-enforcer-client.c: gf_log (this->name, GF_LOG_WARNING, "failed to connect "
src/quota-enforcer-client.c: gf_log (this->name, GF_LOG_DEBUG, "retry connecting to "
src/quota-enforcer-client.c: gf_log (this->name, GF_LOG_WARNING, "failed to "
src/quota-enforcer-client.c: gf_log (this->name, GF_LOG_DEBUG, "connected to quotad after "
src/quota.c: gf_log (this->name, GF_LOG_ERROR,
src/quota.c: gf_log (this->name, GF_LOG_ERROR, "Received null argument");
src/quotad.c: gf_log (this->name, GF_LOG_WARNING, "Memory accounting "
src/quotad.c: gf_log (this->name, GF_LOG_ERROR,
[satheesaran@dhcp-0-189 quota]$ git blame src/quota-enforcer-client.c | grep -r "gf_log " *
src/quota-enforcer-client.c: gf_log (this->name, GF_LOG_WARNING, "failed to connect "
src/quota-enforcer-client.c: gf_log (this->name, GF_LOG_DEBUG, "retry connecting to "
src/quota-enforcer-client.c: gf_log (this->name, GF_LOG_WARNING, "failed to "
src/quota-enforcer-client.c: gf_log (this->name, GF_LOG_DEBUG, "connected to quotad after "
src/quota.c: gf_log (this->name, GF_LOG_ERROR,
src/quota.c: gf_log (this->name, GF_LOG_ERROR, "Received null argument");
src/quotad.c: gf_log (this->name, GF_LOG_WARNING, "Memory accounting "
src/quotad.c: gf_log (this->name, GF_LOG_ERROR,
[satheesaran@dhcp-0-189 quota]$ git blame src/quota-enforcer-client.c | grep "gf_log "
062e8379 (vmallika 2015-04-14 10:44:13 +0530 198) gf_log (this->name, GF_LOG_WARNING, "failed to connect "
062e8379 (vmallika 2015-04-14 10:44:13 +0530 209) gf_log (this->name, GF_LOG_DEBUG, "retry connecting to "
062e8379 (vmallika 2015-04-14 10:44:13 +0530 219) gf_log (this->name, GF_LOG_WARNING, "failed to "
062e8379 (vmallika 2015-04-14 10:44:13 +0530 242) gf_log (this->name, GF_LOG_DEBUG, "connected to quotad after "
[satheesaran@dhcp-0-189 quota]$ git blame src/quota-enforcer-client.c | grep "gf_msg "
4e48c71a (Susant Palai 2015-05-25 16:52:10 +0530 153) gf_msg (this->name, GF_LOG_ERROR, 0,
4e48c71a (Susant Palai 2015-05-25 16:52:10 +0530 232) gf_msg (this->name, GF_LOG_WARNING, rsp.op_errno,
4e48c71a (Susant Palai 2015-05-25 16:52:10 +0530 311) gf_msg (this->name, GF_LOG_WARNING, 0,
4e48c71a (Susant Palai 2015-05-25 16:52:10 +0530 464) gf_msg ("quota", GF_LOG_ERROR, 0,
RPC related error are very tough to reproduce.
Was able to see error message id for soft-limit.
Message id start with 1200 series quota. However header files says message id start with 1100 series
Will open separate bug for the wrong message id series and error logs which are not available in the current patch.
Marking this bug verified on build 3.7-1-10.
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://rhn.redhat.com/errata/RHSA-2015-1495.html |