Error_code: 1032; Handler Error HA_ERR_KEY_NOT_FOUND

Home » CentOS » Error_code: 1032; Handler Error HA_ERR_KEY_NOT_FOUND
CentOS No Comments

Hi,

I am running MySQL DB server 8.0.31
(mysql-community-server-8.0.31-1.el7.x86_64) on the CentOS Linux release
7.9.2009 (Core) operating system and have enabled replication between Master and Standby.

I am currently encountering the error Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND as found in mysqld.log file on Standby server.

cat mysqld.log file
##################################################################################################################################
2023-06-12T07:34:49.698300Z 0 [System] [MY-010116] [Server]
/usr/sbin/mysqld (mysqld 8.0.31) starting as process 9942
2023-06-12T07:34:49.716114Z 1 [System] [MY-013576] [InnoDB] InnoDB
initialization has started.
2023-06-12T07:34:50.203380Z 1 [System] [MY-013577] [InnoDB] InnoDB
initialization has ended.
2023-06-12T07:34:50.560267Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2023-06-12T07:34:50.560375Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2023-06-12T07:34:50.565553Z 0 [Warning] [MY-011810] [Server] Insecure configuration for –pid-file: Location ‘/data’ in the path is accessible to all OS users. Consider choosing a different directory.
2023-06-12T07:34:50.592935Z 0 [Warning] [MY-010604] [Repl] Neither
–relay-log nor –relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use
‘–relay-log