[Bugs] [Bug 1574974] New: Brick will not start after service restart or system reboot

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1574974

            Bug ID: 1574974
           Summary: Brick will not start after service restart or system
                    reboot
           Product: GlusterFS
           Version: 3.12
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: ryan at magenta.tv
                CC: bugs at gluster.org



Created attachment 1431320
  --> https://bugzilla.redhat.com/attachment.cgi?id=1431320&action=edit
glusterd log

Description of problem:
After restarting the 'glusterfsd' and 'glusterd' services, 80% of the time, the
brick will not come back online. After running 'glusterd --debug' the brick
service starts correctly.

Log files attached. I'm noticing these lines, but am unsure on the cause:
[2018-05-04 12:44:01.557104] I [MSGID: 106143]
[glusterd-pmap.c:295:pmap_registry_bind] 0-pmap: adding brick /mnt/h1a/data on
port 49152
[2018-05-04 12:44:01.558314] I [MSGID: 106144]
[glusterd-pmap.c:396:pmap_registry_remove] 0-pmap: removing brick (null) on
port 49152
[2018-05-04 12:44:01.558385] W [socket.c:593:__socket_rwv] 0-management: readv
on /var/run/gluster/ca39474c70ff91cb2cde5cc5d5551022.socket failed (No data
available)

OS: Fedora Server 27
Gluster version: 3.12.9

Two node setup, issue also occurs in a single node cluster.

Version-Release number of selected component (if applicable):
 3.12.9

How reproducible:
Intermittent / 80%

Steps to Reproduce:
1. Create volume
2. restart glusterfsd and glusterd services
3. Repeat step 2 until issue occurs

Actual results:
Brick stays offline

Expected results:
Brick should be online

Additional info:
This occurs after reboot too

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.