Grep for "backtrace" in /var/log/glusterfs, that should give you a particular log file name by which you can determine which process crashed. You should also be able to see a coredump. Why don't you attach the same for further analysis?
~Atin On Mon, Jun 27, 2016 at 1:17 PM, Yann LEMARIE <[email protected]> wrote: > Hi, > > I'm using GlusterFS since many years and never see this problem, but this > is the second time in one week ... > > I have 3 volumes with 2 bricks and 1 volume crash with no reason, I just > have to stop/start the volume to make it up again. > The only logs I can find are in syslog : > > Jun 26 11:27:44 nfs05 srv-cdn[7879]: pending frames: > Jun 26 11:27:44 nfs05 srv-cdn[7879]: frame : type(0) op(10) > Jun 26 11:27:44 nfs05 srv-cdn[7879]: patchset: git:// > git.gluster.com/glusterfs.git > Jun 26 11:27:44 nfs05 srv-cdn[7879]: signal received: 11 > Jun 26 11:27:44 nfs05 srv-cdn[7879]: time of crash: > Jun 26 11:27:44 nfs05 srv-cdn[7879]: 2016-06-26 09:27:44 > Jun 26 11:27:44 nfs05 srv-cdn[7879]: configuration details: > Jun 26 11:27:44 nfs05 srv-cdn[7879]: argp 1 > Jun 26 11:27:44 nfs05 srv-cdn[7879]: backtrace 1 > Jun 26 11:27:44 nfs05 srv-cdn[7879]: dlfcn 1 > Jun 26 11:27:44 nfs05 srv-cdn[7879]: libpthread 1 > Jun 26 11:27:44 nfs05 srv-cdn[7879]: llistxattr 1 > Jun 26 11:27:44 nfs05 srv-cdn[7879]: setfsid 1 > Jun 26 11:27:44 nfs05 srv-cdn[7879]: spinlock 1 > Jun 26 11:27:44 nfs05 srv-cdn[7879]: epoll.h 1 > Jun 26 11:27:44 nfs05 srv-cdn[7879]: xattr.h 1 > Jun 26 11:27:44 nfs05 srv-cdn[7879]: st_atim.tv_nsec 1 > Jun 26 11:27:44 nfs05 srv-cdn[7879]: package-string: glusterfs 3.7.11 > Jun 26 11:27:44 nfs05 srv-cdn[7879]: --------- > > Jun 26 11:27:44 nfs06 srv-cdn[1787]: pending frames: > Jun 26 11:27:44 nfs06 srv-cdn[1787]: frame : type(0) op(10) > Jun 26 11:27:44 nfs06 srv-cdn[1787]: patchset: git:// > git.gluster.com/glusterfs.git > Jun 26 11:27:44 nfs06 srv-cdn[1787]: signal received: 11 > Jun 26 11:27:44 nfs06 srv-cdn[1787]: time of crash: > Jun 26 11:27:44 nfs06 srv-cdn[1787]: 2016-06-26 09:27:44 > Jun 26 11:27:44 nfs06 srv-cdn[1787]: configuration details: > Jun 26 11:27:44 nfs06 srv-cdn[1787]: argp 1 > Jun 26 11:27:44 nfs06 srv-cdn[1787]: backtrace 1 > Jun 26 11:27:44 nfs06 srv-cdn[1787]: dlfcn 1 > Jun 26 11:27:44 nfs06 srv-cdn[1787]: libpthread 1 > Jun 26 11:27:44 nfs06 srv-cdn[1787]: llistxattr 1 > Jun 26 11:27:44 nfs06 srv-cdn[1787]: setfsid 1 > Jun 26 11:27:44 nfs06 srv-cdn[1787]: spinlock 1 > Jun 26 11:27:44 nfs06 srv-cdn[1787]: epoll.h 1 > Jun 26 11:27:44 nfs06 srv-cdn[1787]: xattr.h 1 > Jun 26 11:27:44 nfs06 srv-cdn[1787]: st_atim.tv_nsec 1 > Jun 26 11:27:44 nfs06 srv-cdn[1787]: package-string: glusterfs 3.7.11 > Jun 26 11:27:44 nfs06 srv-cdn[1787]: --------- > > > Thanks for your help > > > Regards > -- > Yann Lemarié > iRaiser - Support Technique > [image: iRaiser Logotype] <http://www.iraiser.eu> > <[email protected]>[email protected] > > _______________________________________________ > Gluster-users mailing list > [email protected] > http://www.gluster.org/mailman/listinfo/gluster-users >
_______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
