mariadb报错

a5525510

执行 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日志，请大神帮忙看看

1. 150917  8:05:35 [ERROR] mysqld got signal 6 ;
   
2. This could be because you hit a bug. It is also possible that this binary
   
3. or one of the libraries it was linked against is corrupt, improperly built,
   
4. or misconfigured. This error can also be caused by malfunctioning hardware.
   
5. 
   
6. To report this bug, see http----（----我添加的）://kb.askmonty.org/en/reporting-bugs
   
7. 
   
8. We will try our best to scrape up some info that will hopefully help
   
9. diagnose the problem, but since we have already crashed,
   
10. something is definitely wrong and this may fail.
    
11. 
    
12. Server version: 5.5.44-MariaDB
    
13. key_buffer_size=134217728
    
14. read_buffer_size=131072
    
15. max_used_connections=0
    
16. max_threads=153
    
17. thread_count=0
    
18. It is possible that mysqld could use up to
    
19. key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466713 K  bytes of memory
    
20. Hope that's ok; if not, decrease some variables in the equation.
    
21. 
    
22. Thread pointer: 0x0x0
    
23. Attempting backtrace. You can use the following information to find out
    
24. where mysqld died. If you see no messages after this, something went
    
25. terribly wrong...
    
26. stack_bottom = 0x0 thread_stack 0x48000
    
27. /usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x7f10b65af15d]
    
28. /usr/libexec/mysqld(handle_fatal_signal+0x515)[0x7f10b61c43b5]
    
29. /lib64/libpthread.so.0(+0xf130)[0x7f10b58f4130]
    
30. /lib64/libc.so.6(gsignal+0x37)[0x7f10b40a95d7]
    
31. /lib64/libc.so.6(abort+0x148)[0x7f10b40aacc8]
    
32. /usr/libexec/mysqld(+0x2d5688)[0x7f10b5ffa688]
    
33. /usr/libexec/mysqld(+0x6eb590)[0x7f10b6410590]
    
34. /usr/libexec/mysqld(+0x64bbbe)[0x7f10b6370bbe]
    
35. /usr/libexec/mysqld(+0x665133)[0x7f10b638a133]
    
36. /usr/libexec/mysqld(+0x65afbd)[0x7f10b637ffbd]
    
37. /usr/libexec/mysqld(+0x65cda1)[0x7f10b6381da1]
    
38. /usr/libexec/mysqld(+0x6559df)[0x7f10b637a9df]
    
39. /usr/libexec/mysqld(+0x73e96c)[0x7f10b646396c]
    
40. /usr/libexec/mysqld(+0x73fdfa)[0x7f10b6464dfa]
    
41. /usr/libexec/mysqld(+0x653d79)[0x7f10b6378d79]
    
42. /usr/libexec/mysqld(+0x654446)[0x7f10b6379446]
    
43. /lib64/libpthread.so.0(+0x7df5)[0x7f10b58ecdf5]
    
44. /lib64/libc.so.6(clone+0x6d)[0x7f10b416a1ad]
    
45. The manual page at http----（----我添加的）://dev.mysql.com/doc/mysql/en/crashing.html contains
    
46. information that should help you find out what is causing the crash.
    
47. 150917 08:05:36 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
    
48. 150917 08:33:14 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    
49. 150917  8:33:14 [Note] /usr/libexec/mysqld (mysqld 5.5.44-MariaDB) starting as process 4517 ...
    
50. 150917  8:33:14 InnoDB: The InnoDB memory heap is disabled
    
51. 150917  8:33:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    
52. 150917  8:33:14 InnoDB: Compressed tables use zlib 1.2.7
    
53. 150917  8:33:14 InnoDB: Using Linux native AIO
    
54. 150917  8:33:14 InnoDB: Initializing buffer pool, size = 128.0M
    
55. 150917  8:33:14 InnoDB: Completed initialization of buffer pool
    
56. 150917  8:33:14 InnoDB: highest supported file format is Barracuda.
    
57. InnoDB: Log scan progressed past the checkpoint lsn 9326855
    
58. 150917  8:33:14  InnoDB: Database was not shut down normally!
    
59. InnoDB: Starting crash recovery.
    
60. InnoDB: Reading tablespace information from the .ibd files...
    
61. InnoDB: Restoring possible half-written data pages from the doublewrite
    
62. InnoDB: buffer...
    
63. InnoDB: Doing recovery: scanned up to log sequence number 9327504
    
64. InnoDB: 1 transaction(s) which must be rolled back or cleaned up
    
65. InnoDB: in total 1 row operations to undo
    
66. InnoDB: Trx id counter is 9B00
    
67. 150917  8:33:15  InnoDB: Starting an apply batch of log records to the database...
    
68. 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
    
69. InnoDB: Apply batch completed
    
70. 150917  8:33:15  InnoDB: Waiting for the background threads to start
    
71. InnoDB: Starting in background the rollback of uncommitted transactions
    
72. 150917  8:33:15  InnoDB: Rolling back trx with id 990F, 1 rows to undo
    
73. 150917  8:33:15  InnoDB: Assertion failure in thread 140695227995904 in file fut0lst.ic line 83
    
74. InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
    
75. InnoDB: We intentionally generate a memory trap.
    
76. InnoDB: Submit a detailed bug report to http----（----我添加的）://bugs.mysql.com.
    
77. InnoDB: If you get repeated assertion failures or crashes, even
    
78. InnoDB: immediately after the mysqld startup, there may be
    
79. InnoDB: corruption in the InnoDB tablespace. Please refer to
    
80. InnoDB: http----（----我添加的）://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
    
81. InnoDB: about forcing recovery.

复制代码

csoho2000

看看防火墙

a5525510

回复 2# csoho2000


    防火墙已经关闭。经分析是由于电脑突然死机，导致了mysql临时数据过多，已经重新部署。

小小小兔

不错的，看来支持呢