- ceph-users - lists.ceph.io

v16.2.1 Pacific released
by David Galloway 20 Apr '21

20 Apr '21

This is the first bugfix release in the Pacific stable series. It addresses a security vulnerability in the Ceph authentication framework. We recommend users to update to this release. For a detailed release notes with links & changelog please refer to the official blog entry at https://ceph.io/releases/v16-2-1-pacific-released Security Fixes -------------- * This release includes a security fix that ensures the global_id value (a numeric value that should be unique for every authenticated client or daemon in the cluster) is reclaimed after a network disconnect or ticket renewal in a secure fashion. Two new health alerts may appear during the upgrade indicating that there are clients or daemons that are not yet patched with the appropriate fix. Getting Ceph ------------ * Git at git://github.com/ceph/ceph.git * Tarball at http://download.ceph.com/tarballs/ceph-16.2.1.tar.gz * For packages, see http://docs.ceph.com/docs/master/install/get-packages/ * Release git sha1: afb9061ab4117f798c858c741efa6390e48ccf10

2 1

v15.2.11 Octopus released
by David Galloway 20 Apr '21

20 Apr '21

This is the 11th bugfix release in the Octopus stable series. It addresses a security vulnerability in the Ceph authentication framework. We recommend users to update to this release. For a detailed release notes with links & changelog please refer to the official blog entry at https://ceph.io/releases/v15-2-11-octopus-released Security Fixes -------------- * This release includes a security fix that ensures the global_id value (a numeric value that should be unique for every authenticated client or daemon in the cluster) is reclaimed after a network disconnect or ticket renewal in a secure fashion. Two new health alerts may appear during the upgrade indicating that there are clients or daemons that are not yet patched with the appropriate fix. Getting Ceph ------------ * Git at git://github.com/ceph/ceph.git * Tarball at http://download.ceph.com/tarballs/ceph-15.2.11.tar.gz * For packages, see http://docs.ceph.com/docs/master/install/get-packages/ * Release git sha1: e3523634d9c2227df9af89a4eac33d16738c49cb

2 1

any experience on using Bcache on top of HDD OSD
by huxiaoyu＠horebdata.cn 20 Apr '21

20 Apr '21

Dear Cephers, Just curious about any one who has some experience on using Bcache on top of HDD OSD to accelerate IOPS performance? If any, how about the stability and the performance improvement, and for how long the running time? I am evaluating whether its is worth to use Bcache on top of HDD OSD. I have done some experimental on using bcache with OSD, and would like to make sure before doing it on a production cluster. thanks in advance, samuel huxiaoyu(a)horebdata.cn

3 4

Documentation of the LVM metadata format
by Nico Schottelius 19 Apr '21

19 Apr '21

Good morning, is there any documentation available regarding the meta data stored within LVM that ceph-volume manages / creates? My background is that ceph-volume activate does not work on non-systemd Linux distributions, but if I know how to recreate the tmpfs, we can easily start the osd without systemd. Any pointers in the right direction are appreciated. Best regards, Nico -- Sustainable and modern Infrastructures by ungleich.ch

3 5

cleanup multipart in radosgw
by Boris Behrens 19 Apr '21

19 Apr '21

