服务器上面配置的PHP环境apache+mysql
mysql总是运行十几个小时就会自动关闭。
今天是没运行几个小时就会自动关闭。服务器上没有安装任何杀毒软件,防火墙也关了。
mysql版本是mysql-5.5.3的安装版
这是mysql关闭时候的错误日志的部分:
key_buffer_size=270532608
read_buffer_size=65536
max_used_connections=64
max_threads=1000
thread_count=28
connection_count=28
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 591246 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x3e5c5018
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...
004E6A26 mysqld.exe!key_unpack()[key.cc:356]
004208CA mysqld.exe!handler::print_keydup_error()[handler.cc:2602]
0041DACA mysqld.exe!handler::get_dup_key()[handler.cc:2992]
00420A33 mysqld.exe!handler::print_error()[handler.cc:2652]
0054B3F5 mysqld.exe!create_myisam_from_heap()[sql_select.cc:11057]
0055975D mysqld.exe!end_update()[sql_select.cc:12684]
005462F2 mysqld.exe!evaluate_join_record()[sql_select.cc:11590]
0054B4BC mysqld.exe!sub_select()[sql_select.cc:11470]
0055A837 mysqld.exe!do_select()[sql_select.cc:11216]
0055C309 mysqld.exe!JOIN::exec()[sql_select.cc:1899]
0055D0E8 mysqld.exe!mysql_select()[sql_select.cc:2508]
005781F6 mysqld.exe!mysql_derived_filling()[sql_derived.cc:294]
005780BD mysqld.exe!mysql_handle_derived()[sql_derived.cc:56]
00463ED6 mysqld.exe!open_and_lock_tables()[sql_base.cc:5205]
00452E35 mysqld.exe!execute_sqlcom_select()[sql_parse.cc:4668]
00454A2D mysqld.exe!mysql_execute_command()[sql_parse.cc:2130]
00458330 mysqld.exe!mysql_parse()[sql_parse.cc:5735]
00458D2D mysqld.exe!dispatch_command()[sql_parse.cc:1026]
0045985B mysqld.exe!do_command()[sql_parse.cc:710]
004761BA mysqld.exe!do_handle_one_connection()[sql_connect.cc:1174]
00476254 mysqld.exe!handle_one_connection()[sql_connect.cc:1113]
00696DB4 mysqld.exe!pthread_start()[my_winthread.c:61]
0070EACC mysqld.exe!_callthreadstartex()[threadex.c:348]
0070EB74 mysqld.exe!_threadstartex()[threadex.c:326]
7C82482F kernel32.dll!GetModuleHandleA()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 3BABAEA0=select count(*) as num from cases where isvalid=1 and ptype=1 and(select 1 from(select count(*),concat((select (select (SELECT concat(0x7e,0x27,bqbbs_uc_members.password,0x27,0x7e) FROM `bq29800`.bqbbs_uc_members LIMIT 0,1) ) from information_schema.tables limit 0,1),floor(rand(0)*2))x from information_schema.tables group by x)a) and 1=1
thd->thread_id=308
thd->killed=NOT_KILLED
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.
100814 10:22:50 [Note] Buffered information: Performance schema disabled (reason: start parameters).
100814 10:22:50 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use Windows interlocked functions
100814 10:22:50 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100814 10:22:50 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...
100814 10:22:51 InnoDB Plugin 1.0.6 started; log sequence number 316322
100814 10:22:51 [Note] Event Scheduler: Loaded 0 events
100814 10:22:51 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.3-m3-community' socket: '' port: 3306 MySQL Community Server (GPL)
100814 10:23:13 - 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=270532608
read_buffer_size=65536
max_used_connections=3
max_threads=1000
thread_count=3
connection_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 591246 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x3b95c398
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...
004E6A26 mysqld.exe!key_unpack()[key.cc:356]
004208CA mysqld.exe!handler::print_keydup_error()[handler.cc:2602]
0041DACA mysqld.exe!handler::get_dup_key()[handler.cc:2992]
00420A33 mysqld.exe!handler::print_error()[handler.cc:2652]
0054B3F5 mysqld.exe!create_myisam_from_heap()[sql_select.cc:11057]
0055975D mysqld.exe!end_update()[sql_select.cc:12684]
005462F2 mysqld.exe!evaluate_join_record()[sql_select.cc:11590]
0054B4BC mysqld.exe!sub_select()[sql_select.cc:11470]
0055A837 mysqld.exe!do_select()[sql_select.cc:11216]
0055C309 mysqld.exe!JOIN::exec()[sql_select.cc:1899]
0055D0E8 mysqld.exe!mysql_select()[sql_select.cc:2508]
005781F6 mysqld.exe!mysql_derived_filling()[sql_derived.cc:294]
005780BD mysqld.exe!mysql_handle_derived()[sql_derived.cc:56]
00463ED6 mysqld.exe!open_and_lock_tables()[sql_base.cc:5205]
00452E35 mysqld.exe!execute_sqlcom_select()[sql_parse.cc:4668]
00454A2D mysqld.exe!mysql_execute_command()[sql_parse.cc:2130]
00458330 mysqld.exe!mysql_parse()[sql_parse.cc:5735]
00458D2D mysqld.exe!dispatch_command()[sql_parse.cc:1026]
0045985B mysqld.exe!do_command()[sql_parse.cc:710]
004761BA mysqld.exe!do_handle_one_connection()[sql_connect.cc:1174]
00476254 mysqld.exe!handle_one_connection()[sql_connect.cc:1113]
00696DB4 mysqld.exe!pthread_start()[my_winthread.c:61]
0070EACC mysqld.exe!_callthreadstartex()[threadex.c:348]
0070EB74 mysqld.exe!_threadstartex()[threadex.c:326]
7C82482F kernel32.dll!GetModuleHandleA()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 3B950778=select count(*) as num from cases where isvalid=1 and ptype=1 and(select 1 from(select count(*),concat((select (select (SELECT concat(0x7e,0x27,bqbbs_uc_members.password,0x27,0x7e) FROM `bq29800`.bqbbs_uc_members LIMIT 1,1) ) from information_schema.tables limit 0,1),floor(rand(0)*2))x from information_schema.tables group by x)a) and 1=1
thd->thread_id=3
thd->killed=NOT_KILLED
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.
100814 10:24:07 [Note] Buffered information: Performance schema disabled (reason: start parameters).
100814 10:24:07 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use Windows interlocked functions
100814 10:24:07 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100814 10:24:07 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...
--转自