# I often encounter this problem when installing Percona XtraDB Cluster 8.0 on my Debian 11 operating system, causing a node's mysql to fail **URL:** \ **Category:** Percona XtraDB Cluster\ **Created:** [April 1, 2024, 6:50am UTC](https://forums.percona.com/t/i-often-encounter-this-problem-when-installing-percona-xtradb-cluster-8-0-on-my-debian-11-operating-system-causing-a-nodes-mysql-to-fail/29474 "2024-04-01T06:50:59Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![poplar.harry](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/poplar.harry/32/15871_2.png) [@poplar.harry](https://forums.percona.com/u/poplar.harry)\ **Post date:** [April 1, 2024, 6:50am UTC](https://forums.percona.com/t/i-often-encounter-this-problem-when-installing-percona-xtradb-cluster-8-0-on-my-debian-11-operating-system-causing-a-nodes-mysql-to-fail/29474/1 "2024-04-01T06:50:59Z")
This is a log error. I checked some information and couldn’t find a solution. Please help me take a look. 2024-03-14T11:10:01.964891Z 13311 [Warning] [MY-013360] [Server] Plugin mysql\_native\_password reported: ‘‘mysql\_native\_password’ is deprecated and will be removed in a future release. Please use caching\_sha2\_password instead’ 2024-03-14T11:10:01.975264Z 13311 [Warning] [MY-013712] [Server] No suitable ‘keyring\_component\_metadata\_query’ service implementation found to fulfill the request. 2024-03-14T11:10:01.975409Z 13311 [Warning] [MY-012637] [InnoDB] 16384 bytes should have been read. Only 0 bytes read. Retrying for the remaining bytes. 2024-03-14T11:10:01.975425Z 13311 [Warning] [MY-012637] [InnoDB] 16384 bytes should have been read. Only 0 bytes read. Retrying for the remaining bytes. 2024-03-14T11:10:01.975431Z 13311 [Warning] [MY-012637] [InnoDB] 16384 bytes should have been read. Only 0 bytes read. Retrying for the remaining bytes. 2024-03-14T11:10:01.975435Z 13311 [Warning] [MY-012637] [InnoDB] 16384 bytes should have been read. Only 0 bytes read. Retrying for the remaining bytes. 2024-03-14T11:10:01.975440Z 13311 [Warning] [MY-012637] [InnoDB] 16384 bytes should have been read. Only 0 bytes read. Retrying for the remaining bytes. 2024-03-14T11:10:01.975444Z 13311 [Warning] [MY-012637] [InnoDB] 16384 bytes should have been read. Only 0 bytes read. Retrying for the remaining bytes. 2024-03-14T11:10:01.975448Z 13311 [Warning] [MY-012637] [InnoDB] 16384 bytes should have been read. Only 0 bytes read. Retrying for the remaining bytes. 2024-03-14T11:10:01.975452Z 13311 [Warning] [MY-012637] [InnoDB] 16384 bytes should have been read. Only 0 bytes read. Retrying for the remaining bytes. 2024-03-14T11:10:01.975456Z 13311 [Warning] [MY-012637] [InnoDB] 16384 bytes should have been read. Only 0 bytes read. Retrying for the remaining bytes. 2024-03-14T11:10:01.975460Z 13311 [Warning] [MY-012637] [InnoDB] 16384 bytes should have been read. Only 0 bytes read. Retrying for the remaining bytes. 2024-03-14T11:10:01.975464Z 13311 [Warning] [MY-012638] [InnoDB] Retry attempts for reading partial data failed. 2024-03-14T11:10:01.975485Z 13311 [ERROR] [MY-012642] [InnoDB] Tried to read 16384 bytes at offset 0, but was only able to read 0 of FD 117, filename /data/mysqldata/#innodb\_temp/temp\_10.ibt 2024-03-14T11:10:01.975491Z 13311 [ERROR] [MY-012646] [InnoDB] File ./#innodb\_temp/temp\_10.ibt: ‘read’ returned OS error 0. Cannot continue operation 2024-03-14T11:10:01.975496Z 13311 [ERROR] [MY-012981] [InnoDB] Cannot continue operation. ---
**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:** [April 1, 2024, 3:58pm UTC](https://forums.percona.com/t/i-often-encounter-this-problem-when-installing-percona-xtradb-cluster-8-0-on-my-debian-11-operating-system-causing-a-nodes-mysql-to-fail/29474/2 "2024-04-01T15:58:11Z")
> [@poplar.harry](#): > > 2024-03-14T11:10:01.975264Z 13311 [Warning] [MY-013712] [Server] No suitable ‘keyring\_component\_metadata\_query’ service implementation found to fulfill the request. This tells me that your InnoDB stuff is encrypted, and since there is no keyring component (ie: plugin) loaded to get the key, the files cannot be decrypted and cannot be read from.