57,064
社区成员
发帖
与我相关
我的任务
分享mysql服务无法启动，1067错误
安装完mysql之后，服务启动不了，显示“在本地计算机无法启动MYSQL服务，错误1067：进程意外中止”，我搜了好多资料，都说是my.ini配置文件的错误，但是路径是对的，望各位大侠帮帮忙！
...全文
请发表友善的回复…
发表回复
zalvsa 2011-08-12
- 打赏
- 举报
结贴率好凄惨……
http://topic.csdn.net/u/20110812/10/26eddfa2-692a-4ad0-8936-68514f77ed7e.html?seed=1457855748&r=74920830#r_74920830
http://topic.csdn.net/u/20110812/10/26eddfa2-692a-4ad0-8936-68514f77ed7e.html?seed=1457855748&r=74920830#r_74920830
呆到深处自然萌2 2011-08-12
- 打赏
- 举报
[Quote=引用 6 楼 acmain_chm 的回复:]
最好贴全一些。
仅从上述信息看，是innodb 的数据文件损坏，一般来说，直接删除ibdata1, ib_logfile0, .. 等innodb的文件，让MYSQL自动重建即可。
[/Quote]恩 今天遇到过 服务启不动 删了就ok啦
最好贴全一些。
仅从上述信息看，是innodb 的数据文件损坏，一般来说，直接删除ibdata1, ib_logfile0, .. 等innodb的文件，让MYSQL自动重建即可。
[/Quote]恩 今天遇到过 服务启不动 删了就ok啦
haojianfeng11 2011-05-14
- 打赏
- 举报
[Quote=引用 6 楼 acmain_chm 的回复:]
最好贴全一些。
仅从上述信息看，是innodb 的数据文件损坏，一般来说，直接删除ibdata1, ib_logfile0, .. 等innodb的文件，让MYSQL自动重建即可。
[/Quote]解决了
最好贴全一些。
仅从上述信息看，是innodb 的数据文件损坏，一般来说，直接删除ibdata1, ib_logfile0, .. 等innodb的文件，让MYSQL自动重建即可。
[/Quote]解决了
fsh2008 2010-07-12
- 打赏
- 举报
[Quote=引用 8 楼 acmain_chm 的回复:]
引用直接删除ibdata1, ib_logfile0, .. 等innodb的文件
[/Quote]
非常感谢, 我找了好久关于这个错误的方法, 网上搜的都不管用, 删除后问题解决了.
引用直接删除ibdata1, ib_logfile0, .. 等innodb的文件
[/Quote]
非常感谢, 我找了好久关于这个错误的方法, 网上搜的都不管用, 删除后问题解决了.
ACMAIN_CHM 2010-03-17
- 打赏
- 举报
你不是新安装的MYSQL吗？里面哪儿来的表？
wasj9999 2010-03-17
- 打赏
- 举报
可是删了之后会不会里面的表不能用了？我已经删了，服务是启动了，可是里面的表不能用了。
ACMAIN_CHM 2010-03-17
- 打赏
- 举报
[Quote]直接删除ibdata1, ib_logfile0, .. 等innodb的文件[/Quote]
wasj9999 2010-03-17
- 打赏
- 举报
100316 20:37:27 InnoDB: Page checksum 198097117, prior-to-4.0.14-form checksum 635963325
InnoDB: stored checksum 402310877, prior-to-4.0.14-form stored checksum 635963325
InnoDB: Page lsn 0 113125904, low 4 bytes of lsn at page end 113125904
InnoDB: Page number (if stored to page already) 2,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an 'inode' page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100316 20:54:31 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...
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2.
InnoDB: You may have to recover from a backup.
这次全了不？
InnoDB: stored checksum 402310877, prior-to-4.0.14-form stored checksum 635963325
InnoDB: Page lsn 0 113125904, low 4 bytes of lsn at page end 113125904
InnoDB: Page number (if stored to page already) 2,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an 'inode' page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100316 20:54:31 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...
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2.
InnoDB: You may have to recover from a backup.
这次全了不？
ACMAIN_CHM 2010-03-17
- 打赏
- 举报
最好贴全一些。
仅从上述信息看，是innodb 的数据文件损坏，一般来说，直接删除ibdata1, ib_logfile0, .. 等innodb的文件，让MYSQL自动重建即可。
仅从上述信息看，是innodb 的数据文件损坏，一般来说，直接删除ibdata1, ib_logfile0, .. 等innodb的文件，让MYSQL自动重建即可。
wasj9999 2010-03-17
- 打赏
- 举报
日志内容中有这些信息：
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
是不是数据库文件损坏了？
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
是不是数据库文件损坏了？
ACMAIN_CHM 2010-03-17
- 打赏
- 举报
直接用记事本打开。
wasj9999 2010-03-17
- 打赏
- 举报
my.ini文件没有指定error-log路径，默认生成了一个主机名.err文件，但是无法看里面的内容
ACMAIN_CHM 2010-03-17
- 打赏
- 举报
到MySQL错误日志中看一下具体的错误信息。
wwwwb 2010-03-17
- 打赏
- 举报
你的INI内容是什么？有无ERRLOG
ACMAIN_CHM 2010-03-17
- 打赏
- 举报
1. 你原来安装的MYSQL本身没有任何问题。
2. 问题出在你的数据库表文件上。
2. 问题出在你的数据库表文件上。
wasj9999 2010-03-17
- 打赏
- 举报
我自己下载了一个MYSQL,在my.ini中配置datadir=哪个安装抱中的数据文件，出现如下错误：
InnoDB: Error: log file .\ib_logfile0 is of different size 0 5242880 bytes
InnoDB: than specified in the .cnf file 0 10485760 bytes!
100317 16:55:31 [ERROR] Plugin 'InnoDB' init function returned error.
100317 16:55:31 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
100317 16:55:31 [ERROR] Unknown/unsupported table type: INNODB
100317 16:55:31 [ERROR] Aborting
100317 16:55:31 [Warning] Forcing shutdown of 1 plugins
100317 16:55:31 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete
InnoDB: Error: log file .\ib_logfile0 is of different size 0 5242880 bytes
InnoDB: than specified in the .cnf file 0 10485760 bytes!
100317 16:55:31 [ERROR] Plugin 'InnoDB' init function returned error.
100317 16:55:31 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
100317 16:55:31 [ERROR] Unknown/unsupported table type: INNODB
100317 16:55:31 [ERROR] Aborting
100317 16:55:31 [Warning] Forcing shutdown of 1 plugins
100317 16:55:31 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete
ACMAIN_CHM 2010-03-17
- 打赏
- 举报
很显然，你的安装包中的数据文件有问题。
重新安装一下试试运气。如果不行，就需要找开发者了。
重新安装一下试试运气。如果不行，就需要找开发者了。
wasj9999 2010-03-17
- 打赏
- 举报
这个不是单独的mysql安装，是集成在一个安装包中的，其中有一步就是安装数据库，既包括mysql也包括里面的表和索引等。
