Description:
dear ,
I have ubunt 16.04 running mysql. Mysql stopped working and only startup in "innodb_force_recovery = 1" . In this mode , I can login and get some dumps of databases but when I comment out "#innodb_force_recovery = 1" it does not startup.
below you can find error.log content:
"InnoDB: End of page dump
2019-07-04T18:38:43.972231Z 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 3555636731, calculated checksums for field1: crc32 3555636731/1212977647, innodb 3515992906, none 3735928559, stored checksum in field2 3703805223, calculated checksums for field2: crc32 3555636731/1212977647, innodb 900607883, none 3735928559, page LSN 6 3412678931, low 4 bytes of LSN at page end 3412617177, page number (if stored to page already) 347, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
2019-07-04T18:38:43.972239Z 0 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-07-04T18:38:43.972241Z 0 [ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page in the system tablespace. Or, there was a failure in tagging the tablespace as corrupt.
2019-07-04 21:38:43 0x7fac48936740 InnoDB: Assertion failure in thread 140377928722240 in file ut0ut.cc line 942
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/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
18:38:43 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.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76388 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xe9510b]
/usr/sbin/mysqld(handle_fatal_signal+0x489)[0x78ad29]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fac4749a390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7fac46853428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fac4685502a]
/usr/sbin/mysqld[0x7605dc]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x145)[0x1072825]
/usr/sbin/mysqld(_Z20buf_page_io_completeP10buf_page_tb+0x2e6)[0x10b0d16]
/usr/sbin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0x4e2)[0x10e2d42]
/usr/sbin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4f1)[0x10af411]
/usr/sbin/mysqld(_Z19trx_undo_lists_initP10trx_rseg_t+0x3b2)[0x1065e92]
/usr/sbin/mysqld[0x104bc46]
/usr/sbin/mysqld[0x104e8db]
/usr/sbin/mysqld(_Z24trx_sys_init_at_db_startv+0x1734)[0x1055584]
/usr/sbin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x4dbd)[0x101b41d]
/usr/sbin/mysqld[0xeda258]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7d86c1]
/usr/sbin/mysqld[0xc729e5]
/usr/sbin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x318)[0xc75e08]
/usr/sbin/mysqld[0x78312f]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0xa49)[0x784b19]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fac4683e830]
/usr/sbin/mysqld(_start+0x29)[0x77afb9]
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."
any suggestion ?
How to repeat:
when "#innodb_force_recovery = 1" is commented out
ozkan@hanubuntu:~$ systemctl status mysql.service
● mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: activating (start-post) (Result: exit-code) since Prş 2019-07-04 21:52:15 +03; 11s ago
Process: 5372 ExecStart=/usr/sbin/mysqld (code=exited, status=2)
Process: 5364 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
Main PID: 5372 (code=exited, status=2); : 5373 (mysql-systemd-s)
CGroup: /system.slice/mysql.service
└─control
├─5373 /bin/bash /usr/share/mysql/mysql-systemd-start post
└─5410 sleep 1
Tem 04 21:52:15 hanubuntu systemd[1]: Starting MySQL Community Server...
Tem 04 21:52:16 hanubuntu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
