<p dir="ltr"><br>
On 29 May 2015 15:42, "Félix de Lelelis" <<a href="mailto:felix.delelisdd@gmail.com">felix.delelisdd@gmail.com</a>> wrote:<br>
><br>
> Hi Atin,<br>
><br>
> I can't upload de sosreport becuase exceed the limit. Where can I upload the file?<br>
In that case could you collect /var/log/glusterd/* and /var/lib/glusterd/* (including .cmd_log_history log which is hidden) of all the nodes and upload and point me to the bug id? I will take a look.<br>
><br>
> Thanks<br>
><br>
> 2015-05-29 10:29 GMT+02:00 Atin Mukherjee <<a href="mailto:atin.mukherjee83@gmail.com">atin.mukherjee83@gmail.com</a>>:<br>
>><br>
>><br>
>> On 29 May 2015 13:29, "Félix de Lelelis" <<a href="mailto:felix.delelisdd@gmail.com">felix.delelisdd@gmail.com</a>> wrote:<br>
>> ><br>
>> > Hi,<br>
>> ><br>
>> > I have a cluster with 3 nodes on pre-production. Yesterday, one node was down. The errror that I have seen is that:<br>
>> ><br>
>> ><br>
>> > [2015-05-28 19:04:27.305560] E [glusterd-syncop.c:1578:gd_sync_task_begin] 0-management: Unable to acquire lock for cfe-gv1<br>
>> > The message "I [MSGID: 106006] [glusterd-handler.c:4257:__glusterd_nodesvc_rpc_notify] 0-management: nfs has disconnected from glusterd." repeated 5 times between [2015-05-28 19:04:09.346088] and [2015-05-28 19:04:24.349191]<br>
>> > pending frames:<br>
>> > frame : type(0) op(0)<br>
>> > patchset: git://<a href="http://git.gluster.com/glusterfs.git">git.gluster.com/glusterfs.git</a><br>
>> > signal received: 11<br>
>> > time of crash:<br>
>> > 2015-05-28 19:04:27<br>
>> > configuration details:<br>
>> > argp 1<br>
>> > backtrace 1<br>
>> > dlfcn 1<br>
>> > libpthread 1<br>
>> > llistxattr 1<br>
>> > setfsid 1<br>
>> > spinlock 1<br>
>> > epoll.h 1<br>
>> > xattr.h 1<br>
>> > st_atim.tv_nsec 1<br>
>> > package-string: glusterfs 3.6.1<br>
>> > /usr/lib64/libglusterfs.so.0(_gf_msg_backtrace_nomem+0xb2)[0x7fd86e2f1232]<br>
>> > /usr/lib64/libglusterfs.so.0(gf_print_trace+0x32d)[0x7fd86e30871d]<br>
>> > /usr/lib64/libc.so.6(+0x35640)[0x7fd86d30c640]<br>
>> > /usr/lib64/glusterfs/3.6.1/xlator/mgmt/glusterd.so(glusterd_remove_pending_entry+0x2c)[0x7fd85f52450c]<br>
>> > /usr/lib64/glusterfs/3.6.1/xlator/mgmt/glusterd.so(+0x5ae28)[0x7fd85f511e28]<br>
>> > /usr/lib64/glusterfs/3.6.1/xlator/mgmt/glusterd.so(glusterd_op_sm+0x237)[0x7fd85f50f027]<br>
>> > /usr/lib64/glusterfs/3.6.1/xlator/mgmt/glusterd.so(__glusterd_brick_op_cbk+0x2fe)[0x7fd85f53be5e]<br>
>> > /usr/lib64/glusterfs/3.6.1/xlator/mgmt/glusterd.so(glusterd_big_locked_cbk+0x4c)[0x7fd85f53d48c]<br>
>> > /usr/lib64/libgfrpc.so.0(rpc_clnt_handle_reply+0x90)[0x7fd86e0c50b0]<br>
>> > /usr/lib64/libgfrpc.so.0(rpc_clnt_notify+0x171)[0x7fd86e0c5321]<br>
>> > /usr/lib64/libgfrpc.so.0(rpc_transport_notify+0x23)[0x7fd86e0c1273]<br>
>> > /usr/lib64/glusterfs/3.6.1/rpc-transport/socket.so(+0x8530)[0x7fd85d17d530]<br>
>> > /usr/lib64/glusterfs/3.6.1/rpc-transport/socket.so(+0xace4)[0x7fd85d17fce4]<br>
>> > /usr/lib64/libglusterfs.so.0(+0x76322)[0x7fd86e346322]<br>
>> > /usr/sbin/glusterd(main+0x502)[0x7fd86e79afb2]<br>
>> > /usr/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fd86d2f8af5]<br>
>> > /usr/sbin/glusterd(+0x6351)[0x7fd86e79b351]<br>
>> > ---------<br>
>> ><br>
>> ><br>
>> > That is a problem with software? is a bug ?<br>
>> This indicates that glusterd crashed, could you raise a bug capturing the sosreport with -a option and attaching it to bugzilla?<br>
>> ><br>
>> > Thanks.<br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Gluster-users mailing list<br>
>> > <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
>> > <a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
><br>
><br>
</p>