Actions
Bug #4425
closedrgw: crash when keystone is used
% Done:
0%
Source:
Support
Tags:
Backport:
Regression:
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
We get the following crash randomly:
ceph version 0.56.3-25-g6483275 (6483275c5678db10d055371227be795cdc63db38) 1: /usr/bin/radosgw() [0x481dda] 2: (()+0xfcb0) [0x7fef04c6fcb0] 3: (gsignal()+0x35) [0x7fef031a6425] 4: (abort()+0x17b) [0x7fef031a9b8b] 5: (()+0x7439e) [0x7fef031e439e] 6: (__fortify_fail()+0x37) [0x7fef0327a807] 7: (()+0x10a77d) [0x7fef0327a77d] 8: (__longjmp_chk()+0x33) [0x7fef0327a6e3] 9: (()+0xca45) [0x7fef050b3a45] 10: (()+0xfcb0) [0x7fef04c6fcb0] 11: (accept()+0x2d) [0x7fef04c6f04d] 12: (OS_Accept()+0x158) [0x7fef03f642c8] 13: (FCGX_Accept_r()+0x9e) [0x7fef03f6223e] 14: (RGWProcess::run()+0x11c) [0x47c37c] 15: (main()+0xa5a) [0x45229a] 16: (__libc_start_main()+0xed) [0x7fef0319176d] 17: /usr/bin/radosgw() [0x453961] NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
(gdb) bt #0 0x00007fef04c6fb7b in raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:42 #1 0x0000000000481f2e in reraise_fatal (signum=6) at global/signal_handler.cc:58 #2 handle_fatal_signal (signum=6) at global/signal_handler.cc:104 #3 <signal handler called> #4 0x00007fef031a6425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #5 0x00007fef031a9b8b in __GI_abort () at abort.c:91 #6 0x00007fef031e439e in __libc_message (do_abort=2, fmt=0x7fef032ebe3f "*** %s ***: %s terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201 #7 0x00007fef0327a807 in __GI___fortify_fail (msg=0x7fef032ebdfe "longjmp causes uninitialized stack frame") at fortify_fail.c:32 #8 0x00007fef0327a77d in ____longjmp_chk () at ../sysdeps/unix/sysv/linux/x86_64/____longjmp_chk.S:90 #9 0x00007fef0327a6e3 in __longjmp_chk (env=0x7fef052fea00, val=<optimized out>) at ../setjmp/longjmp.c:40 #10 0x00007fef050b3a45 in ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 #11 <signal handler called> #12 0x00007fef04c6f04d in accept () at ../sysdeps/unix/syscall-template.S:82 #13 0x00007fef03f642c8 in OS_Accept () from /usr/lib/libfcgi.so.0 #14 0x00007fef03f6223e in FCGX_Accept_r () from /usr/lib/libfcgi.so.0 #15 0x000000000047c37c in RGWProcess::run (this=0x121fae0) at rgw/rgw_main.cc:236 #16 0x000000000045229a in main (argc=<optimized out>, argv=<optimized out>) at rgw/rgw_main.cc:492
Updated by Yehuda Sadeh about 11 years ago
We weren't able to reproduce the issue without keystone, hence we suspect it's related. May be related to the use of libcurl (either to verify tokens, or to retrieve revocation list). Note the following:
Updated by Yehuda Sadeh about 11 years ago
- Status changed from In Progress to Resolved
Fixed, commit:88725316ddcfa02ff110e659f7a8131dc1ea2cfc. Pushed to next and bobtail.
Actions