Update Ceph 17.2.1 -> 17.2.4 Crash / unable to find a keyring

ITT

Well-Known Member
Mar 19, 2021
434
107
48
44
Das heutige Update lief nicht so gut, hat da jemand einen Tip?

Code:
Oct 19 14:32:48 nod150a12 ceph-crash[1299]: WARNING:ceph-crash:post /var/lib/ceph/crash/2022-10-19T12:19:25.374934Z_de56ee36-46e8-4b5c-8ed2-32e78dde7552 as client.admin failed: (None, b'')
Oct 19 14:32:48 nod150a12 ceph-crash[1299]: WARNING:ceph-crash:post /var/lib/ceph/crash/2022-10-19T12:19:30.798438Z_0950097d-ba49-4d24-868d-a2b573f97507 as client.crash.nod150a12 failed: (None, b'2022-10-19T14:32:48.753+0200 7f5fc1330700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.nod150a12.keyring: (2) No such file or directory\n2022-10-19T14:32:48.753+0200 7f5fc1330700 -1 AuthRegistry(0x7f5fbc060670) no keyring found at /etc/pve/priv/ceph.client.crash.nod150a12.keyring, disabling cephx\n2022-10-19T14:32:48.757+0200 7f5fbbfff700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.nod150a12.keyring: (2) No such file or directory\n2022-10-19T14:32:48.757+0200 7f5fbbfff700 -1 AuthRegistry(0x7f5fbc065ca0) no keyring found at /etc/pve/priv/ceph.client.crash.nod150a12.keyring, disabling cephx\n2022-10-19T14:32:48.757+0200 7f5fbbfff700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.nod150a12.keyring: (2) No such file or directory\n2022-10-19T14:32:48.757+0200 7f5fbbfff700 -1 AuthRegistry(0x7f5fbbffe0d0) no keyring found at /etc/pve/priv/ceph.client.crash.nod150a12.keyring, disabling cephx\n[errno 2] RADOS object not found (error connecting to the cluster)\n')
Oct 19 14:32:48 nod150a12 ceph-crash[1299]: WARNING:ceph-crash:post /var/lib/ceph/crash/2022-10-19T12:19:30.798438Z_0950097d-ba49-4d24-868d-a2b573f97507 as client.crash failed: (None, b'2022-10-19T14:32:48.805+0200 7f235487c700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (2) No such file or directory\n2022-10-19T14:32:48.805+0200 7f235487c700 -1 AuthRegistry(0x7f2350060610) no keyring found at /etc/pve/priv/ceph.client.crash.keyring, disabling cephx\n2022-10-19T14:32:48.809+0200 7f234f59e700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (2) No such file or directory\n2022-10-19T14:32:48.809+0200 7f234f59e700 -1 AuthRegistry(0x7f2350065b80) no keyring found at /etc/pve/priv/ceph.client.crash.keyring, disabling cephx\n2022-10-19T14:32:48.809+0200 7f234f59e700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (2) No such file or directory\n2022-10-19T14:32:48.809+0200 7f234f59e700 -1 AuthRegistry(0x7f234f59d0d0) no keyring found at /etc/pve/priv/ceph.client.crash.keyring, disabling cephx\n[errno 2] RADOS object not found (error connecting to the cluster)\n')
Oct 19 14:33:04 nod150a12 ceph-crash[1299]: WARNING:ceph-crash:post /var/lib/ceph/crash/2022-10-19T12:19:30.798438Z_0950097d-ba49-4d24-868d-a2b573f97507 as client.admin failed: (None, b'')
Oct 19 14:33:04 nod150a12 ceph-crash[1299]: WARNING:ceph-crash:post /var/lib/ceph/crash/2022-10-19T12:19:31.320734Z_0a1cb326-870b-4463-9035-16042080823a as client.crash.nod150a12 failed: (None, b'2022-10-19T14:33:04.240+0200 7f1286542700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.nod150a12.keyring: (2) No such file or directory\n2022-10-19T14:33:04.240+0200 7f1286542700 -1 AuthRegistry(0x7f1280060670) no keyring found at /etc/pve/priv/ceph.client.crash.nod150a12.keyring, disabling cephx\n2022-10-19T14:33:04.244+0200 7f1286542700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.nod150a12.keyring: (2) No such file or directory\n2022-10-19T14:33:04.244+0200 7f1286542700 -1 AuthRegistry(0x7f1280065ca0) no keyring found at /etc/pve/priv/ceph.client.crash.nod150a12.keyring, disabling cephx\n2022-10-19T14:33:04.244+0200 7f1286542700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.nod150a12.keyring: (2) No such file or directory\n2022-10-19T14:33:04.244+0200 7f1286542700 -1 AuthRegistry(0x7f12865410d0) no keyring found at /etc/pve/priv/ceph.client.crash.nod150a12.keyring, disabling cephx\n[errno 2] RADOS object not found (error connecting to the cluster)\n')
Oct 19 14:33:04 nod150a12 ceph-crash[1299]: WARNING:ceph-crash:post /var/lib/ceph/crash/2022-10-19T12:19:31.320734Z_0a1cb326-870b-4463-9035-16042080823a as client.crash failed: (None, b'2022-10-19T14:33:04.288+0200 7fd6e83bf700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (2) No such file or directory\n2022-10-19T14:33:04.288+0200 7fd6e83bf700 -1 AuthRegistry(0x7fd6e0060610) no keyring found at /etc/pve/priv/ceph.client.crash.keyring, disabling cephx\n2022-10-19T14:33:04.292+0200 7fd6e715d700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (2) No such file or directory\n2022-10-19T14:33:04.292+0200 7fd6e715d700 -1 AuthRegistry(0x7fd6e0065b80) no keyring found at /etc/pve/priv/ceph.client.crash.keyring, disabling cephx\n2022-10-19T14:33:04.292+0200 7fd6e715d700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (2) No such file or directory\n2022-10-19T14:33:04.292+0200 7fd6e715d700 -1 AuthRegistry(0x7fd6e715c0d0) no keyring found at /etc/pve/priv/ceph.client.crash.keyring, disabling cephx\n[errno 2] RADOS object not found (error connecting to the cluster)\n')
Oct 19 14:33:04 nod150a12 ceph-crash[1299]: WARNING:ceph-crash:post /var/lib/ceph/crash/2022-10-19T12:19:31.320734Z_0a1cb326-870b-4463-9035-16042080823a as client.admin failed: (None, b'')
Oct 19 14:33:04 nod150a12 ceph-crash[1299]: WARNING:ceph-crash:post /var/lib/ceph/crash/2022-10-19T12:19:27.279763Z_049047bd-62a1-487c-be3d-9d736a634d88 as client.crash.nod150a12 failed: (None, b'2022-10-19T14:33:04.500+0200 7f7fcf6ba700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.nod150a12.keyring: (2) No such file or directory\n2022-10-19T14:33:04.500+0200 7f7fcf6ba700 -1 AuthRegistry(0x7f7fc8060670) no keyring found at /etc/pve/priv/ceph.client.crash.nod150a12.keyring, disabling cephx\n2022-10-19T14:33:04.504+0200 7f7fce458700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.nod150a12.keyring: (2) No such file or directory\n2022-10-19T14:33:04.504+0200 7f7fce458700 -1 AuthRegistry(0x7f7fc8065ca0) no keyring found at /etc/pve/priv/ceph.client.crash.nod150a12.keyring, disabling cephx\n2022-10-19T14:33:04.504+0200 7f7fce458700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.nod150a12.keyring: (2) No such file or directory\n2022-10-19T14:33:04.504+0200 7f7fce458700 -1 AuthRegistry(0x7f7fce4570d0) no keyring found at /etc/pve/priv/ceph.client.crash.nod150a12.keyring, disabling cephx\n[errno 2] RADOS object not found (error connecting to the cluster)\n')
Oct 19 14:33:04 nod150a12 ceph-crash[1299]: WARNING:ceph-crash:post /var/lib/ceph/crash/2022-10-19T12:19:27.279763Z_049047bd-62a1-487c-be3d-9d736a634d88 as client.crash failed: (None, b'2022-10-19T14:33:04.552+0200 7ffa79385700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (2) No such file or directory\n2022-10-19T14:33:04.552+0200 7ffa79385700 -1 AuthRegistry(0x7ffa74060610) no keyring found at /etc/pve/priv/ceph.client.crash.keyring, disabling cephx\n2022-10-19T14:33:04.552+0200 7ffa73fff700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (2) No such file or directory\n2022-10-19T14:33:04.552+0200 7ffa73fff700 -1 AuthRegistry(0x7ffa74065b80) no keyring found at /etc/pve/priv/ceph.client.crash.keyring, disabling cephx\n2022-10-19T14:33:04.556+0200 7ffa73fff700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (2) No such file or directory\n2022-10-19T14:33:04.556+0200 7ffa73fff700 -1 AuthRegistry(0x7ffa73ffe0d0) no keyring found at /etc/pve/priv/ceph.client.crash.keyring, disabling cephx\n[errno 2] RADOS object not found (error connecting to the cluster)\n')
Oct 19 14:33:04 nod150a12 ceph-crash[1299]: WARNING:ceph-crash:post /var/lib/ceph/crash/2022-10-19T12:19:27.279763Z_049047bd-62a1-487c-be3d-9d736a634d88 as client.admin failed: (None, b'')
Oct 19 14:33:04 nod150a12 ceph-crash[1299]: WARNING:ceph-crash:post /var/lib/ceph/crash/2022-10-19T12:19:28.635136Z_0971fd4f-1856-4cb6-9098-49b28654334b as client.crash.nod150a12 failed: (None, b'2022-10-19T14:33:04.768+0200 7fbfaee40700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.nod150a12.keyring: (2) No such file or directory\n2022-10-19T14:33:04.768+0200 7fbfaee40700 -1 AuthRegistry(0x7fbfa8060670) no keyring found at /etc/pve/priv/ceph.client.crash.nod150a12.keyring, disabling cephx\n2022-10-19T14:33:04.772+0200 7fbfadbde700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.nod150a12.keyring: (2) No such file or directory\n2022-10-19T14:33:04.772+0200 7fbfadbde700 -1 AuthRegistry(0x7fbfa8065ca0) no keyring found at /etc/pve/priv/ceph.client.crash.nod150a12.keyring, disabling cephx\n2022-10-19T14:33:04.772+0200 7fbfadbde700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.nod150a12.keyring: (2) No such file or directory\n2022-10-19T14:33:04.772+0200 7fbfadbde700 -1 AuthRegistry(0x7fbfadbdd0d0) no keyring found at /etc/pve/priv/ceph.client.crash.nod150a12.keyring, disabling cephx\n[errno 2] RADOS object not found (error connecting to the cluster)\n')
Oct 19 14:33:04 nod150a12 ceph-crash[1299]: WARNING:ceph-crash:post /var/lib/ceph/crash/2022-10-19T12:19:28.635136Z_0971fd4f-1856-4cb6-9098-49b28654334b as client.crash failed: (None, b'2022-10-19T14:33:04.820+0200 7eff1dd82700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (2) No such file or directory\n2022-10-19T14:33:04.820+0200 7eff1dd82700 -1 AuthRegistry(0x7eff18060610) no keyring found at /etc/pve/priv/ceph.client.crash.keyring, disabling cephx\n2022-10-19T14:33:04.824+0200 7eff1dd82700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (2) No such file or directory\n2022-10-19T14:33:04.824+0200 7eff1dd82700 -1 AuthRegistry(0x7eff18065b80) no keyring found at /etc/pve/priv/ceph.client.crash.keyring, disabling cephx\n2022-10-19T14:33:04.824+0200 7eff1dd82700 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (2) No such file or directory\n2022-10-19T14:33:04.824+0200 7eff1dd82700 -1 AuthRegistry(0x7eff1dd810d0) no keyring found at /etc/pve/priv/ceph.client.crash.keyring, disabling cephx\n[errno 2] RADOS object not found (error connecting to the cluster)\n')
Oct 19 14:33:04 nod150a12 ceph-crash[1299]: WARNING:ceph-crash:post /var/lib/ceph/crash/2022-10-19T12:19:28.635136Z_0971fd4f-1856-4cb6-9098-49b28654334b as client.admin failed: (None, b'')

Es handelt sich um einen relativ frischen 4-Node-Ceph-Cluster mit jeweils 5 OSD´s.

Code:
proxmox-ve: 7.2-1 (running kernel: 5.15.60-2-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-helper: 7.2-13
pve-kernel-5.15: 7.2-12
pve-kernel-5.15.60-2-pve: 5.15.60-2
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph: 17.2.4-pve1
ceph-fuse: 17.2.4-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-3
libpve-guest-common-perl: 4.1-3
libpve-http-server-perl: 4.1-4
libpve-storage-perl: 7.2-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-4
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-3
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!