# Warning message about keyring component metadata query service in error.log

**URL:** <https://forums.percona.com/t/warning-message-about-keyring-component-metadata-query-service-in-error-log/11892>\
**Category:** Percona Server for MySQL 8.0\
**Created:** [August 24, 2021, 8:25am UTC](https://forums.percona.com/t/warning-message-about-keyring-component-metadata-query-service-in-error-log/11892 "2021-08-24T08:25:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Serhii\_Bulieienko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/serhii_bulieienko/32/4295_2.png) [@Serhii\_Bulieienko](https://forums.percona.com/u/Serhii_Bulieienko)\
**Post date:** [August 24, 2021, 8:25am UTC](https://forums.percona.com/t/warning-message-about-keyring-component-metadata-query-service-in-error-log/11892/1 "2021-08-24T08:25:33Z")

</div>

Hello,  
After upgrade the Percona MySQL 8.0.23 to 8.0.25 I see every night the warning in error log like this:  
**2021-08-23T21:00:02.911820Z 229549 [Warning] [MY013712] [Server] No suitable ‘keyring\_component\_metadata\_query’ service implementation found to fulfill the request.**

The next plugin is loaded automatically since version 8.0.24 of Oracle MySQL .  
root@localhost[(none)]\> show plugins;  
±--------------------------------±---------±-------------------±-------------------±--------+  
| Name | Status | Type | Library | License |  
±--------------------------------±---------±-------------------±-------------------±--------+  
| daemon\_keyring\_proxy\_plugin | ACTIVE | DAEMON | NULL | GPL |

The keyring component is not installed:  
root@localhost[(none)]\> SELECT \* FROM performance\_schema.keyring\_component\_status;  
Empty set (0.00 sec)

Do you know how to configure the server to prevent this message to be appear in the log?

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [August 24, 2021, 2:30pm UTC](https://forums.percona.com/t/warning-message-about-keyring-component-metadata-query-service-in-error-log/11892/2 "2021-08-24T14:30:44Z")

</div>

Hello @Serhii_Bulieienko,  
This is a known upstream bug [MySQL Bugs: #103684: Warning issued when querying ps. keyring\_component\_status](https://bugs.mysql.com/bug.php?id=103684)  
We have to wait for Oracle/MySQL to publish a fix. Feel free to comment on the bug to increase awareness.

---

<div class="post-metadata">

**Author:** ![bthnklc](https://avatars.discourse-cdn.com/v4/letter/b/e0b2c6/32.png) [@bthnklc](https://forums.percona.com/u/bthnklc)\
**Post date:** [January 2, 2025, 6:47am UTC](https://forums.percona.com/t/warning-message-about-keyring-component-metadata-query-service-in-error-log/11892/3 "2025-01-02T06:47:57Z")

</div>

> [@matthewb](#):
>
> This is a known upstream bug [MySQL Bugs: #103684: Warning issued when querying ps. keyring\_component\_status](https://bugs.mysql.com/bug.php?id=103684)  
> We have to wait for Oracle/MySQL to publish a fix. Feel free to comment on the bug to increase awareness.

Hi @matthewb ,

We use database version is 8.0.36  
Server version: 8.0.36-28.1 Percona XtraDB Cluster (GPL), Release rel28, Revision bfb687f, WSREP version 26.1.4.3  
but we take same warning.  
2025-01-02T01:00:01.220429+03:00 126448 [Warning] [MY-013712] [Server] No suitable ‘keyring\_component\_metadata\_query’ service implementation found to fulfill the request.

Is it important warning ?  
What kind of problems might we experience as a result of this error?

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [January 2, 2025, 2:41pm UTC](https://forums.percona.com/t/warning-message-about-keyring-component-metadata-query-service-in-error-log/11892/4 "2025-01-02T14:41:26Z")

</div>

There are no problems with this warning. The bug is still present in 8.0.38, so Oracle isn’t prioritizing this annoyance. You could install the keyring component with defaults to remove the message.