From: Faidon Liambotis <paravoid@debian.org>
To: Yehuda Sadeh <yehuda@inktank.com>
Cc: Yann ROBIN <yann.robin@youscribe.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Seg Fault on rgw 0.61.1 with cluster in 0.61
Date: Tue, 14 May 2013 15:16:01 +0300 [thread overview]
Message-ID: <51922B01.5060900@debian.org> (raw)
In-Reply-To: <CABBk=J_QaRUFmq_gPHeywkkRSJaaAzMz0eM8jZ15+FQKuQo5Bw@mail.gmail.com>
On 05/10/13 19:02, Yehuda Sadeh wrote:
> Sounds to me like package versioning mismastch. Could it be that one
> of the ceph packages was on a different version (e.g., librados).
I attempted to install and run radosgw 0.61.1 on a system with a 0.56.4
librados and it segfaulted with the same backtrace as the one in this
thread.
If a newer radosgw can't work with an older librados, this should be
reflected on the package relationships -- hopefully without nasty
Breaks/Conflicts, but with a proper librados SONAME bump that will allow
coinstability between librados2 and e.g. librados3. Or symbol versioning
could be employed to provide backwards compatibility.
This installed-but-segfaulting combination of packages shouldn't be
allowed by apt to exist on the system. FWIW, if these were packages in
Debian (and, presumably, Ubuntu), that would be a severity:
serious/release critical bug.
It'd also be nice to be able to do things like mixing newer radosgw
while also keeping the old librados2 on the system. My use case is that
I have monitors and radosgw on the same boxes and I'd like to keep
monitors on bobtail, while at the same time use some of the much needed
radosgw cuttlefish features.
Regards,
Faidon
next prev parent reply other threads:[~2013-05-14 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 8:51 Seg Fault on rgw 0.61.1 with cluster in 0.61 Yann ROBIN
2013-05-10 9:28 ` Yann ROBIN
2013-05-10 15:30 ` Sage Weil
2013-05-11 10:02 ` Yann ROBIN
2013-05-10 16:02 ` Yehuda Sadeh
2013-05-14 12:16 ` Faidon Liambotis [this message]
2013-05-16 17:35 ` Sage Weil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51922B01.5060900@debian.org \
--to=paravoid@debian.org \
--cc=ceph-devel@vger.kernel.org \
--cc=yann.robin@youscribe.com \
--cc=yehuda@inktank.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.