0

Originaly it runned on mysql Server version: 5.6.28-0ubuntu0.15.04.1-log (Ubuntu) now it runs on Server version: 5.7.27-0ubuntu0.18.04.1-log (Ubuntu)

I can get the structure by generating a .sql file with mysqlfrm --diagnostic and then importing it. When I put the ibdata1 on /var/lib/mysql, I can't start the server. At innodb_force_recovery = 6 I get messages

2019-08-04T03:49:29.672824Z 0 [ERROR] InnoDB: Cannot create sys_virtual system tables; running in read-only mode. 2019-08-04T03:49:29.672866Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2019-08-04T03:49:29.980728Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2019-08-04T03:49:29.980778Z 0 [ERROR] Plugin 'InnoDB' init function returned error. 2019-08-04T03:49:29.980794Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2019-08-04T03:49:29.980811Z 0 [ERROR] Failed to initialize builtin plugins. 2019-08-04T03:49:29.980823Z 0 [ERROR] Aborting

At level 5 and 4 I also get: 2019-08-04T03:52:40.783609Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=657] log sequence number 228620392817 is in the future! Current system log sequence number 2696317. 2019-08-04T03:52:40.783629Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to ...for information about forcing recovery.

for different sequence numbers and page numbers.

At level 3 I get: 019-08-04T04:37:09.277070Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for zemec/tbl_faturasclientes. Please refer to ... for how to resolve the issue. 2019-08-04T04:37:09.277082Z 0 [Warning] InnoDB: Ignoring tablespace zemec/tbl_faturasclientes because it could not be opened. 2019-08-04T04:37:09.277110Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-08-04T04:37:09.277122Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-08-04T04:37:09.277132Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create

One strategy could be create fake directories for the missing databases(like zemec) and tables like tbl_faturasclientes. Without this OS error, it could at least start, but would I be able to recover the data ?

At level 2 I get:

2019-08-04T04:43:56.961535Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for zemec/tbl_transportadoras. Please refer to ... for how to resolve the issue. 2019-08-04T04:43:56.961554Z 0 [Warning] InnoDB: Ignoring tablespace zemec/tbl_transportadoras because it could not be opened. 2019-08-04T04:43:56.961596Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2019-08-04T04:43:56.961612Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2019-08-04T04:43:56.961628Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.

and

2019-08-04T04:43:56.989007Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2019-08-04T04:43:56.989122Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2019-08-04T04:43:57.308139Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2019-08-04T04:43:57.309553Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. 2019-08-04T04:43:57.309586Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active. 2019-08-04T04:43:57.309866Z 0 [Note] InnoDB: Creating sys_virtual system tables. 2019-08-04T04:43:57.310009Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=9] log sequence number 228620276756 is in the future! Current system log sequence number 2710777. 2019-08-04T04:43:57.310024Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to .. for information about forcing recovery. 2019-08-04T04:43:57.310242Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=4085] log sequence number 105671479570 is in the future! Current system log sequence number 2711477. 2019-08-04T04:43:57.310256Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to ... for information about forcing recovery. 2019-08-04T04:43:57.333757Z 0 [Note] InnoDB: sys_virtual table created 2019-08-04T04:43:57.333977Z 0 [Note] InnoDB: 5.7.27 started; log sequence number 2710592 2019-08-04T04:43:57.333991Z 0 [Note] InnoDB: !!! innodb_force_recovery is set to 2 !!! 2019-08-04T04:43:57.334100Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2019-08-04T04:43:57.334317Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=243] log sequence number 228632004269 is in the future! Current system log sequence number 2712962. 2019-08-04T04:43:57.334334Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to ... for information about forcing recovery. 2019-08-04T04:43:57.334452Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=322] log sequence number 228347623980 is in the future! Current system log sequence number 2712962. 2019-08-04T04:43:57.334465Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to for information about forcing recovery. 2019-08-04T04:43:57.334496Z 0 [Note] Plugin 'FEDERATED' is disabled. 2019-08-04T04:43:57.334618Z 0 [ERROR] [FATAL] InnoDB: Tablespace id is 2 in the data dictionary but in file ./mysql/innodb_index_stats.ibd it is 14! 2019-08-04 01:43:57 0x7fb0bb7fe700 InnoDB: Assertion failure in thread 140397036693248 in file ut0ut.cc line 910 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: InnoDB: about forcing recovery. 04:43:57 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=8388608 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 = 68196 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 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xec00eb] /usr/sbin/mysqld(handle_fatal_signal+0x48b)[0x79178b] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7fb0f0977890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fb0efc73e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fb0efc75801] /usr/sbin/mysqld[0x767f02] /usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x66)[0x1097e16] /usr/sbin/mysqld[0x11458d8] /usr/sbin/mysqld[0x11460ad] /usr/sbin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x322)[0x1150b92] /usr/sbin/mysqld[0x1102370] 2019-08-04T04:43:57.340733Z 0 [Warning] InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to .. for how to resolve the issue. mysqld: Table 'mysql.plugin' doesn't exist 2019-08-04T04:43:57.340852Z 0 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. /usr/sbin/mysqld(_Z24buf_read_page_backgroundRK9page_id_tRK11page_size_tb+0x35)[0x1102a75] /usr/sbin/mysqld[0x10e67ad] /usr/sbin/mysqld(buf_dump_thread+0x15d)[0x10e6e7d] /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x7fb0f096c6db] /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fb0efd5688f] The manual page at ... contains information that should help you find out what is causing the crash.

Would running mysql upgrade as asked be a good idea ?

Finally, at level 1, the only difference from 2 is: 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): 0 Status: NOT_KILLED

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.