<p dir="ltr">Hi,</p>
<p dir="ltr">After a hardware maintenance (GPU removed) I have powered my oVirt node running gluster 5.5 and noticed that one volume has no running brick locally.</p>
<p dir="ltr">After forcefully starting the volume, the brick is up but almost instantly I got the following on my CentOS 7 terminal.<br>
================================</p>
<p dir="ltr">[root@ovirt2 ~]# gluster volume heal isos full<br>
Broadcast message from systemd-journald@ovirt2.localdomain (Sun 2019-04-07 16:41:30 EEST):</p>
<p dir="ltr">gluster_bricks-isos-isos[6884]: [2019-04-07 13:41:30.148365] M [MSGID: 113075] [posix-helpers.c:1957:posix_health_check_thread_proc] 0-isos-posix: health-check failed, going down<br></p>
<p dir="ltr">Broadcast message from systemd-journald@ovirt2.localdomain (Sun 2019-04-07 16:41:30 EEST):</p>
<p dir="ltr">gluster_bricks-isos-isos[6884]: [2019-04-07 13:41:30.148934] M [MSGID: 113075] [posix-helpers.c:1975:posix_health_check_thread_proc] 0-isos-posix: still alive! -> SIGTERM<br></p>
<p dir="ltr">Message from syslogd@ovirt2 at Apr 7 16:41:30 ...<br>
gluster_bricks-isos-isos[6884]:[2019-04-07 13:41:30.148365] M [MSGID: 113075] [posix-helpers.c:1957:posix_health_check_thread_proc] 0-isos-posix: health-check failed, going down</p>
<p dir="ltr">Message from syslogd@ovirt2 at Apr 7 16:41:30 ...<br>
gluster_bricks-isos-isos[6884]:[2019-04-07 13:41:30.148934] M [MSGID: 113075] [posix-helpers.c:1975:posix_health_check_thread_proc] 0-isos-posix: still alive! -> SIGTERM</p>
<p dir="ltr">================================</p>
<p dir="ltr">Restarting glusterd.service didn't help.<br>
How should I debug it ?</p>
<p dir="ltr">Best Regards,<br>
Strahil Nikolov</p>