[Bugs] [Bug 1739884] glusterfsd process crashes with SIGSEGV

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1739884



--- Comment #13 from Susant Kumar Palai <spalai at redhat.com> ---
>From the current report, it is not clear which thread crashed and for what
reason.

Please do the following.

# Install gluster-debuginfo package of the same version as your glusterfs
server.

# type the following command into terminal :
   "gdb glusterfsd $core-file" and copy the text from the terminal which should
have the crashed thread bt. It looks something like this.


Core was generated by `/usr/local/sbin/glusterfs --process-name fuse
--volfile-server=vm3 --volfile-id'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f12be8c5d9b in dht_create (frame=0x7f12a4001e48, this=0x0,
loc=0x7f12b8009130, flags=34881, mode=33188, umask=0, fd=0x7f12b8001948,
params=0x7f12ac0020c8) at dht-common.c:8677
8677        conf = this->private;
[Current thread is 1 (Thread 0x7f12ce3ff700 (LWP 30689))]
Missing separate debuginfos, use: dnf debuginfo-install
glibc-2.26-28.fc27.x86_64 openssl-libs-1.1.0h-3.fc27.x86_64
pcre2-10.31-7.fc27.x86_64 sssd-client-1.16.2-4.fc27.x86_64
(gdb) bt
#0  0x00007f12be8c5d9b in dht_create (frame=0x7f12a4001e48, this=0x0,
loc=0x7f12b8009130, flags=34881, mode=33188, umask=0, fd=0x7f12b8001948,
params=0x7f12ac0020c8) at dht-common.c:8677
#1  0x00007f12be633d8a in gf_utime_create (frame=0x7f12a4006cb8,
this=0x7f12b0010b70, loc=0x7f12b8009130, flags=34881, mode=33188, umask=0,
fd=0x7f12b8001948, xdata=0x7f12ac0020c8) at utime-autogen-fops.c:172
#2  0x00007f12ce11b86c in default_create (frame=0x7f12a4006cb8,
this=0x7f12b0012890, loc=0x7f12b8009130, flags=34881, mode=33188, umask=0,
fd=0x7f12b8001948, xdata=0x7f12ac0020c8) at defaults.c:2601
#3  0x00007f12be201846 in ra_create (frame=0x7f12a4001608, this=0x7f12b0014540,
loc=0x7f12b8009130, flags=34881, mode=33188, umask=0, fd=0x7f12b8001948,
xdata=0x7f12ac0020c8) at read-ahead.c:194
#4  0x00007f12ce11b86c in default_create (frame=0x7f12a4001608,
this=0x7f12b0016120, loc=0x7f12b8009130, flags=34881, mode=33188, umask=0,
fd=0x7f12b8001948, xdata=0x7f12ac0020c8) at defaults.c:2601
#5  0x00007f12bddd896f in ioc_create (frame=0x7f12a4008ff8,
this=0x7f12b0018240, loc=0x7f12b8009130, flags=34881, mode=33188, umask=0,
fd=0x7f12b8001948, xdata=0x7f12ac0020c8) at io-cache.c:919
#6  0x00007f12ce11b86c in default_create (frame=0x7f12a4008ff8,
this=0x7f12b0019e30, loc=0x7f12b8009130, flags=34881, mode=33188, umask=0,
fd=0x7f12b8001948, xdata=0x7f12ac0020c8) at defaults.c:2601
#7  0x00007f12ce11b86c in default_create (frame=0x7f12a4008ff8,
this=0x7f12b001ba30, loc=0x7f12b8009130, flags=34881, mode=33188, umask=0,
fd=0x7f12b8001948, xdata=0x7f12ac0020c8) at defaults.c:2601
#8  0x00007f12bd798698 in mdc_create (frame=0x7f12a4000cb8,
this=0x7f12b001d610, loc=0x7f12b8009130, flags=34881, mode=33188, umask=0,
fd=0x7f12b8001948, xdata=0x7f12ac0020c8) at md-cache.c:1969
#9  0x00007f12ce1102ed in default_create_resume (frame=0x7f12b8008328,
this=0x7f12b001f210, loc=0x7f12b8009130, flags=34881, mode=33188, umask=0,
fd=0x7f12b8001948, xdata=0x7f12ac0020c8) at defaults.c:1873
#10 0x00007f12ce05fbf8 in call_resume_wind (stub=0x7f12b80090e8) at
call-stub.c:2033
#11 0x00007f12ce071bee in call_resume (stub=0x7f12b80090e8) at call-stub.c:2555
#12 0x00007f12bd5809c6 in iot_worker (data=0x7f12b002efc0) at io-threads.c:232
#13 0x00007f12ccbf550b in start_thread () from /lib64/libpthread.so.0
#14 0x00007f12cc4a516f in clone () from /lib64/libc.so.6


And then get another report with "thread apply all bt". 

Once we check that info we will figure out the next steps.

Regards,
Susant

-- 
You are receiving this mail because:
You are on the CC list for the bug.