Bug 1191423

Summary:	upgrade to gluster 3.6
Product:	[Community] GlusterFS	Reporter:	Felix <felix.delelisdd>
Component:	glusterd	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.6.2	CC:	asmarre, bugs, lmohanty
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-01 04:42:30 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 Felix 2015-02-11 10:19:10 UTC

Description of problem:

Hi,

I have upgraded to version 3.6 from 3.5, and the lunch continuosly the following errors:

[2015-02-11 10:07:20.689299] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:07:23.689774] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:07:26.690279] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:07:29.690873] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:07:32.691446] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:07:35.692048] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:07:38.692481] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:07:41.693026] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:07:44.693586] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:07:47.694148] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:07:50.694767] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:07:53.695269] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:07:56.695877] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:07:59.696423] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:08:02.696937] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:08:05.697503] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:08:08.698032] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:08:11.698554] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)
[2015-02-11 10:08:14.699113] W [socket.c:611:__socket_rwv] 0-management: readv on /var/run/032613d904825273481612e900965093.socket failed (Invalid argument)

How I can resolve it?

thanks

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Lalatendu Mohanty 2015-02-17 12:10:43 UTC

The messages in the log are warnings, hence lowering the severity.

Comment 2 Atin Mukherjee 2016-08-01 04:42:30 UTC

This is not a security bug, not going to fix this in 3.6.x because of
http://www.gluster.org/pipermail/gluster-users/2016-July/027682.html

Comment 3 Atin Mukherjee 2016-08-01 04:43:50 UTC

If the issue persists in the latest releases, please feel free to clone them