search for: werthmann

> First, please note that gluster 3.8 is EOL and that 3.8.4 is rather old in > the 3.8 release, 3.8.15 is the current (and probably final) release of 3.8. > > "With the release of GlusterFS-3.12, GlusterFS-3.8 (LTM) and GlusterFS- > 3.11 (STM) have reached EOL. Except for serious security issues no > further updates to these versions are forthcoming. If you find a bug please

...ugs: https://bugzilla.redhat.com/show_bug.cgi?id=1491059 https://bugzilla.redhat.com/show_bug.cgi?id=1491060 The above bugs are filed against 3.10.4. and this post where the OP was running 3.11.2: http://lists.gluster.org/pipermail/gluster-users/2017-September/032433.html Hopes this helps. Ben Werthmann -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170913/79ef0675/attachment.html>

...ing official RHEL rpms from Red Hat Gluster Storage, so support for that should go through your Red Hat subscription. If you are using the community packages, then yes, you want to update to a more current version. Seems like the latest is: 3.8.4-44.el7 Diego On Wed, Sep 20, 2017 at 1:45 PM, Ben Werthmann <ben at apcera.com> wrote: > >> First, please note that gluster 3.8 is EOL and that 3.8.4 is rather old in >> the 3.8 release, 3.8.15 is the current (and probably final) release of 3.8. >> >> "With the release of GlusterFS-3.12, GlusterFS-3.8 (LTM) and >>...

On 13/09/17 20:47, Ben Werthmann wrote: > These symptoms appear to be the same as I've recorded in > this post: > > http://lists.gluster.org/pipermail/gluster-users/2017-September/032435.html > > On Wed, Sep 13, 2017 at 7:01 AM, Atin Mukherjee > <atin.mukherjee83 at gmail.com > <mailto:atin.muk...

...luster Storage, so support for that should go through > your Red Hat subscription. If you are using the community packages, > then yes, you want to update to a more current version. > > Seems like the latest is: 3.8.4-44.el7 > > Diego > > On Wed, Sep 20, 2017 at 1:45 PM, Ben Werthmann <ben at apcera.com> wrote: > > > >> First, please note that gluster 3.8 is EOL and that 3.8.4 is rather old > in > >> the 3.8 release, 3.8.15 is the current (and probably final) release of > 3.8. > >> > >> "With the release of GlusterFS-3.1...

These symptoms appear to be the same as I've recorded in this post: http://lists.gluster.org/pipermail/gluster-users/2017-September/032435.html On Wed, Sep 13, 2017 at 7:01 AM, Atin Mukherjee <atin.mukherjee83 at gmail.com> wrote: > Additionally the brick log file of the same brick would be required. > Please look for if brick process went down or crashed. Doing a volume start

I ran into something like this in 3.10.4 and filed two bugs for it: https://bugzilla.redhat.com/show_bug.cgi?id=1491059 https://bugzilla.redhat.com/show_bug.cgi?id=1491060 Please see the above bugs for full detail. In summary, my issue was related to glusterd's pid handling of pid files when is starts self-heal and bricks. The issues are: a. brick pid file leaves stale pid and brick fails

Additionally the brick log file of the same brick would be required. Please look for if brick process went down or crashed. Doing a volume start force should resolve the issue. On Wed, 13 Sep 2017 at 16:28, Gaurav Yadav <gyadav at redhat.com> wrote: > Please send me the logs as well i.e glusterd.logs and cmd_history.log. > > > On Wed, Sep 13, 2017 at 1:45 PM, lejeczek