いつもお世話になっております。
標記の件につきまして、phpのあるスクリプトの不具合で
MySQLでトランザクションのロックが大量に発生してしまい、
手動でプロセスを削除したのですが、削除し切れず
MySQL自体をいったん停止させようとしたところ、
何回かトライしても停止に失敗してしまったので、
サーバの方で再起動をかけてみました。
OS: CentOS6.4
mysql Ver 14.14 Distrib 5.5.47, for Linux (x86_64) using readline 5.1
その後、MySQLが正常に起動せず、エラーログに以下のように
出力されております。
Bash
1161110 10:04:01 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 2161110 10:04:01 [Warning] Using unique option prefix thread_cache instead of thread_cache_size is deprecated and will be removed in a future release. Please use the full name instead. 3161110 10:04:01 [Note] /usr/libexec/mysqld (mysqld 5.5.47-log) starting as process 6785 ... 4161110 10:04:01 [Note] Plugin 'FEDERATED' is disabled. 5161110 10:04:01 InnoDB: The InnoDB memory heap is disabled 6161110 10:04:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins 7161110 10:04:01 InnoDB: Compressed tables use zlib 1.2.3 8161110 10:04:01 InnoDB: Using Linux native AIO 9161110 10:04:01 InnoDB: Initializing buffer pool, size = 1000.0M 10161110 10:04:01 InnoDB: Completed initialization of buffer pool 11161110 10:04:01 InnoDB: highest supported file format is Barracuda. 12InnoDB: The log sequence number in ibdata files does not match 13InnoDB: the log sequence number in the ib_logfiles! 14161110 10:04:01 InnoDB: Database was not shut down normally! 15InnoDB: Starting crash recovery. 16InnoDB: Reading tablespace information from the .ibd files... 17InnoDB: Restoring possible half-written data pages from the doublewrite 18InnoDB: buffer... 19InnoDB: Last MySQL binlog file position 0 1065103915, file name ./mysql-bin.002966 20161110 10:04:01 InnoDB: Waiting for the background threads to start 21161110 10:04:02 InnoDB: 5.5.47 started; log sequence number 6110248889894 2201:04:02 UTC - mysqld got signal 11 ; 23This could be because you hit a bug. It is also possible that this binary 24or one of the libraries it was linked against is corrupt, improperly built, 25or misconfigured. This error can also be caused by malfunctioning hardware. 26We will try our best to scrape up some info that will hopefully help 27diagnose the problem, but since we have already crashed, 28something is definitely wrong and this may fail. 29 30key_buffer_size=8388608 31read_buffer_size=131072 32max_used_connections=0 33max_threads=2000 34thread_count=0 35connection_count=0 36It is possible that mysqld could use up to 37key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4383254 K bytes of memory 38Hope that's ok; if not, decrease some variables in the equation. 39 40Thread pointer: 0x0 41Attempting backtrace. You can use the following information to find out 42where mysqld died. If you see no messages after this, something went 43terribly wrong... 44stack_bottom = 0 thread_stack 0x40000 45/usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x78e06e] 46/usr/libexec/mysqld(handle_fatal_signal+0x493)[0x6765d3] 47/lib64/libpthread.so.0[0x3a1d40f710] 48The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains 49information that should help you find out what is causing the crash. 50161110 10:04:02 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
エラー内容を元に検索してみたのですが、キーワードが悪いのか
解決に至るような事例にたどり着けませんでした。
なお、my.cnfの設定は以下のようになっており、
サーバの再起動前は特に問題なく動いておりました。
Bash
1[mysqld] 2datadir=/var/lib/mysql 3socket=/var/lib/mysql/mysql.sock 4 5symbolic-links=0 6character-set-server = utf8 7 8user=mysql 9 10max_connections = 2000 11thread_cache = 600 12thread_cache_size = 50 13table_open_cache = 512 14wait_timeout = 300 15max_connect_errors = 10000 16query_cache_type = 0 17query_cache_size = 0 18tmp_table_size = 1024M 19max_heap_table_size = 1024M 20innodb_buffer_pool_size = 1000M 21 22slow_query_log=1 23slow_query_log_file=mysql-slow.log 24long_query_time=10 25 26log-bin=mysql-bin 27expire_logs_days=3 28 29[mysqld_safe] 30log-error=/var/log/mysqld.log 31pid-file=/var/run/mysqld/mysqld.pid
つきましては、何か解決のヒントになるようなことがございましたら、
ご教授いただけると助かります。
それでは、よろしくお願いいたします。
回答3件
あなたの回答
tips
プレビュー
バッドをするには、ログインかつ
こちらの条件を満たす必要があります。
2016/11/10 09:05
2016/11/10 12:11
2016/11/10 13:28