Project

General

Profile

Actions
Copy link

Bug #4997

closed

Seg Fault on rgw 0.61.1 with cluster in 0.61

Added by Yann ROBIN almost 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Hi,

I've tried to update the rgw to 0.61.1 and I had a segfault while connecting to the 0.61 cluster.
I have another server running rgw 0.61 that run fine.

  • Caught signal (Segmentation fault) * in thread 7fc1fec79780 ceph version 0.61.1 (56c4847ba82a92023700e2d4920b59cdaf23428d)
    1: /usr/bin/radosgw() [0x4f19da]
    2: (()+0xfcb0) [0x7fc1fcf0dcb0]
    3: (ceph::crypto::init(CephContext    )+0xf) [0x7fc1fdfeb2ef]
    4: (common_init_finish(CephContext*)+0x23) [0x7fc1fdfc33f3]
    5: (librados::RadosClient::connect()+0x1d) [0x7fc1fde1d48d]
    6: (RGWRados::initialize()+0x53) [0x5b5c03]
    7: (RGWStoreManager::init_storage_provider(CephContext*, bool)+0x2c9) [0x5b9b39]
    8: (main()+0x2d7) [0x4b4ed7]
    9: (__libc_start_main()+0xed) [0x7fc1fb90176d]
    10: /usr/bin/radosgw() [0x4b6db1]
    2013-05-10 10:36:39.749439 7fc1fec79780 -1 ** Caught signal (Segmentation fault) * in thread 7fc1fec79780

I tried to go back to previous version of rgw, and went to version 0.60. Seg fault still occured.
I went back to 0.61 and noticed rgw starting one time on ten.

I installed the dbg package to try to debug, and the problem disapeared.

Actions
Copy link
 #1

Updated by Ian Colle almost 11 years ago

  • Assignee set to Yehuda Sadeh
Actions
Copy link
 #2

Updated by Anonymous almost 11 years ago

  • Priority changed from Normal to Urgent
Actions
Copy link
 #3

Updated by Ian Colle almost 11 years ago

  • Target version deleted (v0.61 - Cuttlefish)
Actions
Copy link
 #4

Updated by Yann ROBIN almost 11 years ago

, it was a problem with ceph-common and librados2 packages who wasn't up-to-date.

It's not the first time that this problem append.

Reason is simple: Chef upgrade radosgw package automatically... but radosgw package only depend on ceph-common and librados2 without mention of a version... that is quite bad :p

To resolve any futur problem, we must update debian control file to depends on librados2 (= 0.61.1-1precise) (for example)

Guilhem Lettron

Actions
Copy link
 #5

Updated by Sylvain Munaut almost 11 years ago

This is the issue I reported on the ML and is tracked in http://tracker.ceph.com/issues/4944

Actions
Copy link
 #6

Updated by Sage Weil almost 11 years ago

  • Status changed from New to 12
  • Assignee changed from Yehuda Sadeh to Anonymous

gary, do you see a problem with matching up the versions like this? i think in radosgw's case it may be more important because it uses libcommon.la both statically and via librados... librbd probably doesn't care. rbd cli tool might though, but that's in ceph-common.

if ceph-common, librbd, and radosgw require =version i think we'll be okay. ceph and ceph-common should be ok diverging...

Actions
Copy link
 #7

Updated by Sage Weil almost 11 years ago

  • Status changed from 12 to Resolved

commit:604c83ff18f9a40c4f44bc8483ef22ff41efc8ad

Actions
Copy link

Also available in: Atom PDF