Hi Kaleb,
Sorry... here is the version from the other machine. Both have the same version.
[root@conv-gls002 glusterfs]# gluster --version
glusterfs 3.7.6 built on Nov 9 2015 15:20:26
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.
Regards,
Surya Ghatty
"This too shall pass"
________________________________________________________________________________________________________
Surya Ghatty | Software Engineer | IBM Cloud Infrastructure Services Development | tel: (507) 316-0559 | ghatty@xxxxxxxxxx
Kaleb KEITHLEY ---11/17/2015 08:25:49 AM---On 11/17/2015 09:08 AM, Surya K Ghatty wrote: > Hi:
From: Kaleb KEITHLEY <kkeithle@xxxxxxxxxx>
To: Surya K Ghatty/Rochester/IBM@IBMUS, gluster-users@xxxxxxxxxxx
Date: 11/17/2015 08:25 AM
Subject: Re: [Gluster-users] vol set <volname> ganesha.enable errors out
On 11/17/2015 09:08 AM, Surya K Ghatty wrote:
> Hi:
>
> I am running into the following error when trying to enable ganesha on
> my system. This seems to be the same message as the one here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1004332.
>
> [root@conv-gls002 ~]# gluster volume set gvol0 ganesha.enable on
> volume set: failed: Staging failed on gluster1. Error: One or more
> connected clients cannot support the feature being set. These clients
> need to be upgraded or disconnected before running this command again
Some "client" — client usually means a gluster fuse client mount, or a
gfapi client like the nfs-ganesha server — isn't using 3.7.x.
Based on what I think your setup is that seems really unlikely. But see
my comment/question at the end.
>
> However, I can execute some of the other gluster vol set commands.
>
> Here is the log:
> [2015-11-17 13:51:48.629507] E [MSGID: 106289]
> [glusterd-syncop.c:1871:gd_sync_task_begin] 0-management: Failed to
> build payload for operation 'Volume Set'
> [2015-11-17 13:51:56.698145] E [MSGID: 106022]
> [glusterd-utils.c:10154:glusterd_check_client_op_version_support]
> 0-management: One or more clients don't support the required op-version
> [2015-11-17 13:51:56.698193] E [MSGID: 106301]
> [glusterd-syncop.c:1274:gd_stage_op_phase] 0-management: Staging of
> operation 'Volume Set' failed on localhost : One or more connected
> clients cannot support the feature being set. These clients need to be
> upgraded or disconnected before running this command again
> [2015-11-17 13:54:32.759969] E [MSGID: 106022]
> [glusterd-utils.c:10154:glusterd_check_client_op_version_support]
> 0-management: One or more clients don't support the required op-version
> [2015-11-17 13:54:32.760017] E [MSGID: 106301]
> [glusterd-syncop.c:1274:gd_stage_op_phase] 0-management: Staging of
> operation 'Volume Set' failed on localhost : One or more connected
> clients cannot support the feature being set. These clients need to be
> upgraded or disconnected before running this command again
> [2015-11-17 13:55:15.930722] E [MSGID: 106022]
> [glusterd-utils.c:10154:glusterd_check_client_op_version_support]
> 0-management: One or more clients don't support the required op-version
> [2015-11-17 13:55:15.930733] E [MSGID: 106301]
> [glusterd-syncop.c:1274:gd_stage_op_phase] 0-management: Staging of
> operation 'Volume Set' failed on localhost : One or more connected
> clients cannot support the feature being set. These clients need to be
> upgraded or disconnected before running this command again
>
>
> The work around seems to upgrade the "clients" to a certain level or
> disconnect them. What client is this message referring to? I am running
> in a HA mode, and have two glusterfs nodes. Both have gluster at the
> same level. (3.7.6). There are no lingering mounts, as far as I can tell.
>
> [root@conv-gls001 glusterfs]# gluster --version
> glusterfs 3.7.6 built on Nov 9 2015 15:20:26
> ...
> [root@conv-gls001 ~]# gluster --version
> glusterfs 3.7.6 built on Nov 9 2015 15:20:26
These look like the same machine, i.e. conv-gls001. Is that really
correct? Let's'see the output from the _other_ machine.
--
Kaleb
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
