mariadb报错

执行 neutron agent-list 报错 经分析发现mysql起不来了，
[root@controller mariadb]# mysql -u root -p
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)

贴出mariadb.log日志，请大神帮忙看看


[mw_shl_code=actionscript3,true]150917  8:05:35 [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: 5.5.44-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 = 466713 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/libexec/mysqld(my_print_stacktrace+0x3d)[0x7f10b65af15d]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x7f10b61c43b5]
/lib64/libpthread.so.0(+0xf130)[0x7f10b58f4130]
/lib64/libc.so.6(gsignal+0x37)[0x7f10b40a95d7]
/lib64/libc.so.6(abort+0x148)[0x7f10b40aacc8]
/usr/libexec/mysqld(+0x2d5688)[0x7f10b5ffa688]
/usr/libexec/mysqld(+0x6eb590)[0x7f10b6410590]
/usr/libexec/mysqld(+0x64bbbe)[0x7f10b6370bbe]
/usr/libexec/mysqld(+0x665133)[0x7f10b638a133]
/usr/libexec/mysqld(+0x65afbd)[0x7f10b637ffbd]
/usr/libexec/mysqld(+0x65cda1)[0x7f10b6381da1]
/usr/libexec/mysqld(+0x6559df)[0x7f10b637a9df]
/usr/libexec/mysqld(+0x73e96c)[0x7f10b646396c]
/usr/libexec/mysqld(+0x73fdfa)[0x7f10b6464dfa]
/usr/libexec/mysqld(+0x653d79)[0x7f10b6378d79]
/usr/libexec/mysqld(+0x654446)[0x7f10b6379446]
/lib64/libpthread.so.0(+0x7df5)[0x7f10b58ecdf5]
/lib64/libc.so.6(clone+0x6d)[0x7f10b416a1ad]
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.
150917 08:05:36 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
150917 08:33:14 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150917  8:33:14 [Note] /usr/libexec/mysqld (mysqld 5.5.44-MariaDB) starting as process 4517 ...
150917  8:33:14 InnoDB: The InnoDB memory heap is disabled
150917  8:33:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150917  8:33:14 InnoDB: Compressed tables use zlib 1.2.7
150917  8:33:14 InnoDB: Using Linux native AIO
150917  8:33:14 InnoDB: Initializing buffer pool, size = 128.0M
150917  8:33:14 InnoDB: Completed initialization of buffer pool
150917  8:33:14 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 9326855
150917  8:33:14  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 9327504
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 9B00
150917  8:33:15  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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
150917  8:33:15  InnoDB: Waiting for the background threads to start
InnoDB: Starting in background the rollback of uncommitted transactions
150917  8:33:15  InnoDB: Rolling back trx with id 990F, 1 rows to undo
150917  8:33:15  InnoDB: Assertion failure in thread 140695227995904 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
150917  8:33:15 [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: 5.5.44-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 = 466713 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/libexec/mysqld(my_print_stacktrace+0x3d)[0x7ff64764a15d]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x7ff64725f3b5]
/lib64/libpthread.so.0(+0xf130)[0x7ff64698f130]
/lib64/libc.so.6(gsignal+0x37)[0x7ff6451445d7]
/lib64/libc.so.6(abort+0x148)[0x7ff645145cc8]
/usr/libexec/mysqld(+0x2d5688)[0x7ff647095688]
/usr/libexec/mysqld(+0x6eb590)[0x7ff6474ab590]
/usr/libexec/mysqld(+0x64bbbe)[0x7ff64740bbbe]
/usr/libexec/mysqld(+0x665133)[0x7ff647425133]
/usr/libexec/mysqld(+0x65afbd)[0x7ff64741afbd]
/usr/libexec/mysqld(+0x65cda1)[0x7ff64741cda1]
/usr/libexec/mysqld(+0x6559df)[0x7ff6474159df]
/usr/libexec/mysqld(+0x73e96c)[0x7ff6474fe96c]
/usr/libexec/mysqld(+0x73fdfa)[0x7ff6474ffdfa]
/usr/libexec/mysqld(+0x653d79)[0x7ff647413d79]
/usr/libexec/mysqld(+0x654446)[0x7ff647414446]
/lib64/libpthread.so.0(+0x7df5)[0x7ff646987df5]
/lib64/libc.so.6(clone+0x6d)[0x7ff6452051ad]
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.
150917 08:33:15 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended[/mw_shl_code]

虚拟机内存多大

Can't connect to local MySQL server through socket '
没有登录进来，密码是不是错了。

密码没有错就重新安装下

Alkaloid0515 发表于 2015-9-17 22:53
Can't connect to local MySQL server through socket '
没有登录进来，密码是不是错了。

经过分析，是由于在安装过程中 电脑突然司机了，导致了mysql无法回滚。临时文件太大