Bug 1233694 - Quota: Porting logging messages to new logging framework
Summary: Quota: Porting logging messages to new logging framework
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: quota
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: RHGS 3.1.0
Assignee: Susant Kumar Palai
QA Contact: Anil Shah
URL:
Whiteboard:
Depends On:
Blocks: 1202842
TreeView+ depends on / blocked
 
Reported: 2015-06-19 12:26 UTC by Susant Kumar Palai
Modified: 2016-09-17 12:39 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-29 05:06:22 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1495 0 normal SHIPPED_LIVE Important: Red Hat Gluster Storage 3.1 update 2015-07-29 08:26:26 UTC

Description Susant Kumar Palai 2015-06-19 12:26:13 UTC
Description of problem:

Port logging messages to new logging framework

Comment 4 Humble Chirammal 2015-06-22 11:29:06 UTC
Backport of upstream master patch
http://review.gluster.org/#/c/7574/

Comment 10 Anil Shah 2015-07-20 08:52:42 UTC
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.

Comment 11 errata-xmlrpc 2015-07-29 05:06:22 UTC
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


Note You need to log in before you can comment on or make changes to this bug.