This is for your collection of possible data corruption issues; maybe looking at them together will give a new perspective (or maybe they are completely unrelated).
Hi,
I tried to reproduce with creating mentioned table using 10.0.6, upgraded to 10.0.7 without any problems and then upgrade to 10.0.8 and no problems. What kind of device you have tables stored and can you explain what commands you did to see a crash ?
R: Jan
Hi Jan,
The device is a classical harddrive on a ext4 FS.
I haven't done anything specific other than executing the debian "apt-get upgrade" command.
Note there are several consecutive "[Note] InnoDB: Starting shutdown..." in the log during the standard shutdown, with different log sequence number between
140211 00:00:25 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
and
140211 00:01:23 mysqld_safe Starting mysqld daemon with databases from /home/mysql/data
which seem to be specific to the DB upgrade; when doing a classical /etc/init.d/mysql restart, I do not see this kind of behaviour :
140224 12:45:01 [Note] /usr/sbin/mysqld: Normal shutdown
140224 12:45:01 [Note] Event Scheduler: Purging the queue. 0 events
140224 12:45:03 [Note] InnoDB: FTS optimize thread exiting.
140224 12:45:03 [Note] InnoDB: Starting shutdown...
140224 12:45:06 [Note] InnoDB: Shutdown completed; log sequence number 3396586217139
140224 12:45:06 [Note] /usr/sbin/mysqld: Shutdown complete
140224 12:45:06 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140224 12:45:07 mysqld_safe Starting mysqld daemon with databases from /home/mysql/data
140224 12:45:07 [Note] InnoDB: The InnoDB memory heap is disabled
140224 12:45:07 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
140224 12:45:07 [Note] InnoDB: Compressed tables use zlib 1.2.7
140224 12:45:07 [Note] InnoDB: Using Linux native AIO
140224 12:45:07 [Note] InnoDB: Using CPU crc32 instructions
140224 12:45:07 [Note] InnoDB: Initializing buffer pool, size = 4.0G
140224 12:45:07 [Note] InnoDB: Completed initialization of buffer pool
140224 12:45:07 [Note] InnoDB: Highest supported file format is Barracuda.
140224 12:45:10 [Note] InnoDB: 128 rollback segment(s) are active.
140224 12:45:10 [Note] InnoDB: Waiting for purge to start
140224 12:45:10 [Note] InnoDB: 5.6.14 started; log sequence number 3396586217139
140224 12:45:10 [Note] Plugin 'FEEDBACK' is disabled.
140224 12:45:10 [ERROR] Function 'TokuDB_fractal_tree_block_map' already exists
140224 12:45:10 [Warning] Couldn't load plugin named 'TokuDB_fractal_tree_block_map' with soname 'ha_tokudb.so'.
140224 12:45:10 [ERROR] Function 'TokuDB_fractal_tree_info' already exists
140224 12:45:10 [Warning] Couldn't load plugin named 'TokuDB_fractal_tree_info' with soname 'ha_tokudb.so'.
140224 12:45:10 [ERROR] Function 'TokuDB_file_map' already exists
140224 12:45:10 [Warning] Couldn't load plugin named 'TokuDB_file_map' with soname 'ha_tokudb.so'.
140224 12:45:10 [ERROR] Can't find symbol 'TokuDB_user_data_exact' in library
140224 12:45:10 [Warning] Couldn't load plugin named 'TokuDB_user_data_exact' with soname 'ha_tokudb.so'.
140224 12:45:10 [ERROR] Can't find symbol 'TokuDB_user_data' in library
140224 12:45:10 [Warning] Couldn't load plugin named 'TokuDB_user_data' with soname 'ha_tokudb.so'.
140224 12:45:10 [Note] Server socket created on IP: '127.0.0.1'.
140224 12:45:10 [Warning] 'user' entry 'prestashop@@ocalhost' ignored in --skip-name-resolve mode.
140224 12:45:10 [Warning] 'db' entry 'prestashop prestashop@@ocalhost' ignored in --skip-name-resolve mode.
140224 12:45:10 [Note] Event Scheduler: Loaded 0 events
140224 12:45:10 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.8-MariaDB-1~wheezy' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
Thanks,
Jocelyn
Just got a new crash not related to any upgrade, and MariaDB seems to be completely unusable this time, I'm not able to restart mysql anymore 
FYI, this crash occured during a classic backup. I'll definitly switch back to 5.5 after regenerating the DB from a backup.
140307 1:38:37 [ERROR] InnoDB: File ./a_build/ip2c.ibd: 'Linux aio' returned OS error 0. Cannot continue operation
140307 01:38:39 mysqld_safe Number of processes running now: 0
140307 01:38:39 mysqld_safe mysqld restarted
140307 1:38:40 [Note] InnoDB: The InnoDB memory heap is disabled
140307 1:38:40 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
140307 1:38:40 [Note] InnoDB: Compressed tables use zlib 1.2.7
140307 1:38:40 [Note] InnoDB: Using Linux native AIO
140307 1:38:40 [Note] InnoDB: Using CPU crc32 instructions
140307 1:38:40 [Note] InnoDB: Initializing buffer pool, size = 4.0G
140307 1:38:40 [Note] InnoDB: Completed initialization of buffer pool
140307 1:38:40 [Note] InnoDB: Highest supported file format is Barracuda.
140307 1:38:40 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3397107988944
140307 1:38:40 [Note] InnoDB: Database was not shutdown normally!
140307 1:38:40 [Note] InnoDB: Starting crash recovery.
140307 1:38:40 [Note] InnoDB: Reading tablespace information from the .ibd files...
140307 1:39:00 [Note] InnoDB: Restoring possible half-written data pages
140307 1:39:00 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 3397107989420
InnoDB: Last MySQL binlog file position 0 21857709, file name /home/mysql/log/mysql-bin.000011
140307 1:39:01 [Note] InnoDB: 128 rollback segment(s) are active.
140307 1:39:01 [Note] InnoDB: Waiting for purge to start
140307 1:39:01 [Note] InnoDB: 5.6.14 started; log sequence number 3397107989420
140307 1:39:01 [Note] Plugin 'FEEDBACK' is disabled.
140307 1:39:01 [ERROR] Function 'TokuDB_fractal_tree_block_map' already exists
140307 1:39:01 [Warning] Couldn't load plugin named 'TokuDB_fractal_tree_block_map' with soname 'ha_tokudb.so'.
140307 1:39:01 [ERROR] Function 'TokuDB_fractal_tree_info' already exists
140307 1:39:01 [Warning] Couldn't load plugin named 'TokuDB_fractal_tree_info' with soname 'ha_tokudb.so'.
140307 1:39:01 [ERROR] Function 'TokuDB_file_map' already exists
140307 1:39:01 [Warning] Couldn't load plugin named 'TokuDB_file_map' with soname 'ha_tokudb.so'.
140307 1:39:01 [ERROR] Can't find symbol 'TokuDB_user_data_exact' in library
140307 1:39:01 [Warning] Couldn't load plugin named 'TokuDB_user_data_exact' with soname 'ha_tokudb.so'.
140307 1:39:01 [ERROR] Can't find symbol 'TokuDB_user_data' in library
140307 1:39:01 [Warning] Couldn't load plugin named 'TokuDB_user_data' with soname 'ha_tokudb.so'.
InnoDB: Error: trying to access page number 42 in space 326272,
InnoDB: space name jiradb/jiraissue,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
2014-03-07 01:39:01 7eff2dbfc700 InnoDB: Assertion failure in thread 139634449303296 in file fil0fil.cc line 5445
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.
140307 1:39:01 [ERROR] 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.
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.0.8-MariaDB-1~wheezy
key_buffer_size=134217728
read_buffer_size=4194304
max_used_connections=0
max_threads=402
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2609233 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...
stack_bottom = 0x0 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f008555e08b]
/usr/sbin/mysqld(handle_fatal_signal+0x422)[0x7f0085111902]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf030)[0x7f0084783030]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f0082ddf475]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x180)[0x7f0082de26f0]
/usr/sbin/mysqld(+0x93a025)[0x7f00854ec025]
/usr/sbin/mysqld(+0x8ff6d6)[0x7f00854b16d6]
/usr/sbin/mysqld(+0x900024)[0x7f00854b2024]
/usr/sbin/mysqld(+0x8e7899)[0x7f0085499899]
/usr/sbin/mysqld(+0x8cbc3b)[0x7f008547dc3b]
/usr/sbin/mysqld(+0x875438)[0x7f0085427438]
/usr/sbin/mysqld(+0x8727f3)[0x7f00854247f3]
/usr/sbin/mysqld(+0x8cc16a)[0x7f008547e16a]
/usr/sbin/mysqld(+0x8757bd)[0x7f00854277bd]
/usr/sbin/mysqld(+0x8729ae)[0x7f00854249ae]
/usr/sbin/mysqld(+0x8734da)[0x7f00854254da]
/usr/sbin/mysqld(+0x873a82)[0x7f0085425a82]
/usr/sbin/mysqld(+0x840a7b)[0x7f00853f2a7b]
/usr/sbin/mysqld(+0x899111)[0x7f008544b111]
/usr/sbin/mysqld(+0x88bb9d)[0x7f008543db9d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7f008477ab50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f0082e890ed]
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.
140307 01:39:02 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Hi,
What kind of storage you have? Is it SSD ? You could try by setting innodb_use_fallocate=0 and recreate db if that helps, but your database is now broken.
R: Jan
Hi,
It's a good old classical harddrive (ATA TOSHIBA DT01ACA2), and no smart errors reported (no read error, no pending sector, ...).
I'll try to change innodb_use_fallocate=0. FYI, I'm able to start MariaDB with innodb_force_recovery = 2.
I'll see if dropping the DB "a_build" changes anything
BTW, FYI the only thing I've done yesterday is creating/dropping a few new databases, tables and users.
It seems I can work with my DB (no more crash), but I've InnoDB error in the log I don't like at all
I've dropped the table jiradb/jiraissue mentionned in the first error in innodb_force_recovery mode.
Then I've deleted the innodb log file, and restart mariadb, and reimport the table :
140307 8:54:01 [Note] /usr/sbin/mysqld: Normal shutdown
140307 8:54:01 [Note] Event Scheduler: Purging the queue. 0 events
140307 8:54:02 [Note] InnoDB: FTS optimize thread exiting.
140307 8:54:02 [Note] InnoDB: Starting shutdown...
140307 8:54:04 [Note] InnoDB: Shutdown completed; log sequence number 3396587590267
140307 8:54:04 [Note] /usr/sbin/mysqld: Shutdown complete
140307 08:54:04 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140307 08:54:26 mysqld_safe Starting mysqld daemon with databases from /home/mysql/data
140307 8:54:26 [Note] InnoDB: The InnoDB memory heap is disabled
140307 8:54:26 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
140307 8:54:26 [Note] InnoDB: Compressed tables use zlib 1.2.7
140307 8:54:26 [Note] InnoDB: Using Linux native AIO
140307 8:54:26 [Note] InnoDB: Using CPU crc32 instructions
140307 8:54:26 [Note] InnoDB: Initializing buffer pool, size = 4.0G
140307 8:54:26 [Note] InnoDB: Completed initialization of buffer pool
140307 8:54:26 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
140307 8:54:26 [Note] InnoDB: Setting log file ./ib_logfile1 size to 128 MB
140307 8:54:26 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
140307 8:54:26 [Warning] InnoDB: New log files created, LSN=3396587590267
140307 8:54:26 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-07 08:54:26 7fac8afc8780 InnoDB: Error: page 7 log sequence number 3397094069371
InnoDB: is in the future! Current system log sequence number 3396587590668.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2014-03-07 08:54:26 7fac8afc8780 InnoDB: Error: page 11 log sequence number 3397093899144
InnoDB: is in the future! Current system log sequence number 3396587590668.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2014-03-07 08:54:26 7fac8afc8780 InnoDB: Error: page 32795 log sequence number 3397107877727
InnoDB: is in the future! Current system log sequence number 3396587590668.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
Do you think I've no other solution than recreating all the tables / DB from the backup ?
Thanks and regards,
Jocelyn
After purging the datas, and especially the innodb_table_stats & innodb_index_stats in the mysql database, and trying to reimport the schema with empty datas, I've just figured out than one (and only one) of the table, the one involved in the first crash needs infos from those tables (I forgot to recreate them) :
2014-03-07 09:35:02 7f442677f700 InnoDB: Error: Fetch of persistent statistics requested for table "MQA"."errors" 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.
The only thing I've done so far is recreating the schema of all my tables, without any datas.
I'll of course recreate properly the innodb_table_stats & innodb_index_stats, but I want to mention it since this feature is perhaps linked to my original crash ?
Do you know why this table explicitly needs statistics, even without any datas in it ?
The structure of the table :
CREATE TABLE `errors` (
`id_error` int(11) unsigned NOT NULL AUTO_INCREMENT,
`type` varchar(20) NOT NULL DEFAULT '',
`priority` smallint(5) unsigned NOT NULL DEFAULT '0',
`message` text NOT NULL,
`file` varchar(200) NOT NULL DEFAULT '',
`line` smallint(5) unsigned NOT NULL DEFAULT '0',
`url` varchar(200) NOT NULL DEFAULT '',
`referer` varchar(200) NOT NULL DEFAULT '',
`id_user` mediumint(8) unsigned NOT NULL DEFAULT '0',
`server_web` varchar(100) NOT NULL DEFAULT '',
`server_sql` varchar(100) NOT NULL DEFAULT '',
`date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`count` smallint(5) unsigned NOT NULL DEFAULT '1',
`trace` text NOT NULL,
`md5_message` varchar(32) NOT NULL DEFAULT '',
`id_license_domain` int(10) unsigned NOT NULL DEFAULT '0',
`id_license` int(10) unsigned NOT NULL DEFAULT '0',
`extra` varchar(50) NOT NULL DEFAULT '',
PRIMARY KEY (`id_error`),
UNIQUE KEY `error` (`type`,`priority`,`md5_message`,`file`,`line`,`date`,`id_license_domain`),
KEY `date` (`date`),
KEY `md5_message` (`md5_message`,`date`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
Extract of the log :
140307 09:31:23 mysqld_safe Starting mysqld daemon with databases from /home/mysql/data
140307 9:31:23 [Note] InnoDB: The InnoDB memory heap is disabled
140307 9:31:23 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
140307 9:31:23 [Note] InnoDB: Compressed tables use zlib 1.2.7
140307 9:31:23 [Note] InnoDB: Using Linux native AIO
140307 9:31:23 [Note] InnoDB: Using CPU crc32 instructions
140307 9:31:23 [Note] InnoDB: Initializing buffer pool, size = 4.0G
140307 9:31:23 [Note] InnoDB: Completed initialization of buffer pool
140307 9:31:23 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
140307 9:31:23 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
140307 9:31:23 [Note] InnoDB: Database physically writes the file full: wait...
140307 9:31:23 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
InnoDB: Progress in MB: 100
140307 9:31:24 [Note] InnoDB: Setting log file ./ib_logfile1 size to 128 MB
InnoDB: Progress in MB: 100
140307 9:31:26 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
140307 9:31:26 [Warning] InnoDB: New log files created, LSN=45781
140307 9:31:26 [Note] InnoDB: Doublewrite buffer not found: creating new
140307 9:31:26 [Note] InnoDB: Doublewrite buffer created
140307 9:31:26 [Note] InnoDB: 128 rollback segment(s) are active.
140307 9:31:26 [Warning] InnoDB: Creating foreign key constraint system tables.
140307 9:31:26 [Note] InnoDB: Foreign key constraint system tables created
140307 9:31:26 [Note] InnoDB: Creating tablespace and datafile system tables.
140307 9:31:26 [Note] InnoDB: Tablespace and datafile system tables created.
140307 9:31:26 [Note] InnoDB: Waiting for purge to start
140307 9:31:26 [Note] InnoDB: 5.6.14 started; log sequence number 0
140307 9:31:26 [Note] Plugin 'FEEDBACK' is disabled.
140307 9:31:26 [ERROR] Function 'TokuDB_fractal_tree_block_map' already exists
140307 9:31:26 [Warning] Couldn't load plugin named 'TokuDB_fractal_tree_block_map' with soname 'ha_tokudb.so'.
140307 9:31:26 [ERROR] Function 'TokuDB_fractal_tree_info' already exists
140307 9:31:26 [Warning] Couldn't load plugin named 'TokuDB_fractal_tree_info' with soname 'ha_tokudb.so'.
140307 9:31:26 [ERROR] Function 'TokuDB_file_map' already exists
140307 9:31:26 [Warning] Couldn't load plugin named 'TokuDB_file_map' with soname 'ha_tokudb.so'.
140307 9:31:26 [ERROR] Can't find symbol 'TokuDB_user_data_exact' in library
140307 9:31:26 [Warning] Couldn't load plugin named 'TokuDB_user_data_exact' with soname 'ha_tokudb.so'.
140307 9:31:26 [ERROR] Can't find symbol 'TokuDB_user_data' in library
140307 9:31:26 [Warning] Couldn't load plugin named 'TokuDB_user_data' with soname 'ha_tokudb.so'.
140307 9:31:26 [Note] Server socket created on IP: '127.0.0.1'.
140307 9:31:26 [Warning] 'db' entry 'prestashop prestashop@@ocalhost' ignored in --skip-name-resolve mode.
140307 9:31:26 [Note] Event Scheduler: Loaded 0 events
140307 9:31:26 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
140307 9:31:26 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.8-MariaDB-1~wheezy' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
2014-03-07 09:33:43 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-07 09:33:43 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-07 09:33:44 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-07 09:33:44 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-07 09:33:44 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-07 09:33:45 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-07 09:33:45 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-07 09:33:45 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
[...]
2014-03-07 09:35:02 7f442677f700 InnoDB: Error: Fetch of persistent statistics requested for table "MQA"."errors" 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.
2014-03-07 09:37:05 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-07 09:37:05 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-07 09:37:05 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-07 09:37:06 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-07 09:37:06 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-07 09:37:06 7f44267c8700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
[...]
Hi,
That error is not critical but some features that use these table statistics might not be optimal especially after shutdown, as noted above it will use transient (in-memory) version as persistent table stats can't be stored.
R: Jan
Hi Jan,
Yes I've recreated those tables, but is this possible there's a bug somewhere in the code using those stats tables which could perhaps explain my initial crash with MQA.errors ?
Thanks and regards,
Jocelyn
Hi,
FYI, no problem with the 10.0.9 upgrade. However, I still don't really understand why it seems there are several call to start & shutdown during this process ? :
140310 22:10:50 [Note] /usr/sbin/mysqld: Normal shutdown
|
|
|
140310 22:10:51 [Note] Event Scheduler: Purging the queue. 0 events
|
140310 22:10:54 [Note] InnoDB: FTS optimize thread exiting.
|
140310 22:10:54 [Note] InnoDB: Starting shutdown...
|
140310 22:10:56 [Note] InnoDB: Shutdown completed; log sequence number 8845526156
|
140310 22:10:57 [Note] /usr/sbin/mysqld: Shutdown complete
|
140310 22:10:57 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
|
140310 22:11:10 [Note] InnoDB: The InnoDB memory heap is disabled
|
140310 22:11:10 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
140310 22:11:10 [Note] InnoDB: Compressed tables use zlib 1.2.7
|
140310 22:11:10 [Note] InnoDB: Using Linux native AIO
|
140310 22:11:10 [Note] InnoDB: Using CPU crc32 instructions
|
140310 22:11:10 [Note] InnoDB: Initializing buffer pool, size = 4.0G
|
140310 22:11:11 [Note] InnoDB: Completed initialization of buffer pool
|
140310 22:11:11 [Note] InnoDB: Highest supported file format is Barracuda.
|
140310 22:11:13 [Note] InnoDB: 128 rollback segment(s) are active.
|
140310 22:11:13 [Note] InnoDB: Waiting for purge to start
|
140310 22:11:13 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.15-63.0 started; log sequence number 8845526156
|
140310 22:11:23 [Note] InnoDB: FTS optimize thread exiting.
|
140310 22:11:23 [Note] InnoDB: Starting shutdown...
|
140310 22:11:25 [Note] InnoDB: Shutdown completed; log sequence number 8845528348
|
140310 22:11:25 [Note] InnoDB: The InnoDB memory heap is disabled
|
140310 22:11:25 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
140310 22:11:25 [Note] InnoDB: Compressed tables use zlib 1.2.7
|
140310 22:11:25 [Note] InnoDB: Using Linux native AIO
|
140310 22:11:25 [Note] InnoDB: Using CPU crc32 instructions
|
140310 22:11:25 [Note] InnoDB: Initializing buffer pool, size = 4.0G
|
140310 22:11:25 [Note] InnoDB: Completed initialization of buffer pool
|
140310 22:11:25 [Note] InnoDB: Highest supported file format is Barracuda.
|
140310 22:11:26 [Note] InnoDB: 128 rollback segment(s) are active.
|
140310 22:11:27 [Note] InnoDB: Waiting for purge to start
|
140310 22:11:27 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.15-63.0 started; log sequence number 8845528348
|
140310 22:11:28 [Note] InnoDB: FTS optimize thread exiting.
|
140310 22:11:28 [Note] InnoDB: Starting shutdown...
|
140310 22:11:30 [Note] InnoDB: Shutdown completed; log sequence number 8845531481
|
140310 22:11:31 [Note] InnoDB: The InnoDB memory heap is disabled
|
140310 22:11:31 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
140310 22:11:31 [Note] InnoDB: Compressed tables use zlib 1.2.7
|
140310 22:11:31 [Note] InnoDB: Using Linux native AIO
|
140310 22:11:31 [Note] InnoDB: Using CPU crc32 instructions
|
140310 22:11:31 [Note] InnoDB: Initializing buffer pool, size = 4.0G
|
140310 22:11:31 [Note] InnoDB: Completed initialization of buffer pool
|
140310 22:11:31 [Note] InnoDB: Highest supported file format is Barracuda.
|
140310 22:11:32 [Note] InnoDB: 128 rollback segment(s) are active.
|
140310 22:11:33 [Note] InnoDB: Waiting for purge to start
|
140310 22:11:33 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.15-63.0 started; log sequence number 8845531481
|
140310 22:11:33 [Note] Plugin 'FEEDBACK' is disabled.
|
140310 22:11:34 [Note] InnoDB: FTS optimize thread exiting.
|
140310 22:11:34 [Note] InnoDB: Starting shutdown...
|
140310 22:11:36 [Note] InnoDB: Shutdown completed; log sequence number 8845535312
|
140310 22:11:37 [Note] InnoDB: The InnoDB memory heap is disabled
|
140310 22:11:37 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
140310 22:11:37 [Note] InnoDB: Compressed tables use zlib 1.2.7
|
140310 22:11:37 [Note] InnoDB: Using Linux native AIO
|
140310 22:11:37 [Note] InnoDB: Using CPU crc32 instructions
|
140310 22:11:37 [Note] InnoDB: Initializing buffer pool, size = 4.0G
|
140310 22:11:37 [Note] InnoDB: Completed initialization of buffer pool
|
140310 22:11:37 [Note] InnoDB: Highest supported file format is Barracuda.
|
140310 22:11:38 [Note] InnoDB: 128 rollback segment(s) are active.
|
140310 22:11:38 [Note] InnoDB: Waiting for purge to start
|
140310 22:11:38 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.15-63.0 started; log sequence number 8845535312
|
140310 22:11:38 [Note] Plugin 'FEEDBACK' is disabled.
|
140310 22:11:40 [Note] InnoDB: FTS optimize thread exiting.
|
140310 22:11:40 [Note] InnoDB: Starting shutdown...
|
140310 22:11:42 [Note] InnoDB: Shutdown completed; log sequence number 8845539392
|
140310 22:11:42 [Note] InnoDB: The InnoDB memory heap is disabled
|
140310 22:11:42 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
140310 22:11:42 [Note] InnoDB: Compressed tables use zlib 1.2.7
|
140310 22:11:42 [Note] InnoDB: Using Linux native AIO
|
140310 22:11:42 [Note] InnoDB: Using CPU crc32 instructions
|
140310 22:11:42 [Note] InnoDB: Initializing buffer pool, size = 4.0G
|
140310 22:11:42 [Note] InnoDB: Completed initialization of buffer pool
|
140310 22:11:43 [Note] InnoDB: Highest supported file format is Barracuda.
|
140310 22:11:44 [Note] InnoDB: 128 rollback segment(s) are active.
|
140310 22:11:44 [Note] InnoDB: Waiting for purge to start
|
140310 22:11:44 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.15-63.0 started; log sequence number 8845539392
|
140310 22:11:44 [Note] Plugin 'FEEDBACK' is disabled.
|
140310 22:11:46 [Note] InnoDB: FTS optimize thread exiting.
|
140310 22:11:46 [Note] InnoDB: Starting shutdown...
|
140310 22:11:48 [Note] InnoDB: Shutdown completed; log sequence number 8845543718
|
140310 22:11:48 mysqld_safe Starting mysqld daemon with databases from /home/mysql/data
|
140310 22:11:49 [Note] InnoDB: The InnoDB memory heap is disabled
|
140310 22:11:49 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
140310 22:11:49 [Note] InnoDB: Compressed tables use zlib 1.2.7
|
140310 22:11:49 [Note] InnoDB: Using Linux native AIO
|
140310 22:11:49 [Note] InnoDB: Using CPU crc32 instructions
|
140310 22:11:49 [Note] InnoDB: Initializing buffer pool, size = 4.0G
|
140310 22:11:49 [Note] InnoDB: Completed initialization of buffer pool
|
140310 22:11:49 [Note] InnoDB: Highest supported file format is Barracuda.
|
140310 22:11:50 [Note] InnoDB: 128 rollback segment(s) are active.
|
140310 22:11:50 [Note] InnoDB: Waiting for purge to start
|
140310 22:11:50 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.15-63.0 started; log sequence number 8845543718
|
140310 22:11:50 [Note] Plugin 'FEEDBACK' is disabled.
|
140310 22:11:50 [ERROR] Function 'TokuDB_fractal_tree_block_map' already exists
|
140310 22:11:50 [Warning] Couldn't load plugin named 'TokuDB_fractal_tree_block_map' with soname 'ha_tokudb.so'.
|
140310 22:11:50 [ERROR] Function 'TokuDB_fractal_tree_info' already exists
|
140310 22:11:50 [Warning] Couldn't load plugin named 'TokuDB_fractal_tree_info' with soname 'ha_tokudb.so'.
|
140310 22:11:50 [ERROR] Function 'TokuDB_file_map' already exists
|
140310 22:11:50 [Warning] Couldn't load plugin named 'TokuDB_file_map' with soname 'ha_tokudb.so'.
|
140310 22:11:50 [ERROR] Can't find symbol 'TokuDB_user_data_exact' in library
|
140310 22:11:50 [Warning] Couldn't load plugin named 'TokuDB_user_data_exact' with soname 'ha_tokudb.so'.
|
140310 22:11:50 [ERROR] Can't find symbol 'TokuDB_user_data' in library
|
140310 22:11:50 [Warning] Couldn't load plugin named 'TokuDB_user_data' with soname 'ha_tokudb.so'.
|
140310 22:11:51 [Note] Server socket created on IP: '127.0.0.1'.
|
140310 22:11:51 [Warning] 'db' entry 'prestashop prestashop@@ocalhost' ignored in --skip-name-resolve mode.
|
140310 22:11:51 [Note] Event Scheduler: Loaded 0 events
|
140310 22:11:51 [Note] /usr/sbin/mysqld: ready for connections.
|
Version: '10.0.9-MariaDB-1~wheezy' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
|
|
|
Status information:
|
|
|
Current dir: /home/mysql/data/
|
Running threads: 1 Stack size: 294912
|
Current locks:
|
lock: 0x7f506f82d198:
|
|
|
lock: 0x7f506f818508:
|
|
|
lock: 0x7f5198b6f788:
|
|
|
lock: 0x7f5198b63788:
|
|
|
lock: 0x7f51a0fe8f88:
|
|
|
lock: 0x7f5198b62b88:
|
|
|
lock: 0x7f51a0fe6788:
|
|
|
lock: 0x7f51a0fe5388:
|
|
|
lock: 0x7f51b389eb88:
|
|
|
lock: 0x7f5198be6388:
|
|
|
lock: 0x7f5198b5fb88:
|
|
|
lock: 0x7f51a0fe2188:
|
|
|
lock: 0x7f51b7445b40:
|
|
|
lock: 0x7f51b7445a40:
|
|
|
lock: 0x7f51b7444840:
|
|
|
lock: 0x7f51b7444740:
|
|
|
lock: 0x7f51b7444640:
|
|
|
lock: 0x7f51b7444a40:
|
|
|
lock: 0x7f51b7442840:
|
|
|
lock: 0x7f51b7445940:
|
|
|
lock: 0x7f51b7443040:
|
|
|
lock: 0x7f51b7443340:
|
|
|
lock: 0x7f51b7442f40:
|
|
|
lock: 0x7f51b7443240:
|
|
|
lock: 0x7f51b7442e40:
|
|
|
lock: 0x7f51b7443140:
|
|
|
lock: 0x7f51b7443740:
|
|
|
lock: 0x7f51b7443840:
|
|
|
lock: 0x7f51b7443940:
|
|
|
lock: 0x7f51b7442d40:
|
|
|
lock: 0x7f51b7442a40:
|
|
|
lock: 0x7f51b7442c40:
|
|
|
lock: 0x7f51b7442940:
|
|
|
lock: 0x7f51b7442b40:
|
|
|
lock: 0x7f51b7443440:
|
|
|
lock: 0x7f51b7443540:
|
|
|
lock: 0x7f51b7443640:
|
|
|
lock: 0x7f51b7445540:
|
|
|
lock: 0x7f51b7445840:
|
|
|
lock: 0x7f51b7445740:
|
|
|
lock: 0x7f51b7445640:
|
|
|
lock: 0x7f51b7445140:
|
|
|
lock: 0x7f51b7445040:
|
|
|
lock: 0x7f51b7444f40:
|
|
|
lock: 0x7f51b7444e40:
|
|
|
lock: 0x7f51b7444d40:
|
|
|
lock: 0x7f51b7445340:
|
|
|
lock: 0x7f51b7444c40:
|
|
|
lock: 0x7f51b7444b40:
|
|
|
lock: 0x7f51b7445440:
|
|
|
lock: 0x7f51b7444940:
|
|
|
lock: 0x7f51b7444440:
|
|
|
lock: 0x7f51b7444540:
|
|
|
lock: 0x7f51b7444340:
|
|
|
lock: 0x7f51b7444240:
|
|
|
lock: 0x7f51b7443e40:
|
|
|
lock: 0x7f51b7444140:
|
|
|
lock: 0x7f51b7444040:
|
|
|
lock: 0x7f51b7443d40:
|
|
|
lock: 0x7f51b7443f40:
|
|
|
lock: 0x7f51b7443a40:
|
|
|
lock: 0x7f51b7443b40:
|
|
|
lock: 0x7f51b7443c40:
|
|
|
lock: 0x7f51b7445240:
|
|
|
|
|
Key caches:
|
default
|
Buffer_size: 134217728
|
Block_size: 1024
|
Division_limit: 100
|
Age_threshold: 300
|
Partitions: 0
|
blocks used: 4
|
not flushed: 0
|
w_requests: 0
|
writes: 0
|
r_requests: 8
|
reads: 4
|
|
|
|
|
handler status:
|
read_key: 0
|
read_next: 0
|
read_rnd 0
|
read_first: 0
|
write: 0
|
delete 0
|
update: 0
|
|
|
Table status:
|
Opened tables: 0
|
Open tables: 63
|
Open files: 26
|
Open streams: 0
|
|
|
Alarm status:
|
Active alarms: 0
|
Max used alarms: 0
|
Next alarm time: 0
|
140310 22:11:54 [Warning] 'db' entry 'prestashop prestashop@@ocalhost' ignored in --skip-name-resolve mode.
|
|
|
Memory status:
|
Non-mmapped space allocated from system: 0
|
Number of free chunks: 1
|
Number of fastbin blocks: 0
|
Number of mmapped regions: 0
|
Space in mmapped regions: 0
|
Maximum total allocated space: 0
|
Space available in freed fastbin blocks: 0
|
Total allocated space: 0
|
Total free space: 0
|
Top-most, releasable space: 0
|
Estimated memory (with thread stack): 294912
|
|
|
|
|
|
|
Events status:
|
LLA = Last Locked At LUA = Last Unlocked At
|
WOC = Waiting On Condition DL = Data Locked
|
|
|
Event scheduler status:
|
State : INITIALIZED
|
Thread id : 0
|
LLA : n/a:0
|
LUA : n/a:0
|
WOC : NO
|
Workers : 0
|
Executed : 0
|
Data locked: NO
|
|
|
Event queue status:
|
Element count : 0
|
Data locked : NO
|
Attempting lock : NO
|
LLA : init_queue:139
|
LUA : init_queue:149
|
WOC : NO
|
Next activation : never
|
140310 22:12:15 [Warning] 'db' entry 'prestashop prestashop@@ocalhost' ignored in --skip-name-resolve mode.
|
The output during the upgrade :
Pr?paration du remplacement de mariadb-server 10.0.8+maria-1~wheezy (en utilisant .../mariadb-server_10.0.9+maria-1~wheezy_all.deb) ...
|
D?paquetage de la mise ? jour de mariadb-server ...
|
Pr?paration du remplacement de mariadb-client 10.0.8+maria-1~wheezy (en utilisant .../mariadb-client_10.0.9+maria-1~wheezy_all.deb) ...
|
D?paquetage de la mise ? jour de mariadb-client ...
|
Pr?paration du remplacement de mysql-common 10.0.8+maria-1~wheezy (en utilisant .../mysql-common_10.0.9+maria-1~wheezy_all.deb) ...
|
D?paquetage de la mise ? jour de mysql-common ...
|
Pr?paration du remplacement de mariadb-common 10.0.8+maria-1~wheezy (en utilisant .../mariadb-common_10.0.9+maria-1~wheezy_all.deb) ...
|
D?paquetage de la mise ? jour de mariadb-common ...
|
Pr?paration du remplacement de libmariadbclient18 10.0.8+maria-1~wheezy (en utilisant .../libmariadbclient18_10.0.9+maria-1~wheezy_amd64.deb) ...
|
D?paquetage de la mise ? jour de libmariadbclient18 ...
|
Pr?paration du remplacement de libmysqlclient18 10.0.8+maria-1~wheezy (en utilisant .../libmysqlclient18_10.0.9+maria-1~wheezy_amd64.deb) ...
|
D?paquetage de la mise ? jour de libmysqlclient18 ...
|
Pr?paration du remplacement de mariadb-client-core-10.0 10.0.8+maria-1~wheezy (en utilisant .../mariadb-client-core-10.0_10.0.9+maria-1~wheezy_amd64.deb) ...
|
D?paquetage de la mise ? jour de mariadb-client-core-10.0 ...
|
Pr?paration du remplacement de mariadb-client-10.0 10.0.8+maria-1~wheezy (en utilisant .../mariadb-client-10.0_10.0.9+maria-1~wheezy_amd64.deb) ...
|
D?paquetage de la mise ? jour de mariadb-client-10.0 ...
|
Pr?paration du remplacement de mariadb-server-core-10.0 10.0.8+maria-1~wheezy (en utilisant .../mariadb-server-core-10.0_10.0.9+maria-1~wheezy_amd64.deb) ...
|
D?paquetage de la mise ? jour de mariadb-server-core-10.0 ...
|
Traitement des actions diff?r?es (??triggers??) pour ??man-db??...
|
Param?trage de mysql-common (10.0.9+maria-1~wheezy) ...
|
Param?trage de mariadb-common (10.0.9+maria-1~wheezy) ...
|
(Lecture de la base de donn?es... 97806 fichiers et r?pertoires d?j? install?s.)
|
Pr?paration du remplacement de mariadb-server-10.0 10.0.8+maria-1~wheezy (en utilisant .../mariadb-server-10.0_10.0.9+maria-1~wheezy_amd64.deb) ...
|
Stopping MariaDB database server: mysqld.
|
Stopping MariaDB database server: mysqld.
|
D?paquetage de la mise ? jour de mariadb-server-10.0 ...
|
Pr?paration du remplacement de libmariadbclient-dev 10.0.8+maria-1~wheezy (en utilisant .../libmariadbclient-dev_10.0.9+maria-1~wheezy_amd64.deb) ...
|
D?paquetage de la mise ? jour de libmariadbclient-dev ...
|
Pr?paration du remplacement de libmariadbd-dev 10.0.8+maria-1~wheezy (en utilisant .../libmariadbd-dev_10.0.9+maria-1~wheezy_amd64.deb) ...
|
D?paquetage de la mise ? jour de libmariadbd-dev ...
|
Pr?paration du remplacement de udisks 1.0.4-7 (en utilisant .../udisks_1.0.4-7wheezy1_amd64.deb) ...
|
D?paquetage de la mise ? jour de udisks ...
|
Traitement des actions diff?r?es (??triggers??) pour ??man-db??...
|
Param?trage de udisks (1.0.4-7wheezy1) ...
|
Param?trage de libmysqlclient18 (10.0.9+maria-1~wheezy) ...
|
Param?trage de libmariadbclient18 (10.0.9+maria-1~wheezy) ...
|
Param?trage de mariadb-client-core-10.0 (10.0.9+maria-1~wheezy) ...
|
Param?trage de mariadb-client-10.0 (10.0.9+maria-1~wheezy) ...
|
Param?trage de mariadb-server-core-10.0 (10.0.9+maria-1~wheezy) ...
|
Param?trage de mariadb-server-10.0 (10.0.9+maria-1~wheezy) ...
|
Stopping MariaDB database server: mysqld.
|
Starting MariaDB database server: mysqld . ..
|
Checking for corrupt, not cleanly closed and upgrade needing tables..
|
Param?trage de mariadb-server (10.0.9+maria-1~wheezy) ...
|
Param?trage de mariadb-client (10.0.9+maria-1~wheezy) ...
|
Param?trage de libmariadbclient-dev (10.0.9+maria-1~wheezy) ...
|
Param?trage de libmariadbd-dev (10.0.9+maria-1~wheezy) ...
|
I'm not familiar with debian upgrade process but based on log these were normal shutdowns i.e. external shutdown requests not any crashes or unexpected shutdowns. Now that upgrade does work, I will close the issue.
Hi Jan,
Not sure the initial problem is really fixed : I've disabled innodb_use_fallocate before the upgrade.
I'll let you know if I have any other similar corruption.
Thanks,
Jocelyn