ceph keyring directory empty

M

mpopgun

New Member
May 11, 2023
8
0
1
Good evening everybody,
I rebooted and one of my ceph OSDs wouldn't come back up. Got the following error:

auth: unable to find a keyring on /var/lib/ceph/osd/ceph-3/keyring: (13) Permission denied

I went to that dir...ceph-3 and it was empty. First question...any idea what triggers this thing to be empty?

So i set about making it less empty. Performed these steps:
  1. ceph auth list to get the key
  2. ceph auth export osd.13 -o osd.13.export
  3. created a keyring file in osd.3 and copied over the osd.13 keyring, renamed it to osd.3, replaced it's key with the one I got from ceph auth list
  4. copied over the whoami, status, and type files...changed groups and permissions to ceph
  5. modified osd.13.export w/ osd.3's keyring and name
  6. ceph auth import -i osd.13.export
Then it wanted the superblock file recreated - ceph-osd --mkfs --data-path /var/lib/ceph/osd/ceph-3

But it can't find a keyring in a dir that doesn't exist..../var/lib/ceph/osd/ceph-admin/keyring ....None of my other nodes have this dir...so I guess PVE has a different location?

How can I recreate this file and get the OSD back on line pls? Also what did i touch to lose the contents of this directory?

thanks!
 
Hello could you please share with us the exact error as it appears in your journal? The reason is that there is a bug that would print a similar message [1]. The bug is mostly harmless, so there is probably something else going on.

Could you please send us the system logs containing an attempt at setting the OSD as up?

[1] https://bugzilla.proxmox.com/show_bug.cgi?id=4759
 
Last edited:
Could you please send us the output of

Code: 
lvs -oname,tags --reportformat json

Please use a code block.

What about the output of

Code: 
systemctl status ceph-osd@13.service

?
 
The logfile is too big to attach...here is what i think the important sections look like

This is what it started out as:

Code: 
Mar 04 08:15:57 proxmox8 ceph-crash[710]: WARNING:ceph-crash:post /var/lib/ceph/crash/2023-12-12T15:34:18.048067Z_c0f3daac-4efe-4986-a700-1dbf50474304 as client.crash.proxmox8 failed: 2024-03-04T08:15:57.146-0500 719e3ea716c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.proxmox8.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.150-0500 719e3ea716c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.proxmox8.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.150-0500 719e3ea716c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.proxmox8.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.150-0500 719e3ea716c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.proxmox8.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.150-0500 719e3ea716c0 -1 monclient: keyring not found
Mar 04 08:15:57 proxmox8 ceph-crash[710]: [errno 13] RADOS permission denied (error connecting to the cluster)
Mar 04 08:15:57 proxmox8 ceph-crash[710]: WARNING:ceph-crash:post /var/lib/ceph/crash/2023-12-12T15:34:18.048067Z_c0f3daac-4efe-4986-a700-1dbf50474304 as client.crash failed: 2024-03-04T08:15:57.238-0500 7d73c68446c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.238-0500 7d73c68446c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.238-0500 7d73c68446c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.238-0500 7d73c68446c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.238-0500 7d73c68446c0 -1 monclient: keyring not found
Mar 04 08:15:57 proxmox8 ceph-crash[710]: [errno 13] RADOS permission denied (error connecting to the cluster)
Mar 04 08:15:57 proxmox8 ceph-crash[710]: WARNING:ceph-crash:post /var/lib/ceph/crash/2023-12-12T15:34:18.048067Z_c0f3daac-4efe-4986-a700-1dbf50474304 as client.admin failed: 2024-03-04T08:15:57.326-0500 789be06106c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.330-0500 789be06106c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.330-0500 789be06106c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.330-0500 789be06106c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.330-0500 789be06106c0 -1 monclient: keyring not found
Mar 04 08:15:57 proxmox8 ceph-crash[710]: [errno 13] RADOS permission denied (error connecting to the cluster)
Mar 04 08:15:57 proxmox8 ceph-crash[710]: WARNING:ceph-crash:post /var/lib/ceph/crash/2024-02-27T14:03:18.012659Z_a54822da-8e03-491d-bccc-1ded9c5ae7f5 as client.crash.proxmox8 failed: 2024-03-04T08:15:57.418-0500 7a1c8eb326c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.proxmox8.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.418-0500 7a1c8eb326c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.proxmox8.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.418-0500 7a1c8eb326c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.proxmox8.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.418-0500 7a1c8eb326c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.proxmox8.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.418-0500 7a1c8eb326c0 -1 monclient: keyring not found
Mar 04 08:15:57 proxmox8 ceph-crash[710]: [errno 13] RADOS permission denied (error connecting to the cluster)
Mar 04 08:15:57 proxmox8 ceph-crash[710]: WARNING:ceph-crash:post /var/lib/ceph/crash/2024-02-27T14:03:18.012659Z_a54822da-8e03-491d-bccc-1ded9c5ae7f5 as client.crash failed: 2024-03-04T08:15:57.510-0500 77590d9566c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.514-0500 77590d9566c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.514-0500 77590d9566c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.514-0500 77590d9566c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.crash.keyring: (13) Permission denied
Mar 04 08:15:57 proxmox8 ceph-crash[710]: 2024-03-04T08:15:57.514-0500 77590d9566c0 -1 monclient: keyring not found
Mar 04 08:15:57 proxmox8 ceph-crash[710]: [errno 13] RADOS permission denied (error connecting to the cluster)

