Bug 1167734

Summary:	Enhancement: command that failed with cli-timeout should be logged in CMD_LOG_HISTORY file
Product:	[Community] GlusterFS	Reporter:	SATHEESARAN <sasundar>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-20 09:09:04 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:

Description SATHEESARAN 2014-11-25 10:31:41 UTC

Description of problem:
-----------------------
As of today, when the cli timesout for a gluster command, the error message - "Error: Request timed out". But this corresponding error message was not available in /var/log/glusterfs/.cmd_log_history file.

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
mainline

How reproducible:
-----------------
NA as this is a enhancement requirement

Steps to Reproduce:
-------------------
1. Simulate a cli timeout for a command, by blocking another glusterd in gdb or using iptables
2. Execute 'gluster volume status' or any other command that operates cluster-wide
3. Once the cli times out, check for error message in /var/log/glusterfs/.cmd_log_history

Actual results:
----------------
There is no corresponding cli-timed out error message available in /var/log/glusterfs/cmd_log_history


Expected results:
----------------
cli-timeout error message when available in cmd_log_history would help a lot in debugging


Additional info:

Comment 2 Vijay Bellur 2018-11-20 09:37:52 UTC

Migrated to github:

https://github.com/gluster/glusterfs/issues/590

Please follow the github issue for further updates on this bug.