[Gluster-devel] regression: brick crashed because of changelog xlator init failure

[Kotresh Hiremath Ravishankar]

It is crashing in libgcc!!!

Program terminated with signal 11, Segmentation fault.
#0  0x00007ff5555a1867 in ?? () from ./lib64/libgcc_s.so.1
Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.149.el6_6.7.x86_64 keyutils-libs-1.4-5.el6.x86_64 krb5-libs-1.10.3-37.el6_6.x86_64 libcom_err-1.41.12-21.el6.x86_64 libgcc-4.4.7-11.el6.x86_64 libselinux-2.0.94-5.8.el6.x86_64 openssl-1.0.1e-30.el6.8.x86_64 zlib-1.2.3-29.el6.x86_64
(gdb) bt
#0  0x00007ff5555a1867 in ?? () from ./lib64/libgcc_s.so.1
#1  0x00007ff5555a2119 in _Unwind_Backtrace () from ./lib64/libgcc_s.so.1
#2  0x00007ff56170b8f6 in backtrace () from ./lib64/libc.so.6
#3  0x00007ff562826544 in _gf_msg_backtrace_nomem (level=GF_LOG_ALERT, stacksize=200)
    at /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/libglusterfs/src/logging.c:1097
#4  0x00007ff562845b82 in gf_print_trace (signum=11, ctx=0xabc010)
    at /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/libglusterfs/src/common-utils.c:618
#5  0x0000000000409646 in glusterfsd_print_trace (signum=11) at /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/glusterfsd/src/glusterfsd.c:2007
#6  <signal handler called>
#7  0x00007ff554484fa9 in ?? ()
#8  0x00007ff561d8b9d1 in start_thread () from ./lib64/libpthread.so.0
#9  0x00007ff5616f58fd in clone () from ./lib64/libc.so.6


Thanks and Regards,
Kotresh H R

----- Original Message -----
> From: "Vijay Bellur" <vbellur at redhat.com>
> To: "Kotresh Hiremath Ravishankar" <khiremat at redhat.com>, "Pranith Kumar Karampuri" <pkarampu at redhat.com>
> Cc: "Gluster Devel" <gluster-devel at gluster.org>
> Sent: Saturday, May 9, 2015 12:52:33 PM
> Subject: Re: [Gluster-devel] regression: brick crashed because of changelog xlator init failure
> 
> On 05/09/2015 12:49 PM, Kotresh Hiremath Ravishankar wrote:
> > If you observe the logs below. Socket binding failed because of Address and
> > port already in use ERROR.
> > Because of that changelog failed to initiate rpc server, hence failed.
> > Not sure why socket binding failed in this machine.
> >
> > [2015-05-08 21:34:47.747059] E [socket.c:823:__socket_server_bind]
> > 0-socket.patchy-changelog: binding to  failed: Address already in use
> > [2015-05-08 21:34:47.747078] E [socket.c:826:__socket_server_bind]
> > 0-socket.patchy-changelog: Port is already in use
> > [2015-05-08 21:34:47.747096] W [rpcsvc.c:1602:rpcsvc_transport_create]
> > 0-rpc-service: listening on transport failed
> > [2015-05-08 21:34:47.747197] I [mem-pool.c:587:mem_pool_destroy]
> > 0-patchy-changelog: size=116 max=0 total=0
> > [2015-05-08 21:34:47.750460] E [xlator.c:426:xlator_init]
> > 0-patchy-changelog: Initialization of volume 'patchy-changelog' failed,
> > review your volfile again
> > [2015-05-08 21:34:47.750485] E [graph.c:322:glusterfs_graph_init]
> > 0-patchy-changelog: initializing translator failed
> > [2015-05-08 21:34:47.750497] E [graph.c:661:glusterfs_graph_activate]
> > 0-graph: init failed
> > [2015-05-08 21:34:47.749020] I
> > [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread
> > with index 2
> 
> Irrespective of a socket bind failing, we should not crash. any ideas
> why glusterfsd crashed?
> 
> -Vijay
> 
> 
>