On 2/8/19 3:20 AM, Maurits Lamers wrote:
Hi,
[2019-02-07 10:11:24.812606] E [MSGID: 104055]
[glfs-fops.c:4955:glfs_cbk_upcall_data] 0-gfapi: Synctak for Upcall
event_type(1) and gfid(yøêÙ
Mz„–îSL4_@) failed
[2019-02-07 10:11:24.819376] E [MSGID: 104055]
[glfs-fops.c:4955:glfs_cbk_upcall_data] 0-gfapi: Synctak for Upcall
event_type(1) and gfid(eTnôEU«H.<Y4failed
[2019-02-07 10:11:24.833299] E [MSGID: 104055]
[glfs-fops.c:4955:glfs_cbk_upcall_data] 0-gfapi: Synctak for Upcall
event_type(1) and gfid(gÇLÁèFà»0bЯk) failed
[2019-02-07 10:25:01.642509] C
[rpc-clnt-ping.c:166:rpc_clnt_ping_timer_expired] 0-gv0-client-2:
server [node1]:49152 has not responded in the last 42 seconds,
disconnecting.
[2019-02-07 10:25:01.642805] C
[rpc-clnt-ping.c:166:rpc_clnt_ping_timer_expired] 0-gv0-client-1:
server [node2]:49152 has not responded in the last 42 seconds,
disconnecting.
[2019-02-07 10:25:01.642946] C
[rpc-clnt-ping.c:166:rpc_clnt_ping_timer_expired] 0-gv0-client-4:
server [node3]:49152 has not responded in the last 42 seconds,
disconnecting.
[2019-02-07 10:25:02.643120] C
[rpc-clnt-ping.c:166:rpc_clnt_ping_timer_expired] 0-gv0-client-3:
server 127.0.1.1:49152 has not responded in the last 42 seconds,
disconnecting.
[2019-02-07 10:25:02.643314] C
[rpc-clnt-ping.c:166:rpc_clnt_ping_timer_expired] 0-gv0-client-0:
server [node4]:49152 has not responded in the last 42 seconds,
disconnecting.
Strange that synctask failed. Could you please turn off
features.cache-invalidation volume option and check if the issue still
persists.
Turning the cache invalidation option off seems to have solved the
freeze. Still testing, but it looks promising.
If thats the case, please turn on cache invalidation option back and
collect couple of stack traces (using gstack) when the system freezes again.
Thanks,
Soumya
cheers
Maurits
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
