Пытался залить из бекапа через phpmyadmin базу данных... по средине загрузки БД упаала mariadb и больше не в какую не хочет запускаться... Помогите пожалуйста...
[root@datebase mysql]# service mysql start
Starting MySQL. ERROR!
[root@datebase mysql]# cat error.log
160215 14:26:15 mysqld_safe Starting mysqld daemon with databases from /var/lib/m ysql
160215 14:26:16 [Note] /usr/sbin/mysqld (mysqld 10.0.23-MariaDB) starting as proc ess 31558 ...
160215 14:26:16 [Note] InnoDB: Using mutexes to ref count buffer pool pages
160215 14:26:16 [Note] InnoDB: The InnoDB memory heap is disabled
160215 14:26:16 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
160215 14:26:16 [Note] InnoDB: Memory barrier is not used
160215 14:26:16 [Note] InnoDB: Compressed tables use zlib 1.2.7
160215 14:26:16 [Note] InnoDB: Using Linux native AIO
160215 14:26:16 [Note] InnoDB: Using CPU crc32 instructions
160215 14:26:16 [Note] InnoDB: Initializing buffer pool, size = 128.0M
160215 14:26:16 [Note] InnoDB: Completed initialization of buffer pool
160215 14:26:16 [Note] InnoDB: Highest supported file format is Barracuda.
160215 14:26:16 [Note] InnoDB: The log sequence numbers 788704121 and 788704121 i n ibdata files do not match the log sequence number 989004367 in the ib_logfiles!
160215 14:26:16 [Note] InnoDB: Database was not shutdown normally!
160215 14:26:16 [Note] InnoDB: Starting crash recovery.
160215 14:26:16 [Note] InnoDB: Reading tablespace information from the .ibd files ...
160215 14:26:16 [Note] InnoDB: Restoring possible half-written data pages
160215 14:26:16 [Note] InnoDB: from the doublewrite buffer...
160215 14:26:16 [Note] InnoDB: 128 rollback segment(s) are active.
160215 14:26:16 [Note] InnoDB: Waiting for purge to start
160215 14:26:16 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-76 .0 started; log sequence number 989004367
160215 14:26:16 [Note] Plugin 'FEEDBACK' is disabled.
160215 14:26:16 [ERROR] mysqld got signal 11 ;
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.23-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
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 = 467003 K b ytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x7fee8fa7f008
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 = 0x7fffbcbc2a30 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0xbd0aae]
/usr/sbin/mysqld(handle_fatal_signal+0x390)[0x73aa40]
/lib64/libpthread.so.0(+0xf100)[0x7feea486b100]
/usr/sbin/mysqld(_Z9get_fieldP11st_mem_rootP5Field+0x1b)[0x679c0b]
/usr/sbin/mysqld[0x69e22c]
/usr/sbin/mysqld(_Z14servers_reloadP3THD+0x1bf)[0x69ea3f]
/usr/sbin/mysqld(_Z12servers_initb+0x103)[0x69eba3]
/usr/sbin/mysqld[0x53a01f]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x498)[0x53f608]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7feea300bb15]
/usr/sbin/mysqld[0x5347e9]
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,i ndex_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pus hdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,first match=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_matc h_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_b ased=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_c ache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_s ize=off,table_elimination=on,extended_keys=on,exists_to_in=on
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.
160215 14:26:16 mysqld_safe mysqld from pid file /var/lib/mysql/datebase.service- voice.com.pid ended
