Bug #23431
Updated by Brad Hubbard about 6 years ago
I noticed an OSD segmentation fault in one of our OSDs logs. See the attached log entries. There is no core file that I could provide. Best Dietmar <pre> -2> 2018-03-21 05:09:31.310950 7fc69ba1c700 1 -- 10.0.2.10:6828/4210 <== osd.230 10.0.2.10:0/4168 14138 ==== osd_ping(ping e3328 stamp 2018-03-21 05:09:31.307794) v4 ==== 2004+0+0 (603415365 0 0) 0x5589fe22cc00 con 0x558a107ec000 -1> 2018-03-21 05:09:31.310960 7fc69ba1c700 1 -- 10.0.2.10:6828/4210 --> 10.0.2.10:0/4168 -- osd_ping(ping_reply e3328 stamp 2018-03-21 05:09:31.307794) v4 -- 0x558a0645c600 con 0 0> 2018-03-21 05:09:31.330524 7fc698258700 -1 *** Caught signal (Segmentation fault) ** in thread 7fc698258700 thread_name:safe_timer ceph version 12.2.4 (52085d5249a80c5f5121a76d6288429f35e4e77b) luminous (stable) 1: (()+0xa3c611) [0x5589e73f7611] 2: (()+0xf5e0) [0x7fc69f5185e0] NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this. </pre>