Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Incomplete
-
Affects Version/s: 5.5.37
-
Fix Version/s: N/A
-
Component/s: Storage Engine - XtraDB
-
Labels:None
-
Environment:centos-6.6
Description
150227 13:28:56 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 150227 13:28:56 InnoDB: The InnoDB memory heap is disabled 150227 13:28:56 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150227 13:28:56 InnoDB: Compressed tables use zlib 1.2.3 150227 13:28:56 InnoDB: Using Linux native AIO 150227 13:28:56 InnoDB: Initializing buffer pool, size = 1.0G 150227 13:28:56 InnoDB: Completed initialization of buffer pool 150227 13:28:56 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 12156478210 150227 13:28:56 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 12156486587 150227 13:28:56 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 4 6 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 150227 13:28:57 InnoDB: Waiting for the background threads to start 150227 13:28:58 Percona XtraDB (http://www.percona.com) 5.5.37-MariaDB-34.0 started; log sequence number 12156486587 150227 13:28:58 [Note] Plugin 'FEEDBACK' is disabled. 150227 13:28:58 [ERROR] mysqld got signal 4 ; 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: 5.5.37-MariaDB key_buffer_size=134217728 read_buffer_size=1048576 max_used_connections=0 max_threads=153 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 447133 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x7fffb6712a20 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 = 0x7fffb67171a0 thread_stack 0x48000 /usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x7f0e91f3449e] /usr/libexec/mysqld(handle_fatal_signal+0x4ac)[0x7f0e91b7c3cc] /lib64/libpthread.so.0(+0xf710)[0x7f0e912a8710] /usr/libexec/mysqld(+0x7dc150)[0x7f0e91eb4150] /usr/libexec/mysqld(+0x7d9c71)[0x7f0e91eb1c71] /usr/libexec/mysqld(_ZN7handler7ha_openEP5TABLEPKcij+0x3e)[0x7f0e91b7ea6e] /usr/libexec/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x6d7)[0x7f0e91ad5777] /usr/libexec/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0xd06)[0x7f0e91a075e6] /usr/libexec/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x47d)[0x7f0e91a0834d] /usr/libexec/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x44)[0x7f0e91a08da4] /usr/libexec/mysqld(+0x375cce)[0x7f0e91a4dcce] /usr/libexec/mysqld(_Z11plugin_initPiPPci+0x95e)[0x7f0e91a521fe] /usr/libexec/mysqld(+0x2ef0ab)[0x7f0e919c70ab] /usr/libexec/mysqld(_Z11mysqld_mainiPPc+0x542)[0x7f0e919c7ee2] /lib64/libc.so.6(__libc_start_main+0xfd)[0x7f0e8faf1d5d] /usr/libexec/mysqld(+0x2e4875)[0x7f0e919bc875] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): is an invalid pointer Connection ID (thread ID): 0 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off 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. 150227 13:28:58 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
it's happened every time. unfortunately it's a production database so unfortunately i can't send.
Apparently, the problem is related to the data being somehow corrupted after a previous crash (it says in the log that the database was not shut down normally), so it can only be investigated on this particular data. And this crash is very unusual, I don't think we have ever got any reports about the server crashing with signal 4, so we can't even make assumptions based on previous experience.
Do you have a test instance where you could copy your data directory and perform some experiments which we would ask you for?
If you can set up a test instance, we'll provide you with a debug binary of 5.5.37 to get a meaningful stack trace, and then will ask you to try 5.5.42 (the latest 5.5 release) to see if it's still reproducible.
If you cannot do it, you might want to try different values of innodb_force_recovery (see http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html), starting from 1 and up until you can start the server and hopefully recover most or all of your data.
even if i delete all directory and file under /var/lib/mysql/* except the directory mysql it's still not able to start.
Does it fail on an empty datadir with the same error, or with a different one? Can you paste the error log from that attempt?
If you could remove the data, can you maybe try creating a totally new datadir (running mysql_install_db) and see if the server starts there? Maybe there's something wrong with system tables in mysql.
If it fails the same way on an empty datadir, we might need to look in a different direction. Did anything happen on your system since the last time MariaDB server started? Did you perform MariaDB upgrade, or system upgrade, or changed system configuration somehow – anything at all?
Closing as incomplete for now, please comment to re-open if you have further information.
Hi,
Does it happen every time you attempt to start the server?
Is it a production database? Would you be able to pack the whole datadir and upload it for us to ftp.askmonty.org/private? (Only MariaDB developers will have access to it)