Re: [ceph-users] Cloudstack agent crashed JVM with exception in librbd

; > To: "Ceph Users" <ceph-users@lists.ceph.com > <mailto:ceph-users@lists.ceph.com>> > > Sent: Thursday, October 29, 2015 5:27:17 PM > > Subject: Re: [ceph-users] Cloudstack agent crashed JVM with > exception in > > librbd

Re: [ceph-users] Cloudstack agent crashed JVM with exception in librbd

on Dillaman >> > >> > >> > ----- Original Message ----- >> > >> > > From: "Voloshanenko Igor" <igor.voloshane...@gmail.com >> > <mailto:igor.voloshane...@gmail.com>> >> > > To: "Ceph Users&quo

Re: [ceph-users] Cloudstack agent crashed JVM with exception in librbd

; > Jason Dillaman > > > > > > - Original Message - > > > > > From: "Voloshanenko Igor" <igor.voloshane...@gmail.com > <mailto:igor.voloshane...@gmail.com> > > <

Re: [ceph-users] Cloudstack agent crashed JVM with exception in librbd

> aren't > > > actively exporting an image diff. The most likely problem > is that > > > the RADOS IO context is being closed prior to closing the > RBD image. > > > > > > -- > > > > >

Re: [ceph-users] Cloudstack agent crashed JVM with exception in librbd

gt; > Jason Dillaman > > > > > > - Original Message - > > > > > From: "Voloshanenko Igor" <igor.voloshane...@gmail.com > > <mailto:igor.voloshane...@gmail.com>> > > > To: "Ceph Users" <ceph-us

Re: [ceph-users] Cloudstack agent crashed JVM with exception in librbd

t;igor.voloshane...@gmail.com> > To: "Ceph Users" <ceph-users@lists.ceph.com> > Sent: Thursday, October 29, 2015 5:27:17 PM > Subject: Re: [ceph-users] Cloudstack agent crashed JVM with exception in > librbd > From all we analyzed - look like - it's this issue &

Re: [ceph-users] Cloudstack agent crashed JVM with exception in librbd

Dear all, can anybody help? 2015-10-30 10:37 GMT+02:00 Voloshanenko Igor : > It's pain, but not... :( > We already used your updated lib in dev env... :( > > 2015-10-30 10:06 GMT+02:00 Wido den Hollander : > >> >> >> On 29-10-15 16:38, Voloshanenko

Re: [ceph-users] Cloudstack agent crashed JVM with exception in librbd

Users" <ceph-users@lists.ceph.com> > > Sent: Thursday, October 29, 2015 5:27:17 PM > > Subject: Re: [ceph-users] Cloudstack agent crashed JVM with exception in > > librbd > > > From all we analyzed - look like - it's this issue > > http:

Re: [ceph-users] Cloudstack agent crashed JVM with exception in librbd

rom: "Voloshanenko Igor" <igor.voloshane...@gmail.com> > To: "Jason Dillaman" <dilla...@redhat.com> > Cc: "Ceph Users" <ceph-users@lists.ceph.com> > Sent: Monday, November 2, 2015 7:54:23 PM > Subject: Re: [ceph-users] Cloudstack agent crashed JV

Re: [ceph-users] Cloudstack agent crashed JVM with exception in librbd

On 29-10-15 16:38, Voloshanenko Igor wrote: > Hi Wido and all community. > > We catched very idiotic issue on our Cloudstack installation, which > related to ceph and possible to java-rados lib. > I think you ran into this one: https://issues.apache.org/jira/browse/CLOUDSTACK-8879 Cleaning

Re: [ceph-users] Cloudstack agent crashed JVM with exception in librbd

It's pain, but not... :( We already used your updated lib in dev env... :( 2015-10-30 10:06 GMT+02:00 Wido den Hollander : > > > On 29-10-15 16:38, Voloshanenko Igor wrote: > > Hi Wido and all community. > > > > We catched very idiotic issue on our Cloudstack installation, which >

[ceph-users] Cloudstack agent crashed JVM with exception in librbd

Hi Wido and all community. We catched very idiotic issue on our Cloudstack installation, which related to ceph and possible to java-rados lib. So, we have constantly agent crashed (which cause very big problem for us... ). When agent crashed - it's crash JVM. And no event in logs at all. We

Re: [ceph-users] Cloudstack agent crashed JVM with exception in librbd

>From all we analyzed - look like - it's this issue http://tracker.ceph.com/issues/13045 PR: https://github.com/ceph/ceph/pull/6097 Can anyone help us to confirm this? :) 2015-10-29 23:13 GMT+02:00 Voloshanenko Igor : > Additional trace: > > #0 0x7f30f9891cc9

Re: [ceph-users] Cloudstack agent crashed JVM with exception in librbd

Additional trace: #0 0x7f30f9891cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x7f30f98950d8 in __GI_abort () at abort.c:89 #2 0x7f30f87b36b5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #3