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

Vijay Bellur vbellur at redhat.com
Sat May 9 07:22:33 UTC 2015


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




More information about the Gluster-devel mailing list