MySQL service not getting started

Keywords: WordPress - AWS - Technical issue - Other
bnsupport ID: 26ad460c-7734-0004-3d28-c4bdb3bed715
Description:
My bundle id is 26ad460c-7734-0004-3d28-c4bdb3bed715.
Please assist as it’s a live website

Hi @skpandey0002,

If you take a look at the MySQL’s log file

https://docs.bitnami.com/aws/apps/wordpress/troubleshooting/debug-errors-mysql/

you can see that MySQL crashed and can be started

2021-02-22T12:55:02.911794Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 8.0.23) starting as process 9298
2021-02-22T12:55:02.923531Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2021-02-22T12:55:03.675221Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:10815:initial_fsize == (file->size * phy_page_size) thread 140202128111360
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.
12:55:03 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7749d30
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 = 7f835a0aeca0 thread_stack 0x46000
/opt/bitnami/mysql/bin/mysqld.bin(my_print_stacktrace(unsigned char const*, unsigned long)+0x2e) [0x2066f1e]
/opt/bitnami/mysql/bin/mysqld.bin(handle_fatal_signal+0x323) [0x1032cc3]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730) [0x7f836724d730]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b) [0x7f8365f647bb]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x121) [0x7f8365f4f535]
/opt/bitnami/mysql/bin/mysqld.bin() [0xdae42c]
/opt/bitnami/mysql/bin/mysqld.bin(fil_tablespace_redo_extend(unsigned char*, unsigned char const*, page_id_t const&, unsigned long, bool)+0x50b) [0x24828db]
/opt/bitnami/mysql/bin/mysqld.bin() [0x21f8614]
/opt/bitnami/mysql/bin/mysqld.bin() [0x21fa119]
/opt/bitnami/mysql/bin/mysqld.bin(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0x2106) [0x21fee36]
/opt/bitnami/mysql/bin/mysqld.bin(srv_start(bool)+0x1cd1) [0x22e84c1]
/opt/bitnami/mysql/bin/mysqld.bin() [0x21539c7]
/opt/bitnami/mysql/bin/mysqld.bin(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0x81) [0x1d66d31]
/opt/bitnami/mysql/bin/mysqld.bin(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x18b) [0x203181b]
/opt/bitnami/mysql/bin/mysqld.bin() [0x10e3cb8]
/opt/bitnami/mysql/bin/mysqld.bin() [0x25973dc]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3) [0x7f8367242fa3]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f83660264cf]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED

Please follow the steps below to recover the database status:

You can find more information about the InnoDB Recovery in the official website: https://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html

We have updated the page at https://docs.bitnami.com/aws/apps/wordpress/administration/recover-database/ with additional information on this topic.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.