This is new: Possibly from the commands listed above. I checked, and all the time is accurate to within 1 second, which is all i can see in proxmox, so i'm assuming the time is correct, i just messed with something with all the key commands yesterday.

Code: 
Mar 04 19:51:07 proxmox8 ceph-osd[1525]: 2024-03-04T19:51:07.451-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-04T18:51:07.455267-0500)
Mar 04 19:51:08 proxmox8 ceph-osd[1525]: 2024-03-04T19:51:08.451-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-04T18:51:08.455365-0500)
Mar 04 19:51:09 proxmox8 ceph-osd[1525]: 2024-03-04T19:51:09.451-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-04T18:51:09.455588-0500)
Mar 04 19:51:10 proxmox8 ceph-osd[1525]: 2024-03-04T19:51:10.451-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-04T18:51:10.455814-0500)
Mar 04 19:51:11 proxmox8 ceph-osd[1525]: 2024-03-04T19:51:11.451-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-04T18:51:11.456008-0500)


let me know if there is anything else in a log somewhere that will help. Thanks!
 
Maximiliano said:
Could you please send us the output of

Code: 
lvs -oname,tags --reportformat json

Please use a code block.

What about the output of

Code: 
systemctl status ceph-osd@13.service

?
Click to expand...
Code: 
@proxmox8:~# lvs -oname,tags --reportformat json
  {
      "report": [
          {
              "lv": [
                  {"lv_name":"osd-block-4b6017ce-4ffd-4577-9383-95c90f2c551a", "lv_tags":"ceph.block_device=/dev/ceph-ca6c07be-f138-43b1-b93c-0f15b8266af4/osd-block-4b6017ce-4ffd-4577-9383-95c90f2c551a,ceph.block_uuid=2GyXo9-8tgT-yVF4-l7pm-AWMJ-g152-HA32Aj,ceph.cephx_lockbox_secret=,ceph.cluster_fsid=a1e39d9f-8c9f-44de-9cf1-c717a685ec53,ceph.cluster_name=ceph,ceph.crush_device_class=ssd,ceph.encrypted=0,ceph.osd_fsid=4b6017ce-4ffd-4577-9383-95c90f2c551a,ceph.osd_id=13,ceph.osdspec_affinity=,ceph.type=block,ceph.vdo=0"},
                  {"lv_name":"data", "lv_tags":""},
                  {"lv_name":"root", "lv_tags":""},
                  {"lv_name":"swap", "lv_tags":""}
              ]
          }
      ]
  }

