Hello All We’ve have a problem with cluster client mounts fail in mid run with this in the log glusterfsd.c:1332:cleanup_and_exit] (-->/lib64/libpthread.so.0(+0x7dc5) [0x7f640c8b3dc5] -->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xe5) [0x7f640df4bfd5] -->/usr/sbin/glusterfs(cleanup_and_exit+0x6b) [0x7f640df4bdfb] ) 0-: received signum (15), shutting down. We’ve tried running debug but have not found anything suspicious happening at the time of the failures We’ve searched the inter web but can not find anyone else having the same problem in mid flight The clients have four mounts of volumes from the same server, all mounts fail simultaneously Peer status looks ok Volume status looks ok Volume info looks like this: Volume Name: GLUSTERVOLUME Type: Replicate Volume ID: ca7af017-4f0f-44cc-baf6-43168eed0748 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: GLUSTERSERVER1:/gluster/GLUSTERVOLUME/brick Brick2: GLUSTERSERVER2:/gluster/GLUSTERVOLUME/brick Options Reconfigured: transport.address-family: inet cluster.self-heal-daemon: enable nfs.disable: on server.allow-insecure: on client.bind-insecure: on network.ping-timeout: 5 features.bitrot: on features.scrub: Active features.scrub-freq: weekly Any ideas? Cheers Gabbe AB SVENSKA SPEL 621 80 Visby Norra Hansegatan 17, Visby Växel: +4610-120 00 00 https://svenskaspel.se Please consider the environment before printing this email _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
