[Bugs] [Bug 1592258] Gluster brick will not come back up online

[bugzilla at redhat.com]

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



--- Comment #4 from stefan.luteijn at kpn.com ---
Some extra information: The issue occurred after the gluster pod crashed due to
out of memory reasons. We found out that after we remove the brick pid file
under /var/run/gluster/vols/<vol_name> on the machine that hosted the offline
brick, we could start the brick succesfully again with gluster volume start
<vol_name> force.

We related this to the below log entries from the brick and glusterd logs (also
provided in the attachments):

brick log:
[2018-06-18 06:55:19.152561] E [socket.c:2369:socket_connect_finish]
0-glusterfs: connection to 172.16.0.4:24007 failed (Connection refused);
disconnecting socket

glusterd log
[2018-06-18 06:57:00.326425] I [glusterd-utils.c:5953:glusterd_brick_start]
0-management: discovered already-running brick
/var/lib/heketi/mounts/vg_ff6390856febea2c9ec2a7fb7d0c1ff9/brick_08f4fd811dc92bbbfbf1872b7a49c67d/brick

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