On 01/26/2016 01:19 PM, Marc Eisenbarth wrote:> I'm trying to set a parameter on a volume, but unable to due to the > following message. I have a large number of connected clients and it's > likely that some clients have updated packages but haven't remounted the > volume. Is there an easier way to find the offending client? >You could grep for "accepted client from" in /var/log/glusterfs/bricks to get an idea of the versions of connected clients. HTH, Vijay
On 01/27/2016 07:21 AM, Vijay Bellur wrote:> On 01/26/2016 01:19 PM, Marc Eisenbarth wrote: >> I'm trying to set a parameter on a volume, but unable to due to the >> following message. I have a large number of connected clients and it's >> likely that some clients have updated packages but haven't remounted the >> volume. Is there an easier way to find the offending client? >> > > You could grep for "accepted client from" in /var/log/glusterfs/bricks > to get an idea of the versions of connected clients.I had sent a patch [1] to improve the error message to indicate which client is the culprit here. This is not the first time I've heard an user complaining about it, so will try to get it in the release stream. Anyone up for review? [1] http://review.gluster.org/#/c/11831/> > HTH, > Vijay > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users >
Marc Eisenbarth
2016-Jan-27 14:43 UTC
[Gluster-users] Determining Connected Client Version
Unfortunately, I don't have any of these messages and I'm stuck in a bit of a loop here: $ sudo gluster volume get backup diagnostics.brick-log-level Option Value ------ ----- diagnostics.brick-log-level WARNING $ sudo gluster volume set backup diagnostics.brick-log-level INFO volume set: failed: One or more connected clients cannot support the feature being set. These clients need to be upgraded or disconnected before running this command again Perhaps something else is going on here? On Tue, Jan 26, 2016 at 5:51 PM, Vijay Bellur <vbellur at redhat.com> wrote:> On 01/26/2016 01:19 PM, Marc Eisenbarth wrote: > >> I'm trying to set a parameter on a volume, but unable to due to the >> following message. I have a large number of connected clients and it's >> likely that some clients have updated packages but haven't remounted the >> volume. Is there an easier way to find the offending client? >> >> > You could grep for "accepted client from" in /var/log/glusterfs/bricks to > get an idea of the versions of connected clients. > > HTH, > Vijay > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160127/944aeef9/attachment.html>