No keys found after refresh

Hello,

After performing a minor upgrade from MongoDB 6.0.8 to 6.0.11 I’m receiving the bellow spam in logs.
{“t”:{“$date”:“2023-10-16T08:30:36.811+00:00”},“s”:“I”, “c”:“-”, “id”:4939300, “ctx”:“monitoring-keys-for-HMAC”,“msg”:“Failed to refresh key cache”,“attr”:{“error”:“KeyNotFound: No keys found after refre
sh”,“nextWakeupMillis”:22200}}
{“t”:{“$date”:“2023-10-16T08:30:59.031+00:00”},“s”:“I”, “c”:“-”, “id”:4939300, “ctx”:“monitoring-keys-for-HMAC”,“msg”:“Failed to refresh key cache”,“attr”:{“error”:“KeyNotFound: No keys found after refre
sh”,“nextWakeupMillis”:22400}}
{“t”:{“$date”:“2023-10-16T08:31:21.442+00:00”},“s”:“I”, “c”:“-”, “id”:4939300, “ctx”:“monitoring-keys-for-HMAC”,“msg”:“Failed to refresh key cache”,“attr”:{“error”:“KeyNotFound: No keys found after refre
sh”,“nextWakeupMillis”:22600}}
{“t”:{“$date”:“2023-10-16T08:31:44.060+00:00”},“s”:“I”, “c”:“-”, “id”:4939300, “ctx”:“monitoring-keys-for-HMAC”,“msg”:“Failed to refresh key cache”,“attr”:{“error”:“KeyNotFound: No keys found after refre
sh”,“nextWakeupMillis”:22800}}
{“t”:{“$date”:“2023-10-16T08:32:06.883+00:00”},“s”:“I”, “c”:“-”, “id”:4939300, “ctx”:“monitoring-keys-for-HMAC”,“msg”:“Failed to refresh key cache”,“attr”:{“error”:“KeyNotFound: No keys found after refre
sh”,“nextWakeupMillis”:23000}}
{“t”:{“$date”:“2023-10-16T08:32:29.891+00:00”},“s”:“I”, “c”:“-”, “id”:4939300, “ctx”:“monitoring-keys-for-HMAC”,“msg”:“Failed to refresh key cache”,“attr”:{“error”:“KeyNotFound: No keys found after refre
sh”,“nextWakeupMillis”:23200}}
{“t”:{“$date”:“2023-10-16T08:32:53.114+00:00”},“s”:“I”, “c”:“-”, “id”:4939300, “ctx”:“monitoring-keys-for-HMAC”,“msg”:“Failed to refresh key cache”,“attr”:{“error”:“KeyNotFound: No keys found after refre
sh”,“nextWakeupMillis”:23400}}
{“t”:{“$date”:“2023-10-16T08:33:16.535+00:00”},“s”:“I”, “c”:“-”, “id”:4939300, “ctx”:“monitoring-keys-for-HMAC”,“msg”:“Failed to refresh key cache”,“attr”:{“error”:“KeyNotFound: No keys found after refre
sh”,“nextWakeupMillis”:23600}}

Cluster status look ok and no error was observed there.

Any ideas why is happening this?

Thank you!

Hello,

Any news?

Thank you!

Hi dude,

Did you find a solution for this one? xd