我在虚拟机上装了个mysql ,每次都可以启动, 可是每次我使用客户端连接或者在程序中操作数据库时,过一会儿数据库就挂掉了(select是可以的,update就会挂掉)。
我每次重启都提示我mysql-nt.exe 错误,发送错误报告。
后来我以为是数据库问题,我就重装了数据库,我卸载了原有的数据库后重启,还是提示“mysql-nt.exe 错误,发送错误报告。”。最后我重装了,还是出现这个问题。虚拟机的操作系统是:Windows server 2003 R2请大家指点,多谢。
我每次重启都提示我mysql-nt.exe 错误,发送错误报告。
后来我以为是数据库问题,我就重装了数据库,我卸载了原有的数据库后重启,还是提示“mysql-nt.exe 错误,发送错误报告。”。最后我重装了,还是出现这个问题。虚拟机的操作系统是:Windows server 2003 R2请大家指点,多谢。
顺便把errorlog中的相关内容帖出来看看吧
谢谢大家,
mysql版本是:5.0.22-community-nt
日志文件怎么查看
下面会列出来LOG_ERROR的路径
日志文件是:100629 11:03:16 InnoDB: Error: page 9537 log sequence number 0 490242730
InnoDB: is in the future! Current system log sequence number 0 6727496.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
100629 11:03:16 InnoDB: Error: page 9278 log sequence number 0 490242534
InnoDB: is in the future! Current system log sequence number 0 6727496.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
100629 11:03:16 InnoDB: Error: page 9081 log sequence number 0 490242528
InnoDB: is in the future! Current system log sequence number 0 6727496.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
100629 11:03:16 InnoDB: Error: page 12818 log sequence number 0 481960178
InnoDB: is in the future! Current system log sequence number 0 6727496.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
100629 11:03:16 InnoDB: Error: page 11145 log sequence number 0 2473092250
InnoDB: is in the future! Current system log sequence number 0 6727496.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
100629 11:03:16 InnoDB: Error: page 9524 log sequence number 0 3231331048
InnoDB: is in the future! Current system log sequence number 0 6727496.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
100629 11:03:16 InnoDB: Error: page 14843 log sequence number 0 3237589901
InnoDB: is in the future! Current system log sequence number 0 6727496.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
100629 11:03:16 InnoDB: Error: page 11148 log sequence number 0 3237582677
InnoDB: is in the future! Current system log sequence number 0 6727496.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
100629 11:03:16 InnoDB: Error: page 11147 log sequence number 0 3237575756
InnoDB: is in the future! Current system log sequence number 0 6727496.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
100629 11:03:16 InnoDB: Error: page 11146 log sequence number 0 3237567812
InnoDB: is in the future! Current system log sequence number 0 6727496.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
100629 11:03:16 InnoDB: Error: page 19289 log sequence number 0 3237592249
InnoDB: is in the future! Current system log sequence number 0 6727496.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
100629 11:03:32 InnoDB: Error: page 41422 log sequence number 0 3237592630
InnoDB: is in the future! Current system log sequence number 0 6727506.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
100629 11:03:32 InnoDB: Error: page 131072 log sequence number 0 3237592630
InnoDB: is in the future! Current system log sequence number 0 6727506.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
len 1000; hex 00000004aaaaaaaaeaffffffffffffffffffffff000000000000351......中间有很多,我将其省略了2220 in file .\fsp\fsp0fsp.c line 1431
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
望大家多帮忙,多谢