Bug 1458656 - gluster-blockd: server nodes doesn't log
Summary: gluster-blockd: server nodes doesn't log
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-block
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.3.0
Assignee: Prasanna Kumar Kalever
QA Contact: surabhi
URL:
Whiteboard:
Depends On:
Blocks: 1417151
TreeView+ depends on / blocked
 
Reported: 2017-06-05 06:40 UTC by Prasanna Kumar Kalever
Modified: 2017-09-21 04:19 UTC (History)
1 user (show)

Fixed In Version: gluster-block-0.2.1-1.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-21 04:19:33 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:2773 0 normal SHIPPED_LIVE new packages: gluster-block 2017-09-21 08:16:22 UTC

Description Prasanna Kumar Kalever 2017-06-05 06:40:39 UTC 
Description of problem:
The server threads running as part of daemon have no logging, hence currently you can notice only the cli thread (executed by node where cli commands are executed) will only log.

* add logging at server side, about each transaction
* add log-level option, i.e filter log messages based on severity level
* other minor logging improvements which are needed
Comment 7 surabhi 2017-06-19 09:45:31 UTC 
Now there are different levels of logs according to severity which can be set using following commands and logs are displayed correctly.

gluster-blockd --log-level ERROR
gluster-blockd --log-level DEBUG

Now the transactions are also logged which was not the case earlier.If there is any further improvement needed in logging will raise another BZ.
Marking the BZ verified.

gluster-block-0.2.1-1.el7rhgs.x86_64
Comment 9 errata-xmlrpc 2017-09-21 04:19:33 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://access.redhat.com/errata/RHEA-2017:2773
Note You need to log in before you can comment on or make changes to this bug.