Code: 
 systemctl status ceph-osd@13.service
● ceph-osd@13.service - Ceph object storage daemon osd.13
     Loaded: loaded (/lib/systemd/system/ceph-osd@.service; enabled-runtime; preset: enabled)
    Drop-In: /usr/lib/systemd/system/ceph-osd@.service.d
             └─ceph-after-pve-cluster.conf
     Active: active (running) since Mon 2024-03-04 17:11:20 EST; 16h ago
   Main PID: 1525 (ceph-osd)
      Tasks: 76
     Memory: 6.5G
        CPU: 33min 34.723s
     CGroup: /system.slice/system-ceph\x2dosd.slice/ceph-osd@13.service
             └─1525 /usr/bin/ceph-osd -f --cluster ceph --id 13 --setuser ceph --setgroup ceph

Mar 05 09:49:43 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:43.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 20>
Mar 05 09:49:44 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:44.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 20>
Mar 05 09:49:45 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:45.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 20>
Mar 05 09:49:46 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:46.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 20>
Mar 05 09:49:47 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:47.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 20>
Mar 05 09:49:48 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:48.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 20>
Mar 05 09:49:49 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:49.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 20>
Mar 05 09:49:50 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:50.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 20>
Mar 05 09:49:51 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:51.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 20>
Mar 05 09:49:52 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:52.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 20>
lines 1-22/22 (END)
● ceph-osd@13.service - Ceph object storage daemon osd.13
     Loaded: loaded (/lib/systemd/system/ceph-osd@.service; enabled-runtime; preset: enabled)
    Drop-In: /usr/lib/systemd/system/ceph-osd@.service.d
             └─ceph-after-pve-cluster.conf
     Active: active (running) since Mon 2024-03-04 17:11:20 EST; 16h ago
   Main PID: 1525 (ceph-osd)
      Tasks: 76
     Memory: 6.5G
        CPU: 33min 34.723s
     CGroup: /system.slice/system-ceph\x2dosd.slice/ceph-osd@13.service
             └─1525 /usr/bin/ceph-osd -f --cluster ceph --id 13 --setuser ceph --setgroup ceph

Mar 05 09:49:43 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:43.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:43.6>
Mar 05 09:49:44 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:44.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:44.6>
Mar 05 09:49:45 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:45.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:45.6>
Mar 05 09:49:46 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:46.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:46.6>
Mar 05 09:49:47 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:47.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:47.6>
Mar 05 09:49:48 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:48.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:48.6>
Mar 05 09:49:49 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:49.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:49.6>
Mar 05 09:49:50 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:50.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:50.6>
Mar 05 09:49:51 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:51.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:51.6>
Mar 05 09:49:52 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:52.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:52.6>
~
~
~
~
~
~
~
~
~
~
lines 1-22/22 (END)...skipping...
● ceph-osd@13.service - Ceph object storage daemon osd.13
     Loaded: loaded (/lib/systemd/system/ceph-osd@.service; enabled-runtime; preset: enabled)
    Drop-In: /usr/lib/systemd/system/ceph-osd@.service.d
             └─ceph-after-pve-cluster.conf
     Active: active (running) since Mon 2024-03-04 17:11:20 EST; 16h ago
   Main PID: 1525 (ceph-osd)
      Tasks: 76
     Memory: 6.5G
        CPU: 33min 34.723s
     CGroup: /system.slice/system-ceph\x2dosd.slice/ceph-osd@13.service
             └─1525 /usr/bin/ceph-osd -f --cluster ceph --id 13 --setuser ceph --setgroup ceph

