ユーザー登録で「300円クーポン」プレゼント!まずは無料登録から!
募集をシェアしてメンターを探そう
シェア
エンジニア MySQL Linux全般 CentOS

MySQLのレプリケーションエラーや、起動失敗等クリティカルな状況のサポート

2020年11月4日
予算
〜 10,000円
提案数
1人が提案中

MySQLのレプリケーションエラーや、起動失敗等クリティカルな状況をサポートいただける方を探しています。下記、エラーの一例になります。

〇レプリケーションエラー(未解決)
Could not execute Update_rows event on table テーブル名; Can't find record in 'テーブル名', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log ***-bin.000001

〇起動失敗(復旧はできたが防止策を模索中)
/var/log/mysqld.log

2020-10-24T08:45:07.765585Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.13) starting as process 129650
2020-10-24T08:45:08.721941Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: row0umod.cc:149:!dummy_big_rec thread 139968230074112
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:45:08 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
...以下略

メンティーに提案してみましょう
募集をシェアしてメンターを探そう
シェア