OS:Centos6
MySQLのバージョン:mysql-5.1.52-1
本日、突然にMySQLが起動しなくなりました。
Error: A Database connection using "Mysql" was missing or unable to connect.
The database server returned this error: SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
mysql.sockを作成して、MySQLを再起動させるとmysql.sockが消滅してしまいます。
ログの見方が不十分で、よくわからないのですが、
「my.cnf」に「innodb_force_recovery = 3」をして、起動することも行っていますがダメです。
以下のログを見ていただき、解決方法などを教えていただけないでしょうか。
よろしくお願いします。
190719 20:21:47 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 190719 20:26:24 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 190719 20:26:24 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead. 190719 20:26:24 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead. 190719 20:26:24 InnoDB: Initializing buffer pool, size = 1.0G 190719 20:26:24 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 2696 134077419 190719 20:26:24 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 2696 134156521 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 29422 row operations to undo InnoDB: Trx id counter is 0 249070848 190719 20:26:24 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 46 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 11:26:24 UTC - 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. 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. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=0 max_threads=50 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 117508 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 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 = 0 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x29) [0x850ca9] /usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a4143] /lib64/libpthread.so.0(+0xf7e0) [0x2ace1f8a67e0] /usr/libexec/mysqld(page_cur_insert_rec_low+0x288) [0x799be8] /usr/libexec/mysqld(page_cur_parse_insert_rec+0x4eb) [0x79a78b] /usr/libexec/mysqld() [0x787c3d] /usr/libexec/mysqld(recv_recover_page+0x34f) [0x7896ff] /usr/libexec/mysqld(buf_page_io_complete+0x548) [0x74aab8] /usr/libexec/mysqld(fil_aio_wait+0xfa) [0x762c6a] /usr/libexec/mysqld() [0x7c8ce0] /lib64/libpthread.so.0(+0x7aa1) [0x2ace1f89eaa1] /lib64/libc.so.6(clone+0x6d) [0x2ace211fac4d] 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. 190719 20:26:24 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
あなたの回答
tips
プレビュー