[Bugs] [Bug 1486134] glusterfsd (brick) process crashed

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1486134



--- Comment #1 from Raghavendra G <rgowdapp at redhat.com> ---

Description of problem:

glusterfsd brick process crashed. Unfortunately core file limit was set to 0 on
that node. So core file is not available.

Below is the backtrace of the crash
[2017-08-17 19:01:08.790160] I [MSGID: 115013]
[server-helpers.c:294:do_fd_cleanup] 0-dv_repo-server: fd cleanup on /
pending frames:
frame : type(0) op(27)
frame : type(0) op(27)
frame : type(0) op(27)
frame : type(0) op(27)
patchset: git://git.gluster.com/glusterfs.git
signal received: 6
time of crash:
2017-08-17 19:01:08
configuration details:
argp 1
backtrace 1
dlfcn 1
libpthread 1
llistxattr 1
setfsid 1
spinlock 1
epoll.h 1
xattr.h 1
st_atim.tv_nsec 1
package-string: glusterfs 3.7.1
[2017-08-17 19:01:08.790499] E [server.c:200:server_submit_reply] (-->
/lib64/libglusterfs.so.0(_gf_log_callingfn+0x186)[0x7fac3ee299d6] (-->
/usr/lib64/glusterfs/3.7.1/xlator/protocol/server
.so(server_submit_reply+0x2ee)[0x7fac34c6a02e] (-->
/usr/lib64/glusterfs/3.7.1/xlator/protocol/server.so(server_lookup_cbk+0x55c)[0x7fac34c8641c]
(--> /usr/lib64/glusterfs/3.7.1/xlator/debug/
io-stats.so(io_stats_lookup_cbk+0x154)[0x7fac34eaa6f4] (-->
/lib64/libglusterfs.so.0(default_lookup_cbk+0xde)[0x7fac3ee2da4e] ))))) 0-:
Reply submission failed
[2017-08-17 19:01:08.790536] E [server.c:200:server_submit_reply] (-->
/lib64/libglusterfs.so.0(_gf_log_callingfn+0x186)[0x7fac3ee299d6] (-->
/usr/lib64/glusterfs/3.7.1/xlator/protocol/server
.so(server_submit_reply+0x2ee)[0x7fac34c6a02e] (-->
/usr/lib64/glusterfs/3.7.1/xlator/protocol/server.so(server_lookup_cbk+0x55c)[0x7fac34c8641c]
(--> /usr/lib64/glusterfs/3.7.1/xlator/debug/
io-stats.so(io_stats_lookup_cbk+0x154)[0x7fac34eaa6f4] (-->
/lib64/libglusterfs.so.0(default_lookup_cbk+0xde)[0x7fac3ee2da4e] ))))) 0-:
Reply submission failed
/lib64/libglusterfs.so.0(_gf_msg_backtrace_nomem+0xb2)[0x7fac3ee27f62]
/lib64/libglusterfs.so.0(gf_print_trace+0x32d)[0x7fac3ee463ed]
/lib64/libc.so.6(+0x35250)[0x7fac3d515250]
/lib64/libc.so.6(gsignal+0x37)[0x7fac3d5151d7]
/lib64/libc.so.6(abort+0x148)[0x7fac3d5168c8]
/lib64/libc.so.6(+0x2e146)[0x7fac3d50e146]
/lib64/libc.so.6(+0x2e1f2)[0x7fac3d50e1f2]
/lib64/libglusterfs.so.0(+0x8a072)[0x7fac3ee8c072]
/usr/lib64/glusterfs/3.7.1/rpc-transport/socket.so(+0x3814)[0x7fac39fbc814]
/usr/lib64/glusterfs/3.7.1/rpc-transport/socket.so(+0xba18)[0x7fac39fc4a18]
/lib64/libglusterfs.so.0(+0x8a77a)[0x7fac3ee8c77a]
/lib64/libpthread.so.0(+0x7dc5)[0x7fac3dc90dc5]
/lib64/libc.so.6(clone+0x6d)[0x7fac3d5d776d]
---------

Version-Release number of selected component (if applicable):

glusterfs-3.7.1-11

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.