Actions
Bug #13421
closedceph-osd Segmentation fault in pthread_join
Status:
Won't Fix
Priority:
Normal
Assignee:
-
Category:
OSD
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Description
OS is CentOS 7, ceph version is giant.
2015-08-31 14:11:24.017514 7f9ee8dfe900 -1 *** Caught signal (Segmentation fault) ** in thread 7f9ee8dfe900 ceph version 0.87.2 (87a7cec9ab11c677de2ab23a7668a77d2f5b955e) 1: /usr/bin/ceph-osd() [0xaba672] 2: (()+0xf130) [0x7f9ee752a130] 3: (pthread_join()+0xa7) [0x7f9ee7523f37] 4: (Thread::join(void**)+0x12) [0xb8ce82] 5: (DispatchQueue::wait()+0x12) [0xc53022] 6: (SimpleMessenger::wait()+0x9a6) [0xb81676] 7: (main()+0x252c) [0x6393fc] 8: (__libc_start_main()+0xf5) [0x7f9ee5f30b25] 9: /usr/bin/ceph-osd() [0x651db9] NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
Files
Updated by Loïc Dachary over 8 years ago
- Status changed from New to Won't Fix
I'm closing this because giant is no longer supported. If you think this bug is not giant specific, please let me know and I'll take a closer look. Thanks :-)
Updated by Brad Hubbard about 8 years ago
- Status changed from Won't Fix to Need More Info
- Release deleted (
giant) - Release set to hammer
- Affected Versions v0.94 added
This has been seen in a mon on Hammer.
0> 2016-02-12 23:23:28.169430 7f88a84f97c0 -1 ** Caught signal (Aborted) *
in thread 7f88a84f97c0
ceph version 0.94.1 (e4bfad3a3c51054df7e537a724c8d0bf9be972ff)
1: /usr/bin/ceph-mon() [0x903c52]
2: (()+0xf130) [0x7f88a76ba130]
3: (pthread_join()+0xa7) [0x7f88a76b3f27]
4: (Thread::join(void**)+0x12) [0x7a1b22]
5: (DispatchQueue::wait()+0x12) [0x8a39a2]
6: (SimpleMessenger::wait()+0x9a6) [0x797e66]
7: (main()+0x267c) [0x54e32c]
8: (__libc_start_main()+0xf5) [0x7f88a60c0af5]
9: /usr/bin/ceph-mon() [0x55d9c9]
NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
There are some logs available, I'll take a look and update ASAP.
Updated by Greg Farnum about 8 years ago
That most recent one was triggered by user SIGABRT, so it's not a reproduction of any genuine bugs. :)
Updated by Samuel Just about 8 years ago
- Status changed from Need More Info to Won't Fix
Marking back to Won't Fix
Actions