<div dir="ltr">But, why should client version be a problem when brick-log-level is being changed?<div><br></div><div><br></div><div>Regards,</div><div>Raghavendra</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 27, 2016 at 9:57 AM, Atin Mukherjee <span dir="ltr"><<a href="mailto:atin.mukherjee83@gmail.com" target="_blank">atin.mukherjee83@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">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.</p>
<p dir="ltr">-Atin<br>
Sent from one plus one</p>
<div class="gmail_quote"><div><div class="h5">On Jan 27, 2016 8:13 PM, "Marc Eisenbarth" <<a href="mailto:mr.eisenbarth@gmail.com" target="_blank">mr.eisenbarth@gmail.com</a>> wrote:<br type="attribution"></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Unfortunately, I don't have any of these messages and I'm stuck in a bit of a loop here:<div>
<p><span>$ sudo gluster volume get backup diagnostics.brick-log-level</span></p>
<p><span>Option Value </span></p>
<p><span>------ ----- </span></p>
<p><span>diagnostics.brick-log-level WARNING </span></p>
<p>$ sudo gluster volume set backup diagnostics.brick-log-level INFO<br></p>
<p><span>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</span></p>
<p>Perhaps something else is going on here?</p></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 26, 2016 at 5:51 PM, Vijay Bellur <span dir="ltr"><<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 01/26/2016 01:19 PM, Marc Eisenbarth wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm trying to set a parameter on a volume, but unable to due to the<br>
following message. I have a large number of connected clients and it's<br>
likely that some clients have updated packages but haven't remounted the<br>
volume. Is there an easier way to find the offending client?<br>
<br>
</blockquote>
<br></span>
You could grep for "accepted client from" in /var/log/glusterfs/bricks to get an idea of the versions of connected clients.<br>
<br>
HTH,<br>
Vijay<br>
<br>
</blockquote></div><br></div>
<br></div></div><span class="">_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br></span></blockquote></div>
<br>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br></blockquote></div><br></div>