Hi
This morning i noticed that in one of the servers glusterfsd
daemon was not working, the last log entries were:
patchset: v2.0.4
signal received: 11
configuration details:argp 1
backtrace 1
bdb->cursor->get 1
db.h 1
dlfcn 1
fdatasync 1
libpthread 1
llistxattr 1
setfsid 1
spinlock 1
epoll.h 1
xattr.h 1
st_atim.tv_nsec 1
package-string: glusterfs 2.0.4
/lib/libc.so.6[0x7ff43f926db0]
/usr/lib/glusterfs/2.0.4/xlator/cluster/unify.so(unify_open+0xd8)[0x7ff43ecd40a8]
/usr/lib/glusterfs/2.0.4/xlator/features/locks.so(pl_open+0xc5)[0x7ff43eac6945]
/usr/lib/glusterfs/2.0.4/xlator/performance/io-threads.so(iot_open_wrapper+0xc0)[0x7ff43e8bc850]
/usr/lib/libglusterfs.so.0(call_resume+0x551)[0x7ff440083ac1]
/usr/lib/glusterfs/2.0.4/xlator/performance/io-threads.so(iot_worker_unordered+0x18)[0x7ff43e8baea8]
/lib/libpthread.so.0[0x7ff43fc4cf9a]
/lib/libc.so.6(clone+0x6d)[0x7ff43f9c156d]
Looks like it segfaulted, is this a known bug solved in any recent
version ?
--
Thanx & best regards ...
----------------------------------------------------------------
David Saez Padros http://www.ols.es
On-Line Services 2000 S.L. telf +34 902 50 29 75
----------------------------------------------------------------
David Saez Padros wrote:> patchset: v2.0.4 > signal received: 11 > configuration details:argp 1 > backtrace 1 > bdb->cursor->get 1 > db.h 1 > dlfcn 1 > fdatasync 1 > libpthread 1 > llistxattr 1 > setfsid 1 > spinlock 1 > epoll.h 1 > xattr.h 1 > st_atim.tv_nsec 1 > package-string: glusterfs 2.0.4 > /lib/libc.so.6[0x7ff43f926db0] > /usr/lib/glusterfs/2.0.4/xlator/cluster/unify.so(unify_open+0xd8)[0x7ff43ecd40a8] > > /usr/lib/glusterfs/2.0.4/xlator/features/locks.so(pl_open+0xc5)[0x7ff43eac6945] > > /usr/lib/glusterfs/2.0.4/xlator/performance/io-threads.so(iot_open_wrapper+0xc0)[0x7ff43e8bc850] > > /usr/lib/libglusterfs.so.0(call_resume+0x551)[0x7ff440083ac1] > /usr/lib/glusterfs/2.0.4/xlator/performance/io-threads.so(iot_worker_unordered+0x18)[0x7ff43e8baea8] > > /lib/libpthread.so.0[0x7ff43fc4cf9a] > /lib/libc.so.6(clone+0x6d)[0x7ff43f9c156d] > > Looks like it segfaulted, is this a known bug solved in any recent > version ? >This does not look like a known issue. If you have the core file, can you please send the complete backtrace across? Thanks, Vijay