Hello,
on my system it solved it but then a different node suddenly started
the same error. I tried it on the new problem and it did not help.
I notice on:
https://tracker.ceph.com/issues/45726
it says resolved, but on next version v15.2.5
___
Did this solved your issue?
On Wed, Jul 22, 2020 at 2:06 AM wrote:
> Hi!
> I have, or actually had a similar problem.
> I found the solution on this page:
> https://segmentfault.com/a/119023292938
> I used the commands:
> > ceph auth add client.crash.nodeX.xxx.com mgr "profile crash" mon
>
Hi!
I have, or actually had a similar problem.
I found the solution on this page:
https://segmentfault.com/a/119023292938
I used the commands:
> ceph auth add client.crash.nodeX.xxx.com mgr "profile crash" mon "profile
> crash"
___
ceph-users
>> caps mgr = "profile crash"
>> caps mon = "profile crash"
>>I added that back in and now its OK.
>> /var/lib/ceph/./crash.node1/keyring
do you add thsoe "caps" line into the "crash.node1/keyring" file or any other
files?
___
ceph-users mailing list
should the key be the same on all 3 servers?
The values in the fiel are all different:
/var/lib/ceph/474629b4-bd04-11ea-a0bb-sfsfsfdsfs/crash.ceph0-ote/keyring
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to
Hello,
same here. My fix was to examine the keyring file in the misbehaving
server and compare to a different server, I found the file had the key
but was missing:
caps mgr = "profile crash"
caps mon = "profile crash"
I added that back in and now its OK.
/var/lib/ceph/./crash.node1/keyring
No
https://tracker.ceph.com/issues/45726
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
Biohazard;
This looks like a fairly simple authentication issue. It looks like the
keyring(s) available to the command don't contain a key which meets the
commands needs.
Have you verified the presence and accuracy of your keys?
Thank you,
Dominic L. Hilsbos, MBA
Director - Information
