Bug 761957 (GLUSTER-225)

Summary:	Log message not intuitive when server name itself is given as the remote subvolume
Product:	[Community] GlusterFS	Reporter:	Anush Shetty <anush>
Component:	protocol	Assignee:	Vijay Bellur <vbellur>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	2.0.6	CC:	aavati, gluster-bugs, lakshmipathi
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	RTNR	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Anush Shetty 2009-08-24 05:13:31 UTC

When the server name itself is given as the remote subvolume, the log message isn't intuitive enough and it displays authentication failure errors

[2009-08-21 03:27:26] E [authenticate.c:226:gf_authenticate] auth: no authentication module is interested in accepting remote-client 127.0.0.1:1023
[2009-08-21 03:27:26] E [server-protocol.c:7045:mop_setvolume] server1: Cannot authenticate client from 127.0.0.1:1023
[2009-08-21 03:27:26] N [server-protocol.c:7796:notify] server1: 127.0.0.1:1023 disconnected
[2009-08-21 03:27:26] N [server-helpers.c:723:server_connection_destroy] server1: destroyed connection of brick7-8764-2009/08/21-03:27:15:282714-server1
[2009-08-21 03:27:26] E [authenticate.c:226:gf_authenticate] auth: no authentication module is interested in accepting remote-client 127.0.0.1:1022

Comment 1 Anand Avati 2010-01-23 10:01:14 UTC

Log message is sufficiently intuitive for me. Have a another look at the log with care and reopen if you do not find it intuitive again.