Hi, is there a way to remove multipart uploads that are older than X days? It doesn't need to be build into ceph or is automated to the end. Just something I don't need to build on my own. I currently try to debug a problem where ceph reports a lot more used space than it actually requires ( https://www.mail-archive.com/ceph-users@ceph.io/msg09810.html) I came across a lot of old _multipart_ files in some buckets and now I want to clean them up. I don't know if this will fix my problem but I would love to rule that out. radosgw-admin bucket check --bucket=bucket --check-objects --fix does not work because it is a shareded bucket. I have also some buckets that look like this, and contain 100% _multipart_ files which are >2 years old: "buckets": [ { "bucket": "ncprod", "tenant": "", "num_objects": -482, "num_shards": 0, "objects_per_shard": -482, "fill_status": "OVER 180143985094819%" } ] -- Die Selbsthilfegruppe "UTF-8-Probleme" trifft sich diesmal abweichend im groÃƒ¼en Saal.

2 2

Radosgw - WARNING: couldn't find acl header for object, generating default
by by morphin 19 Apr '21

19 Apr '21

Hello. I've a RGW bucket (versioning=on). And there was objects like this: radosgw-admin object stat --bucket=xdir --object=f5492238-50cb-4bc2-93fa-424869018946 { "name": "f5492238-50cb-4bc2-93fa-424869018946", "size": 0, "tag": "", "attrs": { "user.rgw.manifest": "", "user.rgw.olh.idtag": "5rs3x0qh152tn0j865k8ybo9xqy92qjn", "user.rgw.olh.info": "\u0001\u0001�", "user.rgw.olh.pending.00000000607c87b5pgo03tvm3sqt23i9": "\u0001\u0001\u0008", "user.rgw.olh.pending.00000000607c87b5pyv13ugk3fadvxw7": "\u0001\u0001\u0008", "user.rgw.olh.pending.00000000607c87b5qic02n0e54zsjkax": "\u0001\u0001\u0008", "user.rgw.olh.ver": "3" } } I'm not sure but I suspect that these objects maybe leftover from unfinished multisite sync. I've removed the zone and made it master (because I have to for something else) and I've created a newbucket with (versioning=off) and copied all objects from old rgw bucket to a new rgw bucket with "rclone" cmd: "rclone copy --files-from "object.list" old:bucket new:bucket --no-traverse -vv --progress --fast-list --no-check-dest --no-update-modtime" Config: [bucket] type = s3 provider = Ceph env_auth = false acl = private bucket = access_key_id = secret_access_key = endpoint = After the copy I've checked every object via "radosgw-admin object stat object=$i" and there was still these problematic objects. I've tried to overwrite these objects from the Backup-bucket at different cluster (these objects are fine) and I tried to be sure everything written as expected via object stat again and these pending object was gone and everything was ok. All of them was OK! After a while I started to see this warning in radosgw.log when the client GET or HEAD the objects. 2021-04-19 11:37:50.230 7f2d917eb700 1 ====== starting new request req=0x55a44414a710 ===== 2021-04-19 11:37:50.230 7f2d917eb700 0 WARNING: couldn't find acl header for object, generating default 2021-04-19 11:37:50.230 7f2d917eb700 1 ====== req done req=0x55a44414a710 op status=0 http_status=200 latency=0s ====== 2021-04-19 11:37:50.230 7f2d917eb700 1 beast: 0x55a44414a710: 10.10.10.1 - - [2021-04-19 11:37:50.0.230489s] "HEAD /xdir/f5492238-50cb-4bc2-93fa-424869018946 HTTP/1.1" 200 0 - "aws-sdk-java/1.11.638 Linux/3.10.0-1160.11.1.el7.x86_64 Java_HotSpot(TM)_64-Bit_Server_VM/25.281-b09 java/1.8.0_281 groovy/2.5.6 vendor/Oracle_Corporation" - These objects are problematic objects and somehow the overwritten objects is gone and these objects left after the WARNING. (versioning is still =off --> multisite = off --> the cluster alone in zonegroup and its masterzone) But I've checked every overwritten object via "radosgw-admin object stat object=$i" and there was all OK!!! How the hell they're gone and others came back? HOW? What should I do? Maybe "object rm" "log trim" and re-write again?

1 0

Octopus - unbalanced OSDs
by Ml Ml 19 Apr '21

19 Apr '21

Hello List, any ideas why my OSDs are that unbalanced ? root@ceph01:~# ceph -s cluster: id: 5436dd5d-83d4-4dc8-a93b-60ab5db145df health: HEALTH_WARN 1 nearfull osd(s) 4 pool(s) nearfull services: mon: 3 daemons, quorum ceph03,ceph01,ceph02 (age 2w) mgr: ceph03(active, since 4M), standbys: ceph02.jwvivm mds: backup:1 {0=backup.ceph06.hdjehi=up:active} 3 up:standby osd: 56 osds: 56 up (since 29h), 56 in (since 3d) task status: scrub status: mds.backup.ceph06.hdjehi: idle data: pools: 4 pools, 1185 pgs objects: 24.29M objects, 44 TiB usage: 151 TiB used, 55 TiB / 206 TiB avail pgs: 675 active+clean 476 active+clean+snaptrim_wait 30 active+clean+snaptrim 4 active+clean+scrubbing+deep root@ceph01:~# ceph osd df tree ID CLASS WEIGHT REWEIGHT SIZE RAW USE DATA OMAP META AVAIL %USE VAR PGS STATUS TYPE NAME -1 206.79979 - 206 TiB 151 TiB 151 TiB 36 GiB 503 GiB 55 TiB 73.23 1.00 - root default -2 28.89995 - 29 TiB 20 TiB 20 TiB 5.5 GiB 74 GiB 8.9 TiB 69.19 0.94 - host ceph01 0 hdd 2.70000 1.00000 2.7 TiB 1.8 TiB 1.8 TiB 590 MiB 6.9 GiB 908 GiB 66.81 0.91 44 up osd.0 1 hdd 2.70000 1.00000 2.7 TiB 1.6 TiB 1.6 TiB 411 MiB 6.5 GiB 1.1 TiB 60.43 0.83 39 up osd.1 4 hdd 2.70000 1.00000 2.7 TiB 1.8 TiB 1.8 TiB 501 MiB 6.8 GiB 898 GiB 67.15 0.92 43 up osd.4 8 hdd 2.70000 1.00000 2.7 TiB 2.0 TiB 2.0 TiB 453 MiB 7.0 GiB 700 GiB 74.39 1.02 47 up osd.8 11 hdd 1.70000 1.00000 1.7 TiB 1.3 TiB 1.3 TiB 356 MiB 5.6 GiB 433 GiB 75.39 1.03 31 up osd.11 12 hdd 2.70000 1.00000 2.7 TiB 2.1 TiB 2.1 TiB 471 MiB 7.0 GiB 591 GiB 78.40 1.07 48 up osd.12 14 hdd 2.70000 1.00000 2.7 TiB 1.6 TiB 1.6 TiB 448 MiB 6.0 GiB 1.1 TiB 59.68 0.82 38 up osd.14 18 hdd 2.70000 1.00000 2.7 TiB 1.7 TiB 1.7 TiB 515 MiB 6.2 GiB 980 GiB 64.15 0.88 41 up osd.18 22 hdd 1.70000 1.00000 1.7 TiB 1.2 TiB 1.2 TiB 360 MiB 4.2 GiB 491 GiB 72.06 0.98 29 up osd.22 30 hdd 1.70000 1.00000 1.7 TiB 1.2 TiB 1.2 TiB 366 MiB 4.7 GiB 558 GiB 68.26 0.93 28 up osd.30 33 hdd 1.59999 1.00000 1.6 TiB 1.2 TiB 1.2 TiB 406 MiB 4.9 GiB 427 GiB 74.28 1.01 29 up osd.33 64 hdd 3.29999 1.00000 3.3 TiB 2.4 TiB 2.4 TiB 736 MiB 8.6 GiB 915 GiB 73.22 1.00 60 up osd.64 -3 29.69995 - 30 TiB 22 TiB 22 TiB 5.4 GiB 81 GiB 7.9 TiB 73.20 1.00 - host ceph02 2 hdd 1.70000 1.00000 1.7 TiB 1.3 TiB 1.2 TiB 402 MiB 5.2 GiB 476 GiB 72.93 1.00 30 up osd.2 3 hdd 2.70000 1.00000 2.7 TiB 2.0 TiB 2.0 TiB 653 MiB 7.8 GiB 652 GiB 76.15 1.04 49 up osd.3 7 hdd 2.70000 1.00000 2.7 TiB 2.5 TiB 2.5 TiB 456 MiB 7.7 GiB 209 GiB 92.36 1.26 56 up osd.7 9 hdd 2.70000 1.00000 2.7 TiB 1.9 TiB 1.9 TiB 434 MiB 7.2 GiB 781 GiB 71.46 0.98 46 up osd.9 13 hdd 2.39999 1.00000 2.4 TiB 1.6 TiB 1.6 TiB 451 MiB 6.1 GiB 823 GiB 66.28 0.91 38 up osd.13 16 hdd 2.70000 1.00000 2.7 TiB 1.6 TiB 1.6 TiB 375 MiB 6.4 GiB 1.1 TiB 59.84 0.82 39 up osd.16 19 hdd 1.70000 1.00000 1.7 TiB 1.1 TiB 1.1 TiB 323 MiB 4.7 GiB 601 GiB 65.80 0.90 27 up osd.19 23 hdd 2.70000 1.00000 2.7 TiB 2.2 TiB 2.2 TiB 471 MiB 7.7 GiB 520 GiB 80.99 1.11 50 up osd.23 24 hdd 1.70000 1.00000 1.7 TiB 1.4 TiB 1.4 TiB 371 MiB 5.5 GiB 273 GiB 84.44 1.15 32 up osd.24 28 hdd 2.70000 1.00000 2.7 TiB 1.9 TiB 1.9 TiB 428 MiB 7.4 GiB 818 GiB 70.07 0.96 44 up osd.28 31 hdd 2.70000 1.00000 2.7 TiB 2.0 TiB 2.0 TiB 516 MiB 7.4 GiB 660 GiB 75.85 1.04 48 up osd.31 32 hdd 3.29999 1.00000 3.3 TiB 2.2 TiB 2.2 TiB 661 MiB 7.9 GiB 1.2 TiB 64.86 0.89 52 up osd.32 -4 26.29996 - 26 TiB 18 TiB 18 TiB 4.3 GiB 73 GiB 8.0 TiB 69.58 0.95 - host ceph03 5 hdd 1.70000 1.00000 1.7 TiB 1.2 TiB 1.2 TiB 298 MiB 5.2 GiB 541 GiB 69.21 0.95 29 up osd.5 6 hdd 1.70000 1.00000 1.7 TiB 1.0 TiB 1.0 TiB 321 MiB 4.4 GiB 697 GiB 60.34 0.82 25 up osd.6 10 hdd 2.70000 1.00000 2.7 TiB 1.9 TiB 1.9 TiB 431 MiB 7.5 GiB 796 GiB 70.89 0.97 46 up osd.10 15 hdd 2.70000 1.00000 2.7 TiB 1.9 TiB 1.9 TiB 500 MiB 6.6 GiB 805 GiB 70.55 0.96 44 up osd.15 17 hdd 1.59999 1.00000 1.6 TiB 1.1 TiB 1.1 TiB 377 MiB 4.9 GiB 530 GiB 68.05 0.93 27 up osd.17 20 hdd 1.70000 1.00000 1.7 TiB 1.0 TiB 1.0 TiB 223 MiB 4.7 GiB 685 GiB 61.03 0.83 25 up osd.20 21 hdd 2.70000 1.00000 2.7 TiB 1.7 TiB 1.7 TiB 392 MiB 6.7 GiB 951 GiB 65.23 0.89 42 up osd.21 25 hdd 1.70000 1.00000 1.7 TiB 1.1 TiB 1.1 TiB 157 MiB 5.1 GiB 601 GiB 65.83 0.90 27 up osd.25 26 hdd 2.70000 1.00000 2.7 TiB 2.1 TiB 2.1 TiB 512 MiB 7.6 GiB 573 GiB 79.06 1.08 50 up osd.26 27 hdd 2.70000 1.00000 2.7 TiB 1.9 TiB 1.9 TiB 473 MiB 7.6 GiB 805 GiB 70.55 0.96 46 up osd.27 29 hdd 2.70000 1.00000 2.7 TiB 2.1 TiB 2.1 TiB 478 MiB 7.3 GiB 539 GiB 80.29 1.10 50 up osd.29 63 hdd 1.70000 1.00000 1.7 TiB 1.1 TiB 1.1 TiB 195 MiB 5.1 GiB 646 GiB 63.23 0.86 26 up osd.63 -11 24.79999 - 25 TiB 18 TiB 18 TiB 4.1 GiB 59 GiB 6.3 TiB 74.51 1.02 - host ceph04 34 hdd 5.20000 1.00000 5.2 TiB 3.9 TiB 3.8 TiB 954 MiB 13 GiB 1.4 TiB 73.48 1.00 94 up osd.34 42 hdd 5.20000 1.00000 5.2 TiB 3.9 TiB 3.8 TiB 841 MiB 13 GiB 1.4 TiB 73.43 1.00 94 up osd.42 44 hdd 7.20000 1.00000 7.2 TiB 5.5 TiB 5.5 TiB 1.2 GiB 17 GiB 1.6 TiB 77.54 1.06 133 up osd.44 45 hdd 7.20000 1.00000 7.2 TiB 5.2 TiB 5.2 TiB 1.2 GiB 16 GiB 1.9 TiB 73.03 1.00 125 up osd.45 -13 30.09998 - 30 TiB 22 TiB 22 TiB 5.1 GiB 72 GiB 8.0 TiB 73.48 1.00 - host ceph05 39 hdd 7.20000 1.00000 7.2 TiB 5.6 TiB 5.6 TiB 1.4 GiB 17 GiB 1.6 TiB 77.89 1.06 126 up osd.39 40 hdd 7.20000 1.00000 7.2 TiB 5.3 TiB 5.3 TiB 1.2 GiB 17 GiB 1.9 TiB 73.87 1.01 124 up osd.40 41 hdd 7.20000 1.00000 7.2 TiB 5.4 TiB 5.3 TiB 1.1 GiB 17 GiB 1.8 TiB 74.92 1.02 128 up osd.41 43 hdd 5.20000 1.00000 5.2 TiB 3.7 TiB 3.7 TiB 853 MiB 13 GiB 1.5 TiB 71.28 0.97 91 up osd.43 60 hdd 3.29999 1.00000 3.3 TiB 2.1 TiB 2.1 TiB 573 MiB 7.9 GiB 1.2 TiB 63.53 0.87 52 up osd.60 -9 17.59999 - 18 TiB 12 TiB 12 TiB 3.0 GiB 40 GiB 5.3 TiB 70.10 0.96 - host ceph06 35 hdd 7.20000 1.00000 7.2 TiB 5.2 TiB 5.2 TiB 1.3 GiB 16 GiB 1.9 TiB 72.80 0.99 125 up osd.35 36 hdd 5.20000 1.00000 5.2 TiB 3.5 TiB 3.5 TiB 804 MiB 12 GiB 1.8 TiB 66.50 0.91 85 up osd.36 38 hdd 5.20000 1.00000 5.2 TiB 3.7 TiB 3.7 TiB 978 MiB 12 GiB 1.6 TiB 70.02 0.96 88 up osd.38 -15 24.89998 - 25 TiB 18 TiB 18 TiB 4.3 GiB 58 GiB 6.5 TiB 73.75 1.01 - host ceph07 66 hdd 7.20000 1.00000 7.2 TiB 5.3 TiB 5.3 TiB 1.1 GiB 17 GiB 1.8 TiB 74.74 1.02 126 up osd.66 67 hdd 7.20000 1.00000 7.2 TiB 5.3 TiB 5.3 TiB 1.2 GiB 17 GiB 1.8 TiB 74.51 1.02 121 up osd.67 68 hdd 3.29999 1.00000 3.3 TiB 2.3 TiB 2.3 TiB 720 MiB 7.9 GiB 1.0 TiB 68.63 0.94 55 up osd.68 69 hdd 7.20000 1.00000 7.2 TiB 5.3 TiB 5.3 TiB 1.2 GiB 17 GiB 1.8 TiB 74.40 1.02 129 up osd.69 -17 24.50000 - 24 TiB 20 TiB 20 TiB 4.1 GiB 47 GiB 4.4 TiB 82.08 1.12 - host ceph08 37 hdd 9.50000 1.00000 9.5 TiB 7.8 TiB 7.7 TiB 1.5 GiB 18 GiB 1.8 TiB 81.39 1.11 166 up osd.37 46 hdd 5.00000 1.00000 5.0 TiB 4.0 TiB 3.9 TiB 889 MiB 9.3 GiB 1.0 TiB 79.67 1.09 87 up osd.46 47 hdd 5.00000 1.00000 5.0 TiB 4.2 TiB 4.2 TiB 863 MiB 9.7 GiB 817 GiB 83.90 1.15 90 up osd.47 48 hdd 5.00000 1.00000 5.0 TiB 4.2 TiB 4.2 TiB 969 MiB 10 GiB 813 GiB 83.99 1.15 91 up osd.48 TOTAL 206 TiB 151 TiB 151 TiB 36 GiB 503 GiB 55 TiB 73.23 MIN/MAX VAR: 0.82/1.26 STDDEV: 7.00 root@ceph01:~# ceph balancer status { "active": true, "last_optimize_duration": "0:00:00.016174", "last_optimize_started": "Fri Apr 16 12:54:47 2021", "mode": "upmap", "optimize_result": "Unable to find further optimization, or pool(s) pg_num is decreasing, or distribution is already perfect", "plans": [] } root@ceph01:~# ceph versions { "mon": { "ceph version 15.2.5 (2c93eff00150f0cc5f106a559557a58d3d7b6f1f) octopus (stable)": 3 }, "mgr": { "ceph version 15.2.5 (2c93eff00150f0cc5f106a559557a58d3d7b6f1f) octopus (stable)": 2 }, "osd": { "ceph version 15.2.5 (2c93eff00150f0cc5f106a559557a58d3d7b6f1f) octopus (stable)": 56 }, "mds": { "ceph version 15.2.5 (2c93eff00150f0cc5f106a559557a58d3d7b6f1f) octopus (stable)": 4 }, "overall": { "ceph version 15.2.5 (2c93eff00150f0cc5f106a559557a58d3d7b6f1f) octopus (stable)": 65 } } root@ceph01:~# ceph osd crush rule ls replicated_ruleset root@ceph01:~# ceph osd crush rule dump replicated_ruleset { "rule_id": 0, "rule_name": "replicated_ruleset", "ruleset": 0, "type": 1, "min_size": 1, "max_size": 10, "steps": [ { "op": "take", "item": -1, "item_name": "default" }, { "op": "chooseleaf_firstn", "num": 0, "type": "host" }, { "op": "emit" } ] } Cheers, Michael

2 2

Abandon incomplete (damaged EC) pgs - How to manage the impact on cephfs?
by Joshua West 18 Apr '21

18 Apr '21

Hey everyone. Inside of cephfs, I have a directory which I setup a directory layout field to use an erasure coded (CLAY) pool, specific to the task. The rest of my cephfs is using normal replication. Fast forward some time, and the EC directory has been used pretty extensively, and through some bad luck and poor timing, ~200pgs are in an incomplete state, and the OSDs are completely gone and unrecoverable. (Specifically OSD 31 and 34, not that it matters at this point) # ceph pg ls incomplete --> is attached for reference. Fortunately, it's primarily (only) my on-site backups, and other replaceable data inside of I tried for a few days to recover the PGs: - Recreate blank OSDs with correct ID (was blocked by non-existant OSDs) - Deep Scrub - osd_find_best_info_ignore_history_les = true (`pg query` was showing related error) etc. I've finally just accepted this pool to be a lesson learned, and want to get the rest of my cephfs back to normal. My questions: -- `ceph osd force-create-pg` doesn't appear to fix pgs, even for pgs with 0 objects -- Deleting the pool seems like an appropriate step, but as I am using an xattr within cephfs, which is otherwise on another pool, I am not confident that this approach is safe? -- cephfs currently blocks when attemping to impact every third file in the EC directory. Once I delete the pool, how will I remove the files if even `rm` is blocking? Thank you for your time, Joshua West

3 8

Can't get one OSD (out of 14) to start
by Mark Johnson 16 Apr '21

16 Apr '21

Really not sure where to go with this one. Firstly, a description of my cluster. Yes, I know there are a lot of "not ideals" here but this is what I inherited. The cluster is running Jewel and has two storage/mon nodes and an additional mon only node, with a pool size of 2. Today, we had a some power issues in the data centre and we very ungracefully lost both storage servers at the same time. Node 1 came back online before node 2 but I could see there were a few OSDs that were down. When node 2 came back, I started trying to get OSDs up. Each node has 14 OSDs and I managed to get all OSDs up and in on node 2, but one of the OSDs on node 1 keeps starting and crashing and just won't stay up. I'm not finding the OSD log output to be much use. Current health status looks like this: # ceph health HEALTH_ERR 26 pgs are stuck inactive for more than 300 seconds; 26 pgs down; 26 pgs peering; 26 pgs stuck inactive; 26 pgs stuck unclean; 5 requests are blocked > 32 sec # ceph status cluster e2391bbf-15e0-405f-af12-943610cb4909 health HEALTH_ERR 26 pgs are stuck inactive for more than 300 seconds 26 pgs down 26 pgs peering 26 pgs stuck inactive 26 pgs stuck unclean 5 requests are blocked > 32 sec Any clues as to what I should be looking for or what sort of action I should be taking to troubleshoot this? Unfortunately, I'm a complete novice with Ceph. Here's a snippet from the OSD log that means little to me... --- begin dump of recent events --- 0> 2021-04-16 12:25:10.169340 7f2e23921ac0 -1 *** Caught signal (Aborted) ** in thread 7f2e23921ac0 thread_name:ceph-osd ceph version 10.2.11 (e4b061b47f07f583c92a050d9e84b1813a35671e) 1: (()+0x9f1c2a) [0x7f2e24330c2a] 2: (()+0xf5d0) [0x7f2e21ee95d0] 3: (gsignal()+0x37) [0x7f2e2049f207] 4: (abort()+0x148) [0x7f2e204a08f8] 5: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x267) [0x7f2e2442fd47] 6: (FileJournal::read_entry(ceph::buffer::list&, unsigned long&, bool*)+0x90c) [0x7f2e2417bc7c] 7: (JournalingObjectStore::journal_replay(unsigned long)+0x1ee) [0x7f2e240c8dce] 8: (FileStore::mount()+0x3cd6) [0x7f2e240a0546] 9: (OSD::init()+0x27d) [0x7f2e23d5828d] 10: (main()+0x2c18) [0x7f2e23c71088] 11: (__libc_start_main()+0xf5) [0x7f2e2048b3d5] 12: (()+0x3c8847) [0x7f2e23d07847] NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this. Thanks in advance, Mark

2 5

what-does-nosuchkey-error-mean-while-subscribing-for-notification-in-ceph
by Szabo, Istvan (Agoda) 16 Apr '21

16 Apr '21

Hi, I am trying to follow this url https://docs.ceph.com/en/latest/radosgw/s3/bucketops/#create-notification to create a publisher for my bucket into a topic. My curl: curl -v -H 'Date: Fri, 16 Apr 2021 05:21:14 +0000' -H 'Authorization: AWS accessid:secretkey' -L -H 'content-type: text/xml' -H 'Content-MD5: pBRX39Oo7aAUYbilIYMoAw==' -T notif.xml http://ceph:8080/vig-test?notification and it returns me this error <?xml version="1.0" encoding="UTF-8"?> <Error> <Code>NoSuchKey</Code> <BucketName>vig-test</BucketName> <RequestId>tx0000000000000016ac570-0060791ecb-1c7e96b-hkg</RequestId> <HostId>1c7e96b-hkg-data</HostId> </Error> Does anybody know what does this error mean in Ceph? How can I proceed? Thank you ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

3 3