MySQL数据库意外停止,每天都要重启,求解决
pooq 2014-06-04 10:25:04 贴一下MySQL里面的.err文件,从文件看估计是病毒造成,不知如何根除?下面加粗部分都是被病毒工具查出的病毒!
140529 10:40:38 [Note] Plugin 'FEDERATED' is disabled.
140529 10:40:38 [Note] Plugin 'InnoDB' is disabled.
140529 10:40:38 [Note] Event Scheduler: Loaded 0 events
140529 10:40:38 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
Version: '5.1.52-community' socket: '' port: 3306 MySQL Community Server (GPL)
140529 16:50:54 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Normal shutdown
140529 16:50:54 [Note] Event Scheduler: Purging the queue. 0 events
140529 16:50:56 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Forcing close of thread 12157 user: 'root'
140529 16:50:56 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Forcing close of thread 12053 user: 'root'
140529 16:50:56 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete
140529 16:53:24 [Note] Plugin 'FEDERATED' is disabled.
140529 16:53:24 [Note] Plugin 'InnoDB' is disabled.
140529 16:53:25 [Note] Event Scheduler: Loaded 0 events
140529 16:53:25 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
Version: '5.1.52-community' socket: '' port: 3306 MySQL Community Server (GPL)
140529 23:02:35 - 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=201326592
read_buffer_size=65536
max_used_connections=5
max_threads=1510
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 689493 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x11a4b330
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...
7C93ED80 ntdll.dll!RtlUpperChar()
113B14F2 tsgno.dll!ShellExe_deinit()
113B1101 tsgno.dll!ShellExe_deinit()
E58CBCEF
007C7390 mysqld.exe!order()
C7084E8D
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 1194D018=select ShellExe('C:/WINDOWS/system32/wemote.dll')
thd->thread_id=1408
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.
140530 9:35:12 [Note] Plugin 'FEDERATED' is disabled.
140530 9:35:12 [Note] Plugin 'InnoDB' is disabled.
140530 9:35:12 [Note] Event Scheduler: Loaded 0 events
140530 9:35:12 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
Version: '5.1.52-community' socket: '' port: 3306 MySQL Community Server (GPL)
140602 23:11:14 - 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=201326592
read_buffer_size=65536
max_used_connections=13
max_threads=1510
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 689493 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x1196e940
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...
7C93ED80 ntdll.dll!RtlUpperChar()
113B14F2 tsgno.dll!ShellExe_deinit()
113B1101 tsgno.dll!ShellExe_deinit()
80E68101
007C7390 mysqld.exe!order()
C7084E8D
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 11939BC8=select ShellExe('C:/WINDOWS/system32/Server.exe')
thd->thread_id=25018
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.
140603 8:07:32 [Note] Plugin 'FEDERATED' is disabled.
140603 8:07:32 [Note] Plugin 'InnoDB' is disabled.
140603 8:07:33 [Note] Event Scheduler: Loaded 0 events
140603 8:07:33 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
Version: '5.1.52-community' socket: '' port: 3306 MySQL Community Server (GPL)
140604 8:09:39 - 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=201326592
read_buffer_size=65536
max_used_connections=9
max_threads=1510
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 689493 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x11d0bf38
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...
7C93ED80 ntdll.dll!RtlUpperChar()
113B14F2 tsgno.dll!ShellExe_deinit()
113B1101 tsgno.dll!ShellExe_deinit()
A988E59F
007C7390 mysqld.exe!order()
C7084E8D
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 11CDE018=select ShellExe('C:/WINDOWS/system32/1234.exe')
thd->thread_id=8562
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.
140604 9:08:52 [Note] Plugin 'FEDERATED' is disabled.
140604 9:08:52 [Note] Plugin 'InnoDB' is disabled.
140604 9:08:53 [Note] Event Scheduler: Loaded 0 events
140604 9:08:53 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
Version: '5.1.52-community' socket: '' port: 3306 MySQL Community Server (GPL)