Details
-
Type:
Bug
-
Status: Open
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 10.1.6
-
Fix Version/s: None
-
Component/s: Storage Engine - InnoDB
-
Labels:None
-
Environment:Windows 2008 R2 , Debian sid
Description
Installed 10.1.6 over 10.0.20. upgrade from install failed and mysqld do not load.
C:\Program Files\MariaDB 10.1\bin>"C:\Program Files\MariaDB 10.1\bin\mysqld.exe" "--defaults-file=C:\Program Files\MariaDB 10.0\data\my.ini"
and in the log:
150824 10:33:56 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150824 10:33:56 [Note] InnoDB: The InnoDB memory heap is disabled 150824 10:33:56 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150824 10:33:56 [Note] InnoDB: Memory barrier is not used 150824 10:33:56 [Note] InnoDB: Compressed tables use zlib 1.2.3 150824 10:33:56 [Note] InnoDB: Not using CPU crc32 instructions 150824 10:33:56 [Note] InnoDB: Initializing buffer pool, size = 511.0M 150824 10:33:56 [Note] InnoDB: Completed initialization of buffer pool 150824 10:33:56 [Note] InnoDB: Highest supported file format is Barracuda. 150824 10:33:56 [Note] InnoDB: The log sequence numbers 461142294696 and 461142294696 in ibdata files do not match the log sequence number 461142294706 in the ib_logfiles! 150824 10:33:56 [Note] InnoDB: Database was not shutdown normally! 150824 10:33:56 [Note] InnoDB: Starting crash recovery. 150824 10:33:56 [Note] InnoDB: Reading tablespace information from the .ibd files... 150824 10:34:03 [Note] InnoDB: Restoring possible half-written data pages 150824 10:34:03 [Note] InnoDB: from the doublewrite buffer... 150824 10:34:04 [Note] InnoDB: 128 rollback segment(s) are active. 150824 10:34:04 [Note] InnoDB: Waiting for purge to start 150824 10:34:04 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.24-72.2 started; log sequence number 461142294706 150824 10:34:04 [Note] Plugin 'FEEDBACK' is disabled. 150824 10:34:04 [ERROR] Can't open shared library 'C:\Program Files\MariaDB 10.0\lib\plugin\handlersocket.so.dll' (errno: 0, The specified module could not be found.) 150824 10:34:04 [Warning] Couldn't load plugin named 'handlersocket' with soname 'handlersocket.so'. 150824 10:34:04 [Note] Server socket created on IP: '::'. 150824 10:34:05 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure 150824 10:34:05 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure.... 150824 10:34:05 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure 150824 10:34:05 [Note] Event Scheduler: Loaded 9 events 2015-08-24 10:34:05 e0c InnoDB: Error: There are 1 foreign key(s) pointing to "mysql"."innodb_table_stats", but there must be 0. 2015-08-24 10:34:05 e0c InnoDB: Error: Fetch of persistent statistics requested for table "mysql"."gtid_slave_pos" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead. 150824 10:34:05 [Note] C:\Program Files\MariaDB 10.0\bin\mysqld.exe: ready for connections. Version: '10.0.20-MariaDB' socket: '' port: 3306 mariadb.org binary distribution 2015-08-24 10:34:17 72c InnoDB: Error: There are 1 foreign key(s) pointing to "mysql"."innodb_table_stats", but there must be 0. 2015-08-24 10:34:17 72c InnoDB: Error: Fetch of persistent statistics requested for table "a7"."users" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.... 150824 10:39:12 [Warning] Host name '*.barak.inn.local' could not be resolved: No such host is known. 2015-08-24 10:52:33 1380 InnoDB: Error: There are 1 foreign key(s) pointing to "mysql"."innodb_table_stats", but there must be 0. 2015-08-24 10:52:33 1380 InnoDB: Error: Fetch of persistent statistics requested for table "a7"."flashes" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead. 2015-08-24 10:53:54 1860 [Warning] Couldn't load plugin named 'handlersocket' with soname 'handlersocket.so'. 2015-08-24 10:53:54 1860 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2015-08-24 10:53:54 1860 [Note] InnoDB: The InnoDB memory heap is disabled 2015-08-24 10:53:54 1860 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2015-08-24 10:53:54 1860 [Note] InnoDB: Memory barrier is not used 2015-08-24 10:53:54 1860 [Note] InnoDB: Compressed tables use zlib 1.2.3 2015-08-24 10:53:54 1860 [Note] InnoDB: Not using CPU crc32 instructions 2015-08-24 10:53:54 1860 [Note] InnoDB: Initializing buffer pool, size = 511.0M 2015-08-24 10:53:54 1860 [Note] InnoDB: Completed initialization of buffer pool 2015-08-24 10:53:54 1860 [Note] InnoDB: Highest supported file format is Barracuda. 2015-08-24 10:53:54 1860 [Note] InnoDB: The log sequence numbers 461142294696 and 461142294696 in ibdata files do not match the log sequence number 461142317591 in the ib_logfiles! 2015-08-24 10:53:54 1860 [Note] InnoDB: Database was not shutdown normally! 2015-08-24 10:53:54 1860 [Note] InnoDB: Starting crash recovery. 2015-08-24 10:53:54 1860 [Note] InnoDB: Reading tablespace information from the .ibd files... 2015-08-24 10:53:55 1860 [Note] InnoDB: Restoring possible half-written data pages 2015-08-24 10:53:55 1860 [Note] InnoDB: from the doublewrite buffer... 2015-08-24 10:53:56 1860 [Note] InnoDB: 128 rollback segment(s) are active. 2015-08-24 10:53:56 1860 [Note] InnoDB: Waiting for purge to start 2015-08-24 10:53:56 1860 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.24-72.2 started; log sequence number 461142317591 2015-08-24 10:53:56 12e0 InnoDB: Assertion failure in thread 4832 in file btr0cur.cc line 5255 InnoDB: Failing assertion: rb_ctx != RB_NONE 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.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 150824 10:53:56 [ERROR] mysqld got exception 0x80000003 ; 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. To report this bug, see http://kb.askmonty.org/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.1.6-MariaDB key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=0 max_threads=1001 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2311976 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x0 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... 2015-08-24 10:53:56 4708 [Note] InnoDB: not started 2015-08-24 10:53:56 1860 [Note] Plugin 'FEEDBACK' is disabled. 2015-08-24 10:53:56 1860 [Note] Recovering after a crash using tc.log 2015-08-24 10:53:56 1860 [Note] Starting crash recovery... 2015-08-24 10:53:56 1860 [Note] Crash recovery finished. 2015-08-24 10:53:56 1860 [Note] Server socket created on IP: '::'. 2015-08-24 10:53:56 1860 [Note] Event Scheduler: Loaded 9 events 2015-08-24 10:53:56 e0c InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch). 2015-08-24 10:53:56 e0c InnoDB: Error: Fetch of persistent statistics requested for table "mysql"."gtid_slave_pos" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead. 2015-08-24 10:53:56 1860 [Note] C:\Program Files\MariaDB 10.1\bin\mysqld.exe: ready for connections. Version: '10.1.6-MariaDB' socket: '' port: 3306 mariadb.org binary distribution mysqld.exe!my_sigabrt_handler()[my_thr_init.c:475] mysqld.exe!raise()[winsig.c:593] mysqld.exe!abort()[abort.c:81] mysqld.exe!btr_free_externally_stored_field()[btr0cur.cc:5256] mysqld.exe!row_purge_upd_exist_or_extern_func()[row0purge.cc:698] mysqld.exe!row_purge_record_func()[row0purge.cc:853] mysqld.exe!row_purge()[row0purge.cc:899] mysqld.exe!row_purge_step()[row0purge.cc:978] mysqld.exe!que_thr_step()[que0que.cc:1089] mysqld.exe!que_run_threads_low()[que0que.cc:1154] mysqld.exe!que_run_threads()[que0que.cc:1194] mysqld.exe!trx_purge()[trx0purge.cc:1254] mysqld.exe!srv_do_purge()[srv0srv.cc:3429] mysqld.exe!srv_purge_coordinator_thread()[srv0srv.cc:3613] kernel32.dll!BaseThreadInitThunk() ntdll.dll!RtlUserThreadStart() 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.
when I am running 10.0 on the same data folder, all is OK.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
My.ini attached
dataset - 21GB compressed one database, all ~ 30GB, with innodb_file_per_table if it relevant (I can upload some of the tables, but not all of them, maybe will help you).
there is no changes opun upgrade (I was tried to use INNODB Recover to make it work, without help).
Thanks, yes, please upload whatever you can. The partial data is likely not to work, but it's worth trying anyway. Besides, it's possible the problem is in system tables which the server complains about in your error log (mysql.innodb_table_stats and such), which you will hopefully be able to provide.
1. please send me an email (m@inn.co.il). I will upload an non-sensitive information so you can check.
2. tables `x has the wrong structure` - there is a tables in 10.0 format (the old one), so I just need to run mysql_upgrade to make it works.
I can upload these table, as these not store sensitive data.
please send me an email (m@inn.co.il). I will upload an non-sensitive information so you can check.
What kind of email? If you mean credentials for FTP (ftp.askmonty.org/private), anyone can upload there, but only MariaDB developers can read from there.
tables `x has the wrong structure` - there is a tables in 10.0 format (the old one), so I just need to run mysql_upgrade to make it works.
"has wrong structure" error messages are of course indeed just that.
The problem is, you also had "There are 1 foreign key(s) pointing to "mysql"."innodb_table_stats", but there must be 0." messages which are far less normal – and you had them even before 10.0=>10.1 upgrade. Same for messages about performance_schema tables.
1. yes, FTP cred.
Uploaded some frm/ibd files - tables you requested and some random tables without sensitive information. `performance_schema` folder is empty.
2. I was tried to upgrade via wizard and mysqld was crashed in the wizard. maybe some tables was updated before the crash.
Elena Stepanova commented on MDEV-8672:
---------------------------------------
please send me an email (m@inn.co.il). I will upload an non-sensitive information so you can check.
What kind of email? If you mean credentials for FTP (ftp.askmonty.org/private), anyone can upload there, but only MariaDB developers can read from there.
tables `x has the wrong structure` - there is a tables in 10.0 format (the old one), so I just need to run mysql_upgrade to make it works.
"has wrong structure" error messages are of course indeed just that.
The problem is, you also had "There are 1 foreign key(s) pointing to "mysql"."innodb_table_stats", but there must be 0." messages which are far less normal – and you had them even before 10.0=>10.1 upgrade. Same for messages about performance_schema tables.
–
This message was sent by Atlassian JIRA
(v7.0.0-OD-02-247#70102)
Thanks. One more thing, in the 'Environment' field you put both Windows 2008 R2 and Debian sid. Does it mean you actually have two instances which have the same problem? Can you provide the error log from the Debian instance as well?
I was tried a month ago to do the same thing on a clone of our production server, and upgrading to 10.1.5 (as I remember), and see the same problem (won't load, things like this).
I do not have the logs from the Debian machine, as it was deleted...
Moshe L,
Is it a test instance or production, and how big is the data set? Would you be able to upload the datadir to our ftp? (ftp.askmonty.org/private, only MariaDB developers will have access to it).
Please also attach your cnf file(s) and mention which, if any, changes you've made upon upgrade.
Thanks.