[Duplicate] MGR log spoiled with auth: could not find secret_id


Well-Known Member
Mar 4, 2014
my cluster is not healthy, means there were many slow request and unknown pgs.
Then I noticed an error message that spoiled the MGR log heavily:
2019-11-13 12:09:34.684 7fc46549b700 0 auth: could not find secret_id=4027
2019-11-13 12:09:34.684 7fc46549b700 0 cephx: verify_authorizer could not get service secret for service mgr secret_id=4027

The secret_id can differ depending when I look into the log.
However these errors are getting more and more, and it seems that this is slowing down the recovery process of the cluster.
Ultimately I don't get a healthy cluster.

I would like to understand what is causing this error message or at least how it can be prevented.
Would it be possible to stop cephx authentication?

Please don't double post.

Judging from your other thread, it may be that the device health scrapping of Ceph might lead to those message. If you have it turned on, try to disable it and see if those messages persist.

Would it be possible to stop cephx authentication?
Possible, yes. Depending on environment, unauthorized third party clients can access the ceph cluster too.
I will close this ticket because it's a duplicate.
My last comment is:
I executed
ceph device monitoring off
already before and this is not a solution.

  • Like
Reactions: Alwin


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!