じょもらな日々

電脳硬化症気味な日記です。まとまった情報は wiki にあります。

2009.6.17 (Wednesday)

at 20:54  

自宅サーバのMySQLがダウン!   [わたくしごと]

 先日のVirus騒ぎに引き続き、今度はMySQL 5.0.83が異常停止しました。その影響で、Apache 2.2のerror.logもかなり肥大化。全てのWebアクセスに対してエラーが出力されてるからです。
 原因は不明。う~む。帰宅して、MySQLのWindowsサービスを起動したら、正常に起動するし。

 以下、MySQLのerror.log

090617 13:29:27 - mysqld got exception 0xc0000005 ;
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=134217728
read_buffer_size=131072
max_used_connections=5
max_connections=100
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 348671 K
bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.

thd=0325CDF0
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…
0063847B mysqld-nt.exe!my_hash_sort_bin()[ctype-bin.c:307]
005ED5F1 mysqld-nt.exe!rec_hashnr()[hash.c:184]
005ED9DA mysqld-nt.exe!hash_delete()[hash.c:483]
00515A2A mysqld-nt.exe!Query_cache::free_old_query()[sql_cache.cc:2023]
005166E3 mysqld-nt.exe!Query_cache::allocate_data_chain()[sql_cache.cc:2374]
00516C17 mysqld-nt.exe!Query_cache::write_result_data()[sql_cache.cc:2278]
00517577 mysqld-nt.exe!Query_cache::append_result_data()[sql_cache.cc:2196]
00517718 mysqld-nt.exe!query_cache_insert()[sql_cache.cc:684]
004BD32D mysqld-nt.exe!net_real_write()[net_serv.cc:571]
004BDACB mysqld-nt.exe!net_flush()[net_serv.cc:347]
004D2445 mysqld-nt.exe!send_eof()[protocol.cc:352]
005180C0 mysqld-nt.exe!select_send::send_eof()[sql_class.cc:1108]
005679A4 mysqld-nt.exe!do_select()[sql_select.cc:10524]
00568A6F mysqld-nt.exe!JOIN::exec()[sql_select.cc:2125]
005690C4 mysqld-nt.exe!mysql_select()[sql_select.cc:2313]
0056950B mysqld-nt.exe!handle_select()[sql_select.cc:256]
0053B042 mysqld-nt.exe!mysql_execute_command()[sql_parse.cc:2880]
00541F41 mysqld-nt.exe!mysql_parse()[sql_parse.cc:6441]
00542F4E mysqld-nt.exe!dispatch_command()[sql_parse.cc:1963]
00544236 mysqld-nt.exe!do_command()[sql_parse.cc:1646]
00544555 mysqld-nt.exe!handle_one_connection()[sql_parse.cc:1234]
005F5D9B mysqld-nt.exe!pthread_start()[my_winthread.c:85]
006E123F mysqld-nt.exe!_threadstart()[thread.c:196]
7C80B729 kernel32.dll!GetModuleFileNameA()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort…
thd->query at 03266018=SELECT DISTINCT * FROM wp_posts WHERE 1=1 AND post_date < = ‘2009-06-17 13:29:27′ AND post_category > 0 AND (post_status = ‘publish’) ORDER BY post_date DESC LIMIT 15
thd->thread_id=2120
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.
InnoDB: Log scan progressed past the checkpoint lsn 0 95234970


« ツイテナイ …orz… Clip to Evernote
log4net RemotingA… »
  trackback:    



Go back.