Bug 764888 (GLUSTER-3156)

Summary:	Avoid logging Socket read failures in glusterd
Product:	[Community] GlusterFS	Reporter:	Vijay Bellur <vijay>
Component:	logging	Assignee:	Rajesh <rajesh>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.1.4	CC:	gluster-bugs, rahulcs, vagarwal
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:	master	Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Vijay Bellur 2011-07-12 09:19:36 UTC

When a cli command terminates, the following log is observed in glusterd's logs:

[2011-07-08 17:43:47.462807] W [socket.c:1494:__socket_proto_state_machine] 0-socket.management: reading from socket failed. Error (Transport endpoint is not connected), peer (127.0.0.1:1021)

The above log should be avoided post a CLI command execution.

Comment 1 Anand Avati 2011-07-25 13:25:27 UTC

CHANGE: http://review.gluster.com/22 (An option, transport.socket.read-fail-log was added in glusterd.) merged in master by Anand Avati (avati)

Comment 2 Rahul C S 2011-09-05 05:11:20 UTC

This message is not getting logged everytime now.

Comment 3 Vijay Bellur 2013-01-15 10:25:56 UTC

CHANGE: http://review.gluster.org/4377 (socket: Don't log readv failures if read-fail-log is false) merged in master by Vijay Bellur (vbellur)