Ah found it. It was a SSL certificate that was invalid (some PoC which started to mold). Now the sync is running fine, but there is one bucket that got a ton of data in the mdlog. [root@s3db16 ~]# radosgw-admin mdlog list | grep temonitor | wc -l No --period given, using current period=e8fc96f1-ae86-4dc1-b432-470b0772fded 284760 [root@s3db16 ~]# radosgw-admin mdlog list | grep name | wc -l No --period given, using current period=e8fc96f1-ae86-4dc1-b432-470b0772fded 343078 Is it safe to clear the mdlog? Am Mo., 20. Sept. 2021 um 01:00 Uhr schrieb Boris Behrens <bb@xxxxxxxxx>: > I just deleted the rados object from .rgw.data.root and this removed the > bucket.instance, but this did not solve the problem. > > It looks like there is some access error when I try to radosgw-admin > metadata sync init. > The 403 http response code on the post to the /admin/realm/period endpoint. > > I checked the system_key and added a new system user and set the keys with > zone modify and period update --commit on both sides. > This also did not help. > > After a weekend digging through the mailing list and trying to fix it, I > am totally stuck. > I hope that someone of you people can help me. > > > > > Am Fr., 17. Sept. 2021 um 17:54 Uhr schrieb Boris Behrens <bb@xxxxxxxxx>: > >> While searching for other things I came across this: >> [root ~]# radosgw-admin metadata list bucket | grep www1 >> "www1", >> [root ~]# radosgw-admin metadata list bucket.instance | grep www1 >> "www1:ff7a8b0c-07e6-463a-861b-78f0adeba8ad.81095307.31103", >> "www1.company.dev", >> [root ~]# radosgw-admin bucket list | grep www1 >> "www1", >> [root ~]# radosgw-admin metadata rm bucket.instance:www1.company.dev >> ERROR: can't remove key: (22) Invalid argument >> >> Maybe this is part of the problem. >> >> Did somebody saw this and know what to do? >> -- >> Die Selbsthilfegruppe "UTF-8-Probleme" trifft sich diesmal abweichend im >> groüen Saal. >> > > > -- > Die Selbsthilfegruppe "UTF-8-Probleme" trifft sich diesmal abweichend im > groüen Saal. > -- Die Selbsthilfegruppe "UTF-8-Probleme" trifft sich diesmal abweichend im groüen Saal. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx