# \[PS 8.4.4\] Keyvault component doen't launch **URL:** \ **Category:** Percona Server for MySQL 8.0\ **Created:** [May 21, 2025, 6:32am UTC](https://forums.percona.com/t/ps-8-4-4-keyvault-component-doent-launch/38034 "2025-05-21T06:32:41Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Valentin\_TRAEN1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/valentin_traen1/32/21062_2.png) [@Valentin\_TRAEN1](https://forums.percona.com/u/Valentin_TRAEN1)\ **Post date:** [May 21, 2025, 6:32am UTC](https://forums.percona.com/t/ps-8-4-4-keyvault-component-doent-launch/38034/1 "2025-05-21T06:32:41Z")
Has anyone tested the PS 8.4 component\_keyring\_vault component? With the global manifest I have this error: ```auto `May 20 12:26:54 server_name systemd[1]: Starting Percona Server...` `May 20 12:26:54 server_name mysqld[3277351]: 2025-05-20T10:26:54Z UTC - mysqld got signal 11 ;` `May 20 12:26:54 server_name mysqld[3277351]: Signal SIGSEGV (Address not mapped to object) at address 0x1b` `May 20 12:26:54 server_name mysqld[3277351]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.` `May 20 12:26:54 server_name mysqld[3277351]: BuildID[sha1]=` `May 20 12:26:54 server_name mysqld[3277351]: Server Version: Percona Server (GPL), Release '4', Revision '844fde07'` `May 20 12:26:54 server_name mysqld[3277351]: Thread pointer: 0x0` `May 20 12:26:54 server_name mysqld[3277351]: Attempting backtrace. You can use the following information to find out` `May 20 12:26:54 server_name mysqld[3277351]: where mysqld died. If you see no messages after this, something went` `May 20 12:26:54 server_name mysqld[3277351]: terribly wrong...` `May 20 12:26:54 server_name mysqld[3277351]: stack_bottom = 0 thread_stack 0x10000` `May 20 12:26:54 server_name mysqld[3277351]: #0 0x561edf48f2eb _Z19my_print_stacktracePKhm` `May 20 12:26:54 server_name mysqld[3277351]: #1 0x561ede585452 ` `May 20 12:26:54 server_name mysqld[3277351]: #2 0x561ede5858b4 _Z19handle_fatal_signaliP9siginfo_tPv` `May 20 12:26:54 server_name mysqld[3277351]: #3 0x7f1a0224813f ` `May 20 12:26:54 server_name mysqld[3277351]: #4 0x7f1a01a87b78 ` `May 20 12:26:54 server_name mysqld[3277351]: #5 0x7f1a0197ec37 ` `May 20 12:26:54 server_name mysqld[3277351]: #6 0x7f1a0198f6c5 ` `May 20 12:26:54 server_name mysqld[3277351]: #7 0x561edfde2bda _ZN23log_builtins_string_imp11substitutevEPcmPKcP13__va_list_tag` `May 20 12:26:54 server_name mysqld[3277351]: #8 0x7f19de69d9f2 ` `May 20 12:26:54 server_name mysqld[3277351]: #9 0x7f19de69dbb5 ` `May 20 12:26:54 server_name mysqld[3277351]: #10 0x7f19de6b0a4f ` `May 20 12:26:54 server_name mysqld[3277351]: #11 0x561edfdf1692 _Z41set_srv_keyring_implementation_as_defaultv` `May 20 12:26:54 server_name mysqld[3277351]: #12 0x561ede2a5e8e _Z11mysqld_mainiPPc` `May 20 12:26:54 server_name mysqld[3277351]: #13 0x7f1a01939d79 __libc_start_main` `May 20 12:26:54 server_name mysqld[3277351]: #14 0x561ede0cbe19 _start` `May 20 12:26:54 server_name mysqld[3277351]: #15 0xffffffffffffffff ` `May 20 12:26:54 server_name mysqld[3277351]: Please help us make Percona Server better by reporting any` `May 20 12:26:54 server_name mysqld[3277351]: bugs at ` `https://bugs.percona.com/` `May 20 12:26:54 server_name mysqld[3277351]: You may download the Percona Server operations manual by visiting` `May 20 12:26:54 server_name mysqld[3277351]: ` `http://www.percona.com/software/percona-server/` `. You may find information` `May 20 12:26:54 server_name mysqld[3277351]: in the manual which will help you identify the cause of the crash.` `May 20 12:26:54 server_name systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT` `May 20 12:26:54 server_name systemd[1]: mysql.service: Failed with result 'exit-code'.` `May 20 12:26:54 server_name systemd[1]: Failed to start Percona Server.` `May 20 12:26:55 server_name systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.` `May 20 12:26:55 server_name systemd[1]: Stopped Percona Server.` `May 20 12:26:55 server_name systemd[1]: mysql.service: Start request repeated too quickly.` `May 20 12:26:55 server_name systemd[1]: mysql.service: Failed with result 'exit-code'.` `May 20 12:26:55 server_name systemd[1]: Failed to start Percona Server.` ``` With the local manifest, PS starts but the component is not active. > **[Jira](https://perconadev.atlassian.net/browse/PS-9813?atlOrigin=eyJpIjoiZWJjNDBmMDdjNWI4NDgyNWIxZDIzMjU3YzEwOWJlMGUiLCJwIjoiaiJ9)** ---
**Author:** ![lalit.choudhary](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lalit.choudhary/32/51_2.png) [@lalit.choudhary](https://forums.percona.com/u/lalit.choudhary)\ **Post date:** [May 21, 2025, 6:37am UTC](https://forums.percona.com/t/ps-8-4-4-keyvault-component-doent-launch/38034/2 "2025-05-21T06:37:04Z")
Hello @Valentin_TRAEN1 what steps you followed ? If you are upgrading from 8.0 to 8.4 then, Here is doc for Transition a plugin to a component: > **[Upgrading from plugins to components - Percona Server for MySQL](https://docs.percona.com/percona-server/8.4/upgrade-components.html#transition-a-plugin-to-a-component)** > > The following plugins have changed: Please try this doc steps for transitioning a plugin to a component. ---
**Author:** ![Valentin\_TRAEN1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/valentin_traen1/32/21062_2.png) [@Valentin\_TRAEN1](https://forums.percona.com/u/Valentin_TRAEN1)\ **Post date:** [May 21, 2025, 6:44am UTC](https://forums.percona.com/t/ps-8-4-4-keyvault-component-doent-launch/38034/3 "2025-05-21T06:44:46Z")
Hi, At the moment I’m starting with a fresh install of PS 8.4 (no upgrade) and just trying to get it working. I followed: [Use the keyring vault component - Percona Server for MySQL](https://docs.percona.com/percona-server/8.4/use-keyring-vault-component.html) As soon as I create the file /usr/sbin/mysqld.my containing ```auto { "components": "file://component_keyring_vault" } ``` PS crash. On the other hand, if I do the same thing with the Oracle component ```auto { "components": "file://component_keyring_file" } ``` there, PS starts (but it is not the component I need!). I also specify that each time I start with a new installation. I also have created the /usr/lib/mysql/plugin/component\_keyring\_vault.cnf file with : ```auto { "vault_url" : "[hidden]", "secret_mount_point" : "[hidden]_kv", "secret_mount_point_version" : "AUTO", "token" : "hvs.[hidden]", "vault_ca" : "[hidden]" } ``` which contains the same information as the module in PS 8.0 ---
**Author:** ![Yunus](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/yunus/32/6430_2.png) [@Yunus](https://forums.percona.com/u/Yunus)\ **Post date:** [May 21, 2025, 12:35pm UTC](https://forums.percona.com/t/ps-8-4-4-keyvault-component-doent-launch/38034/4 "2025-05-21T12:35:11Z")
Please use this document > **[Use the keyring vault component - Percona Server for MySQL](https://docs.percona.com/percona-server/8.4/use-keyring-vault-component.html)** > > The keyring\_vault component extends the server capabilities and provides an interface for the database with a HashiCorp Vault server to store key and secure encryption keys. for configuration file format and add the values there. Also, is your operating system 64 bit? > [@Valentin\_TRAEN1](#): > > I also have created the /usr/lib/mysql/plugin/component\_keyring\_vault.cnf file with : Is your plugin directory proper? You can check the plugin directory using your variables. Also check ```auto rpm -qa |grep -i percona-server ``` Component should load when you add a manifest file and just look for configuration file in the plugin directory and start. If it could not load component, the mysql start should not fail. The component will just be inactive. ---
**Author:** ![Valentin\_TRAEN1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/valentin_traen1/32/21062_2.png) [@Valentin\_TRAEN1](https://forums.percona.com/u/Valentin_TRAEN1)\ **Post date:** [May 21, 2025, 1:09pm UTC](https://forums.percona.com/t/ps-8-4-4-keyvault-component-doent-launch/38034/5 "2025-05-21T13:09:32Z")
Hi, This is the documentation I used. Yes, it’s a 64 bit Debian 11. Other plugins / components seems to work well except this one, but they are not launched “early”. The result of ` dpkg -l | grep -i percona-server` : ```auto ii percona-server-client 8.4.4-4-1.bullseye amd64 Percona Server database client binaries ii percona-server-common 8.4.4-4-1.bullseye amd64 Percona Server database common files (e.g. /etc/mysql/my.cnf) ii percona-server-server 8.4.4-4-1.bullseye amd64 Percona Server database server binaries ``` Other than this problem, PS works fine. I use the audit component (which seems buggy but still works), ldap authentication… I have declared my manifest and my configuration is there (see the file paths that I indicated above). If you can get it to work on your machine, can you tell me what files you created/configured, where you put them and with what rights/owner? I tried everything… ---
**Author:** ![Yunus](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/yunus/32/6430_2.png) [@Yunus](https://forums.percona.com/u/Yunus)\ **Post date:** [May 22, 2025, 4:28pm UTC](https://forums.percona.com/t/ps-8-4-4-keyvault-component-doent-launch/38034/6 "2025-05-22T16:28:01Z")
> [@Valentin\_TRAEN1](#): > > If you can get it to work on your machine, can you tell me what files you created/configured, where you put them and with what rights/owner? I upgraded from 8.0 plugin to 8.4 and It works fine ```auto mysql> select * from keyring_component_status; +----------------------------+---------------------------+ | STATUS_KEY | STATUS_VALUE | +----------------------------+---------------------------+ | Component_name | component_keyring_vault | | Author | Percona Corporation | | License | GPL | | Implementation_name | component_keyring_vault | | Version | 1.0 | | Component_status | Active | | timeout | 15 | | vault_url | https://x.x.x.x:8200 | | secret_mount_point | secretv2/mysql | | vault_ca | /etc/vault_ca/support.crt | | secret_mount_point_version | AUTO | +----------------------------+---------------------------+ 11 rows in set (0.00 sec) mysql> \s -------------- mysql Ver 8.0.41-32 for Linux on x86_64 (Percona Server (GPL), Release 32, Revision b8e378ec) Connection id: 212 Current database: performance_schema Current user: root@localhost SSL: Not in use Current pager: stdout Using outfile: '' Using delimiter: ; Server version: 8.4.4-4 Percona Server (GPL), Release 4, Revision 844fde07 ``` My config is here, ```auto [root@node0 /]# cat /usr/sbin/mysqld.my { "read_local_manifest": false, "components": "file://component_keyring_vault" } ``` And config file in plugin directory ```auto [root@node0 /]# cat /usr/lib64/mysql/plugin/component_keyring_vault.cnf { "timeout": 15, "vault_url": "https://x.x.x.x:8200", "secret_mount_point": "secretv2/mysql", "secret_mount_point_version": "AUTO", "token": "abcd", "vault_ca": "/etc/vault_ca/support.crt" } ``` Make sure your config file has proper format. Looking at your config file, the spacing doesn’t look good. ---
**Author:** ![Valentin\_TRAEN1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/valentin_traen1/32/21062_2.png) [@Valentin\_TRAEN1](https://forums.percona.com/u/Valentin_TRAEN1)\ **Post date:** [May 27, 2025, 5:53am UTC](https://forums.percona.com/t/ps-8-4-4-keyvault-component-doent-launch/38034/7 "2025-05-27T05:53:40Z")
Unfortunately that doesn’t change anything… I copied and pasted your files by adapting them with my values ​​but I still get the same error. What OS are you using? ---
**Author:** ![Valentin\_TRAEN1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/valentin_traen1/32/21062_2.png) [@Valentin\_TRAEN1](https://forums.percona.com/u/Valentin_TRAEN1)\ **Post date:** [May 27, 2025, 7:20am UTC](https://forums.percona.com/t/ps-8-4-4-keyvault-component-doent-launch/38034/8 "2025-05-27T07:20:24Z")
OMG…found it! It was just a typo in my token. I saw in my HV audits that the token did not have the right rights, and unlike before with the module, it crashes MySQL and does not put a clear message in the error log!