[ceph-users] Re: [ceph v16.2.10] radosgw crash

2023-09-12 Thread Tobias Urdin
Hello, That was solved in 16.2.11 in tracker [1] with fix [2]. Best regards Tobias [1] https://tracker.ceph.com/issues/55765 [2] https://github.com/ceph/ceph/pull/47194/commits > On 12 Sep 2023, at 05:29, Louis Koo wrote: > > radosgw crash again with: > ceph version 16.2.10 (45fa1a083152e41a4

[ceph-users] Re: [ceph v16.2.10] radosgw crash

2023-09-11 Thread Louis Koo
radosgw crash again with: ceph version 16.2.10 (45fa1a083152e41a408d15505f594ec5f1b4fe17) pacific (stable) 1: /lib64/libpthread.so.0(+0x12ce0) [0x7fdffc5d4ce0] 2: (rgw::ARN::ARN(rgw_bucket const&)+0x42) [0x7fe00727dbc2] 3: (verify_bucket_permission(DoutPrefixProvider const*, perm_state_base*,

[ceph-users] Re: [ceph v16.2.10] radosgw crash

2023-08-18 Thread 1187873955
Here is  the backtrace info in  core file (gdb) bt #0  0x7f79da065b7f in raise () from /lib64/libpthread.so.0 #1  0x7f79e5303563 in reraise_fatal (signum=6) at /usr/src/debug/ceph-16.2.10-0.el8.x86_64/src/global/signal_handler.cc:332 #2  handle_fatal_signal (signum=6) at /usr/

[ceph-users] Re: [ceph v16.2.10] radosgw crash

2023-08-16 Thread Casey Bodley
thanks Louis, that looks like the same backtrace as https://tracker.ceph.com/issues/61763. that issue has been on 'Need More Info' because all of the rgw logging was disabled there. are you able to share some more log output to help us figure this out? under "--- begin dump of recent events ---",