Hi,
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.
After forcefully starting the volume, the brick is up but almost instantly I got the following on my CentOS 7 terminal.
================================
[root@ovirt2 ~]# gluster volume heal isos full
Broadcast message from systemd-journald@ovirt2.localdomain (Sun 2019-04-07 16:41:30 EEST):
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
Broadcast message from systemd-journald@ovirt2.localdomain (Sun 2019-04-07 16:41:30 EEST):
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
Message from syslogd@ovirt2 at Apr 7 16:41:30 ...
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
Message from syslogd@ovirt2 at Apr 7 16:41:30 ...
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
================================
Restarting glusterd.service didn't help.
How should I debug it ?
Best Regards,
Strahil Nikolov
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
