Bug 848882

Summary:	misleading/wrong keep-alive error message in log
Product:	[Community] GlusterFS	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	core	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	gluster-bugs, vraman
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-24 17:17:51 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 Kaleb KEITHLEY 2012-08-16 17:24:52 UTC

Description of problem:

Gluster NFS and brick logs contain the following log entries:


[2012-08-16 09:23:39.498998] W [socket.c:410:__socket_keepalive] 0-socket: failed to set keep idle on socket 8
[2012-08-16 09:23:39.499049] W [socket.c:1876:socket_server_event_handler] 0-socket.glusterfsd: Failed to set keep-alive: Operation not supported
[2012-08-16 09:23:42.673756] I [client-handshake.c:1636:select_server_supported_

Stepping through the code though, setting keep-alive did actually work, it's the keep-idle that failed.

The actual problem is setting keep-idle on non-AF_INET sockets results in the spurious error message in the log.


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

all (-head, 3.3.0, 3.2.7)

How reproducible:

create and start a volume. Examine the logs.

Steps to Reproduce:

  
Actual results:


Expected results:


Additional info:

Comment 1 Vijay Bellur 2012-08-19 16:29:03 UTC

CHANGE: http://review.gluster.com/3823 (misleading/wrong keep-alive error message in log) merged in master by Anand Avati (avati)