"NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this." Have you ever wondered what this means and why it's there? :) This is at least something you can try. it may provide useful information, it may not. This stack looks like it is either corrupted, or possibly not in ceph but in one of the linked libraries or glibc itself. If it's the former, it probably won't tell us anything. If it's the latter you will need the relevant debuginfo installed to get meaningful output and note that it will probably take a while. '<executable>' in this case is ceph-osd of course. Alternatively, if you can upload a coredump and an sosreport (so I can validate exact versions of all packages installed) I can try and take a look. On Fri, Mar 23, 2018 at 9:20 PM, Dietmar Rieder <dietmar.rieder@xxxxxxxxxxx> wrote: > Hi, > > > I encountered one more two days ago, and I opened a ticket: > > http://tracker.ceph.com/issues/23431 > > In our case it is more like 1 every two weeks, for now... > And it is affecting different OSDs on different hosts. > > Dietmar > > On 03/23/2018 11:50 AM, Oliver Freyermuth wrote: >> Hi together, >> >> I notice exactly the same, also the same addresses, Luminous 12.2.4, CentOS 7. >> Sadly, logs are equally unhelpful. >> >> It happens randomly on an OSD about once per 2-3 days (of the 196 total OSDs we have). It's also not a container environment. >> >> Cheers, >> Oliver >> >> Am 08.03.2018 um 15:00 schrieb Dietmar Rieder: >>> Hi, >>> >>> I noticed in my client (using cephfs) logs that an osd was unexpectedly >>> going down. >>> While checking the osd logs for the affected OSD I found that the osd >>> was seg faulting: >>> >>> [....] >>> 2018-03-07 06:01:28.873049 7fd9af370700 -1 *** Caught signal >>> (Segmentation fault) ** >>> in thread 7fd9af370700 thread_name:safe_timer >>> >>> ceph version 12.2.4 (52085d5249a80c5f5121a76d6288429f35e4e77b) >>> luminous (stable) >>> 1: (()+0xa3c611) [0x564585904611] >>> 2: (()+0xf5e0) [0x7fd9b66305e0] >>> NOTE: a copy of the executable, or `objdump -rdS <executable>` is >>> needed to interpret this. >>> [...] >>> >>> Should I open a ticket for this? What additional information is needed? >>> >>> >>> I put the relevant log entries for download under [1], so maybe someone >>> with more >>> experience can find some useful information therein. >>> >>> Thanks >>> Dietmar >>> >>> >>> [1] https://expirebox.com/download/6473c34c80e8142e22032469a59df555.html >>> >>> >>> >>> _______________________________________________ >>> ceph-users mailing list >>> ceph-users@xxxxxxxxxxxxxx >>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >>> >> >> >> >> >> _______________________________________________ >> ceph-users mailing list >> ceph-users@xxxxxxxxxxxxxx >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >> > > > -- > _________________________________________ > D i e t m a r R i e d e r, Mag.Dr. > Innsbruck Medical University > Biocenter - Division for Bioinformatics > Innrain 80, 6020 Innsbruck > Phone: +43 512 9003 71402 > Fax: +43 512 9003 73100 > Email: dietmar.rieder@xxxxxxxxxxx > Web: http://www.icbi.at > > > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > -- Cheers, Brad _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |