Bug 764888 (GLUSTER-3156) - Avoid logging Socket read failures in glusterd
Summary: Avoid logging Socket read failures in glusterd
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3156
Product: GlusterFS
Classification: Community
Component: logging
Version: 3.1.4
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
Assignee: Rajesh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-12 09:19 UTC by Vijay Bellur
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions: master

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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)
Note You need to log in before you can comment on or make changes to this bug.