[Gluster-users] Determining Connected Client Version

[Atin Mukherjee]

On 01/27/2016 09:43 PM, Raghavendra Bhat wrote:
> But, why should client version be a problem when brick-log-level is
> being changed?
Because the check is there in any volume set operation.
> 
> 
> Regards,
> Raghavendra
> 
> On Wed, Jan 27, 2016 at 9:57 AM, Atin Mukherjee
> <atin.mukherjee83 at gmail.com <mailto:atin.mukherjee83 at gmail.com>> wrote:
> 
>     gluster volume status <volname> clients can give you the list of
>     clients connected. By that would be able to scan through all clients
>     and see who is the culprit by checking its op-version.
> 
>     -Atin
>     Sent from one plus one
> 
>     On Jan 27, 2016 8:13 PM, "Marc Eisenbarth" <mr.eisenbarth at gmail.com
>     <mailto:mr.eisenbarth at gmail.com>> wrote:
> 
>         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 <mailto: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
> 
> 
> 
>         _______________________________________________
>         Gluster-users mailing list
>         Gluster-users at gluster.org <mailto:Gluster-users at gluster.org>
>         http://www.gluster.org/mailman/listinfo/gluster-users
> 
> 
>     _______________________________________________
>     Gluster-users mailing list
>     Gluster-users at gluster.org <mailto:Gluster-users at gluster.org>
>     http://www.gluster.org/mailman/listinfo/gluster-users
> 
> 
> 
> 
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>