<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
"... a client which is running higher version than the server [...]
glusterd will reject the mount request." is incorrect. You are
correct in your understanding that the rpc is supposed to be
cross-version compatible with newer features not being allowed as
long as older versions are in the cluster as either servers or
clients.<br>
<br>
The problem seems to have come from a policy shift between 3.7.2 and
3.7.3 where 3.7.3 uses unprivileged ports by default (there was
supposed to be an email set to gluster-announce but I can't find
that nor hardly any other announcements this year).<br>
<br>
To solve this, add "option rpc-auth-allow-insecure on" to
"/etc/glusterfs/glusterd.vol" and set "server.allow-insecure on" for
your volumes.<br>
<br>
<div class="moz-cite-prefix">On 08/13/2015 11:47 AM, Taylor Lewick
wrote:<br>
</div>
<blockquote
cite="mid:70DB60AB185EF74D8C215BF05963F42C040DC5CF@plb-exmail02.adknowledge.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Ok,
Thank you, I had read online where gluster supported
backwards compatibility, with respect to newer client
versions working with older server versions. Thanks for
the clarification…<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
Atin Mukherjee [<a class="moz-txt-link-freetext" href="mailto:atin.mukherjee83@gmail.com">mailto:atin.mukherjee83@gmail.com</a>]
<br>
<b>Sent:</b> Thursday, August 13, 2015 10:46 AM<br>
<b>To:</b> Taylor Lewick<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
<b>Subject:</b> Re: [Gluster-users] After Centos 6 yum
update client fails to mount glusterfs volume<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p>-Atin<br>
Sent from one plus one<br>
On Aug 13, 2015 9:11 PM, "Taylor Lewick" <<a
moz-do-not-send="true" href="mailto:tlewick@adknowledge.com"><a class="moz-txt-link-abbreviated" href="mailto:tlewick@adknowledge.com">tlewick@adknowledge.com</a></a>>
wrote:<br>
><br>
> As a follow up, I created a test gluster cluster,
installed 3.6, and upgraded it to 3.7. I verified client
machines running glusterfs 3.6 and 3.7 could mount the volume
via glusterfs…<br>
><br>
> <br>
><br>
> So currently, clients running 3.7 can’t mount a gluster
volume via glusterfs if the gluster servers are running
3.6.x. I didn’t test mounting the volume via NFS. <br>
I think I didn't understood your problem earlier. If you are
trying to connect a client which is running higher version
than the server then its expected as glusterd will reject the
mount request. You should first upgrade your servers followed
by the clients.<br>
><br>
> When it fails it still returns an authentication error. <br>
><br>
> <br>
><br>
> Not sure if this is a bug or just requires specifically
setting some authentication parameters on the volume/cluster.<br>
><br>
> <br>
><br>
> From: <a moz-do-not-send="true"
href="mailto:gluster-users-bounces@gluster.org">gluster-users-bounces@gluster.org</a>
[mailto:<a moz-do-not-send="true"
href="mailto:gluster-users-bounces@gluster.org">gluster-users-bounces@gluster.org</a>]
On Behalf Of Taylor Lewick<br>
> Sent: Wednesday, August 12, 2015 10:52 AM<br>
> To: <a moz-do-not-send="true"
href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> Subject: [Gluster-users] After Centos 6 yum update client
fails to mount glusterfs volume<br>
><br>
> <br>
><br>
> I have an 8 node gluster cluster running 3.6.2.
Yesterday one of our admin ran a yum update on his Centos 6.6
machine, and it updated the gluster client to 3.7.3. (Client
update only on his machine, not the gluster cluster servers).<br>
><br>
> After the update he was not able to mount the gluster
volume. <br>
><br>
> He then removed and reinstalled the 3.6 gluster client,
and he was able to mount the volume again.<br>
><br>
> <br>
><br>
> So to test/confirm, I did the same thing. Prior to the
running the upgrade I was running 3.6.4 glusterfs and
glusterfs-fuse, and I had the mountpoint mounted on my test
server. <br>
><br>
> I ran the yum update glusterfs, it completed
successfully, and I could access the mount. I then unmounted
the gluster mount, and when I tried to mount it, and I
received the following error:<br>
><br>
> Mount failed. Please check the log file for more details.<br>
><br>
> Since I could access the mountpoint, it appears something
has happened in this update to change default behavior from a
client mount request. Any ideas what changes I need to make
to be able to mount the volume?<br>
><br>
> With 3.7 version of client, do you have to specifically
set auth.allow options for volumes?<br>
><br>
> Below is the logfile from the client<br>
><br>
> [2015-08-12 15:47:10.982346] I [MSGID: 100030]
[glusterfsd.c:2301:main] 0-/usr/sbin/glusterfs: Started
running /usr/sbin/glusterfs version 3.7.3 (args:
/usr/sbin/glusterfs --volfile-server=infarchive01
--volfile-id=/archives /media)<br>
><br>
> [2015-08-12 15:47:11.029757] I [MSGID: 101190]
[event-epoll.c:632:event_dispatch_epoll_worker] 0-epoll:
Started thread with index 1<br>
><br>
> [2015-08-12 15:47:11.058367] I [MSGID: 114020]
[client.c:2118:notify] 0-archives-client-0: parent translators
are ready, attempting connect on transport<br>
><br>
> [2015-08-12 15:47:11.058529] I [MSGID: 101190]
[event-epoll.c:632:event_dispatch_epoll_worker] 0-epoll:
Started thread with index 2<br>
><br>
> [2015-08-12 15:47:11.065361] I [MSGID: 114020]
[client.c:2118:notify] 0-archives-client-1: parent translators
are ready, attempting connect on transport<br>
><br>
> [2015-08-12 15:47:11.066220] I
[rpc-clnt.c:1819:rpc_clnt_reconfig] 0-archives-client-0:
changing port to 49152 (from 0)<br>
><br>
> [2015-08-12 15:47:11.073949] I [MSGID: 114057]
[client-handshake.c:1437:select_server_supported_programs]
0-archives-client-0: Using Program GlusterFS 3.3, Num
(1298437), Version (330)<br>
><br>
> [2015-08-12 15:47:11.074260] I [MSGID: 114020]
[client.c:2118:notify] 0-archives-client-2: parent translators
are ready, attempting connect on transport<br>
><br>
> [2015-08-12 15:47:11.075504] W [MSGID: 114043]
[client-handshake.c:1114:client_setvolume_cbk]
0-archives-client-0: failed to set the volume [Permission
denied]<br>
><br>
> [2015-08-12 15:47:11.075671] W [MSGID: 114007]
[client-handshake.c:1143:client_setvolume_cbk]
0-archives-client-0: failed to get 'process-uuid' from reply
dict [Invalid argument]<br>
><br>
> [2015-08-12 15:47:11.075761] E [MSGID: 114044]
[client-handshake.c:1149:client_setvolume_cbk]
0-archives-client-0: SETVOLUME on remote-host failed
[Permission denied]<br>
><br>
> [2015-08-12 15:47:11.075801] I [MSGID: 114049]
[client-handshake.c:1240:client_setvolume_cbk]
0-archives-client-0: sending AUTH_FAILED event<br>
><br>
> [2015-08-12 15:47:11.075840] E
[fuse-bridge.c:5130:notify] 0-fuse: Server authenication
failed. Shutting down.<br>
><br>
> [2015-08-12 15:47:11.075892] I [fuse-bridge.c:5595:fini]
0-fuse: Unmounting '/media'.<br>
><br>
> [2015-08-12 15:47:11.082675] I [MSGID: 114020]
[client.c:2118:notify] 0-archives-client-3: parent translators
are ready, attempting connect on transport<br>
><br>
> [2015-08-12 15:47:11.084889] W
[glusterfsd.c:1219:cleanup_and_exit]
(-->/lib64/libpthread.so.0() [0x3fe5a07a51]
-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xcd) [0x405e4d]
-->/usr/sbin/glusterfs(cleanup_and_exit+0x65) [0x4059b5] )
0-: received signum (15), shutting down<br>
><br>
><br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a moz-do-not-send="true"
href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> <a moz-do-not-send="true"
href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a><o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</body>
</html>