search for: wingu3

Ouch! Yes, I see two port-related fixes in the GlusterFS 3.12.3 release notes[0][1][2]. I've attached a tarball of all yesterday's logs from /var/log/glusterd on one the affected nodes (called "wingu3"). I hope that's what you need. [0] https://github.com/gluster/glusterfs/blob/release-3.12/doc/release-notes/3.12.3.md [1] https://bugzilla.redhat.com/show_bug.cgi?id=1507747 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1507748 Thanks, On Mon, Jan 22, 2018 at 6:34 AM Atin Mukherjee &...

The patch was definitely there in 3.12.3. Do you have the glusterd and brick logs handy with you when this happened? On Sun, Jan 21, 2018 at 10:21 PM, Alan Orth <alan.orth at gmail.com> wrote: > For what it's worth, I just updated some CentOS 7 servers from GlusterFS > 3.12.1 to 3.12.4 and hit this bug. Did the patch make it into 3.12.4? I had > to use Mike Hulsman's

...5 PM, Alan Orth <alan.orth at gmail.com <mailto:alan.orth at gmail.com> > wrote: Ouch! Yes, I see two port-related fixes in the GlusterFS 3.12.3 release notes[0][1][2]. I've attached a tarball of all yesterday's logs from /var/log/glusterd on one the affected nodes (called "wingu3"). I hope that's what you need. [0] https://github.com/gluster/glusterfs/blob/release-3.12/doc/release-notes/3.12.3.md [1] https://bugzilla.redhat.com/show_bug.cgi?id=1507747 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1507748 ?Thanks, On Mon, Jan 22, 2018 at 6:34 AM Atin Mukherjee...

...on, Jan 22, 2018 at 3:15 PM, Alan Orth <alan.orth at gmail.com> wrote: > Ouch! Yes, I see two port-related fixes in the GlusterFS 3.12.3 release > notes[0][1][2]. I've attached a tarball of all yesterday's logs from > /var/log/glusterd on one the affected nodes (called "wingu3"). I hope > that's what you need. > > [0] https://github.com/gluster/glusterfs/blob/release-3.12/ > doc/release-notes/3.12.3.md > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1507747 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1507748 > > Thanks, > >...

...Jan 22, 2018 at 3:15 PM, Alan Orth <alan.orth at gmail.com> wrote: > > Ouch! Yes, I see two port-related fixes in the GlusterFS 3.12.3 release > notes[0][1][2]. I've attached a tarball of all yesterday's logs from > /var/log/glusterd on one the affected nodes (called "wingu3"). I hope > that's what you need. > > [0] https://github.com/gluster/glusterfs/blob/release-3.12/ > doc/release-notes/3.12.3.md > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1507747 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1507748 > > Thanks, > >...

For what it's worth, I just updated some CentOS 7 servers from GlusterFS 3.12.1 to 3.12.4 and hit this bug. Did the patch make it into 3.12.4? I had to use Mike Hulsman's script to check the daemon port against the port in the volume's brick info, update the port, and restart glusterd on each node. Luckily I only have four servers! Hoping I don't have to do this every time I