Mar 05 09:49:43 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:43.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:43.684148-0500)
Mar 05 09:49:44 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:44.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:44.684364-0500)
Mar 05 09:49:45 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:45.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:45.684476-0500)
Mar 05 09:49:46 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:46.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:46.684604-0500)
Mar 05 09:49:47 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:47.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:47.684754-0500)
Mar 05 09:49:48 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:48.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:48.684877-0500)
Mar 05 09:49:49 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:49.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:49.684963-0500)
Mar 05 09:49:50 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:50.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:50.685132-0500)
Mar 05 09:49:51 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:51.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:51.685219-0500)
Mar 05 09:49:52 proxmox8 ceph-osd[1525]: 2024-03-05T09:49:52.680-0500 72de3d0e16c0 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2024-03-05T08:49:52.685335-0500)

I haven't seen this before...i think it's due to the commands I ran yesterday. MIght have made things worse. 13 is up and in at the moment...3 is down and out.
 
Oh my bad, please give me the output of `systemctl status ceph-osd@3.service` as I made at typo and added a `1`.
 
No worries...i knew it would be confusing...just so happens 3 and 13 are on the same node.

Code: 
proxmox8:~# systemctl status ceph-osd@3.service
× ceph-osd@3.service - Ceph object storage daemon osd.3
     Loaded: loaded (/lib/systemd/system/ceph-osd@.service; disabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/ceph-osd@.service.d
             └─ceph-after-pve-cluster.conf
     Active: failed (Result: exit-code) since Mon 2024-03-04 17:58:38 EST; 16h ago
   Duration: 152ms
    Process: 26530 ExecStartPre=/usr/libexec/ceph/ceph-osd-prestart.sh --cluster ${CLUSTER} --id 3 (code=exited, status=0/SUCCESS)
    Process: 26534 ExecStart=/usr/bin/ceph-osd -f --cluster ${CLUSTER} --id 3 --setuser ceph --setgroup ceph (code=exited, status=1/FAILURE)
   Main PID: 26534 (code=exited, status=1/FAILURE)
        CPU: 59ms

Mar 04 17:58:38 proxmox8 systemd[1]: ceph-osd@3.service: Scheduled restart job, restart counter is at 3.
Mar 04 17:58:38 proxmox8 systemd[1]: Stopped ceph-osd@3.service - Ceph object storage daemon osd.3.
Mar 04 17:58:38 proxmox8 systemd[1]: ceph-osd@3.service: Start request repeated too quickly.
Mar 04 17:58:38 proxmox8 systemd[1]: ceph-osd@3.service: Failed with result 'exit-code'.
Mar 04 17:58:38 proxmox8 systemd[1]: Failed to start ceph-osd@3.service - Ceph object storage daemon osd.3.
 
It's spreading:

Code: 
Mar 05 15:51:24 proxmox6 ceph-crash[702]: [errno 13] RADOS permission denied (error connecting to the cluster)
Mar 05 15:51:24 proxmox6 ceph-crash[702]: WARNING:ceph-crash:post /var/lib/ceph/crash/2023-12-12T15:34:18.987943Z_98c90261-f68b-4d07-bb68-ef492263064b as client.admin failed: 2024-03-05T15:51:24.270-0500 7f936a41c6c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied
Mar 05 15:51:24 proxmox6 ceph-crash[702]: 2024-03-05T15:51:24.274-0500 7f936a41c6c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied
Mar 05 15:51:24 proxmox6 ceph-crash[702]: 2024-03-05T15:51:24.274-0500 7f936a41c6c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied
Mar 05 15:51:24 proxmox6 ceph-crash[702]: 2024-03-05T15:51:24.274-0500 7f936a41c6c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied
Mar 05 15:51:24 proxmox6 ceph-crash[702]: 2024-03-05T15:51:24.274-0500 7f936a41c6c0 -1 monclient: keyring not found
Mar 05 15:51:24 proxmox6 ceph-crash[702]: [errno 13] RADOS permission denied (error connecting to the cluster)

I see this error now:
Code: 
1 monclient(hunting): handle_auth_bad_method server allowed_methods [2] but i only support [2]
 
Last edited:
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back