Red Hat Bugzilla – Bug 848882
misleading/wrong keep-alive error message in log
Last modified: 2013-12-18 19:08:34 EST
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)
create and start a volume. Examine the logs.
Steps to Reproduce:
CHANGE: http://review.gluster.com/3823 (misleading/wrong keep-alive error message in log) merged in master by Anand Avati (firstname.lastname@example.org)