Andrey,
can you also send along the server side spec file? if you still have the
core is it possible to get the output of 'p *prev' from gdb?
thanks,
avati
2007/6/15, NovA <av.nova@xxxxxxxxx>:
Hello everybody!
After working a couple of weeks, glusterfsd has died today on one node
of my unify GlusterFS (9 bricks). The version is
glusterfs--mainline--2.4 patch-163. Here there are some info...
server.log
--------
[Jun 15 09:22:59] [CRITICAL/common-utils.c:215/gf_print_trace()]
debug-backtrace:Got signal (11), printing backtrace
[Jun 15 09:22:59] [CRITICAL/common-utils.c:217/gf_print_trace()]
debug-backtrace:/usr/lib64/libglusterfs.so.0(gf_print_trace+0x21)
[0x2ada4c81cf71]
[Jun 15 09:22:59] [CRITICAL/common-utils.c:217/gf_print_trace()]
debug-backtrace:/lib64/libc.so.6 [0x2ada4d2945b0]
[Jun 15 09:22:59] [CRITICAL/common-utils.c:217/gf_print_trace()]
debug-backtrace:/usr/lib64/libglusterfs.so.0(dict_destroy+0x30)
[0x2ada4c817d60]
[Jun 15 09:22:59] [CRITICAL/common-utils.c:217/gf_print_trace()]
debug-backtrace:/usr/lib64/glusterfs/1.3.0-pre3/xlator/protocol/server.so
[0x2aaaab0be69f]
[Jun 15 09:22:59] [CRITICAL/common-utils.c:217/gf_print_trace()]
debug-backtrace:/usr/lib64/libglusterfs.so.0(sys_epoll_iteration+0xd4)
[0x2ada4c81e7e4]
[Jun 15 09:22:59] [CRITICAL/common-utils.c:217/gf_print_trace()]
debug-backtrace:[glusterfsd] [0x40164c]
[Jun 15 09:22:59] [CRITICAL/common-utils.c:217/gf_print_trace()]
debug-backtrace:/lib64/libc.so.6(__libc_start_main+0xf4)
[0x2ada4d281ae4]
[Jun 15 09:22:59] [CRITICAL/common-utils.c:217/gf_print_trace()]
debug-backtrace:[glusterfsd] [0x401149]
[Jun 15 09:22:59] [CRITICAL/common-utils.c:215/gf_print_trace()]
debug-backtrace:Got signal (11), printing backtrace
--------
core dump backtrace:
-------
Program terminated with signal 11, Segmentation fault.
#0 dict_destroy (this=0x2aaab0000f70) at dict.c:251
251 data_unref (prev->value);
(gdb) bt
#0 dict_destroy (this=0x2aaab0000f70) at dict.c:251
#1 0x00002aaaab0be69f in proto_srv_notify (this=<value optimized
out>, trans=0x612340, event=1)
at proto-srv.c:2781
#2 0x00002ada4c81e7e4 in sys_epoll_iteration (ctx=0x7fff5e4b1ee0) at
epoll.c:53
#3 0x000000000040164c in main (argc=7, argv=0x7fff5e4b2078) at
glusterfsd.c:288
---------
Hope this helps to locate a posible bug. But I have to note, that this
crash can be caused by some hardware malfunction due to overheating
(although anything else works fine)...
With best regards,
Andrey
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel
--
Anand V. Avati
