Monday, May 6, 2024

BITNAMI MYSQL INSTANCE INNODB CRASH

 Error:


2024-05-05T19:19:41.260401Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld (mysqld 8.0.23) starting as process 28016

2024-05-05T19:19:41.262950Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.

2024-05-05T19:19:41.262960Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8_general_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.

2024-05-05T19:19:41.274571Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.

2024-05-05T19:19:41.452755Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:10815:initial_fsize == (file->size * phy_page_size) thread 140475468232448

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.

19:19:41 UTC - mysqld got signal 6 ;

Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.

Thread pointer: 0x55a7d6822eb0

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

stack_bottom = 7fc2fe622ca0 thread_stack 0x46000

/opt/bitnami/mysql/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2e) [0x55a7d225115e]

/opt/bitnami/mysql/bin/mysqld(handle_fatal_signal+0x31b) [0x55a7d13036eb]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730) [0x7fc30abf4730]

/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b) [0x7fc30a2dc8eb]

/lib/x86_64-linux-gnu/libc.so.6(abort+0x121) [0x7fc30a2c7535]

/opt/bitnami/mysql/bin/mysqld(+0xebeff8) [0x55a7d1085ff8]

/opt/bitnami/mysql/bin/mysqld(fil_tablespace_redo_extend(unsigned char*, unsigned char const*, page_id_t const&, unsigned long, bool)+0x532) [0x55a7d2662632]

/opt/bitnami/mysql/bin/mysqld(+0x2217e34) [0x55a7d23dee34]

/opt/bitnami/mysql/bin/mysqld(+0x2219969) [0x55a7d23e0969]

/opt/bitnami/mysql/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0x2450) [0x55a7d23e5a00]

/opt/bitnami/mysql/bin/mysqld(srv_start(bool)+0x1d87) [0x55a7d24cf907]

/opt/bitnami/mysql/bin/mysqld(+0x2174476) [0x55a7d233b476]

/opt/bitnami/mysql/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0x90) [0x55a7d2027770]

/opt/bitnami/mysql/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x18b) [0x55a7d221b74b]

/opt/bitnami/mysql/bin/mysqld(+0x11ed208) [0x55a7d13b4208]

/opt/bitnami/mysql/bin/mysqld(+0x25af2b4) [0x55a7d27762b4]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3) [0x7fc30abe9fa3]

/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7fc30a39e06f]


Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0): Connection ID (thread ID): 1

Status: NOT_KILLED


The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

information that should help you find out what is causing the crash.


Solution:

1)Stop all bitnami process.

2)edit "/opt/bitnami/mysql/conf/my.cnf" and add "innodb_force_recovery=6" in [mysqld] block.

3)Comment "innodb_tempdir=/bitnami/mysql/data" and save the file.

4)Start MySQL instance [/opt/bitnami/ctlscript.sh start MySQL] and check the status [/opt/bitnami/ctlscript.sh status]. If MySQL instance running, then start all other process.

No comments:

Post a Comment