MySql服务启动不了...急

freedragonle 2012-04-09 09:17:29
以前一直没问题..突然提示:
Can't connect to MySQL server on 'localhost' (10061)
服务再也启动不了了
把my.ini里的datadir换了一个地址可用....但是怎么把以前位置的数据库转移过来？
貌似问题在ibdeta1这个文件上。。一指向原来的就不行....
...全文
145 13 打赏 收藏 转发到动态 举报
写回复
用AI写文章
13 条回复
切换为时间正序
请发表友善的回复…
发表回复
jastdoit 2012-04-12
  • 打赏
  • 举报
 回复
文件被损坏
zhiyuanzheliuzhaojun 2012-04-11
  • 打赏
  • 举报
 回复
没遇见过
Rotel-刘志东 2012-04-10
  • 打赏
  • 举报
 回复
数据库损坏了，关键中间做什么操作了。
wwwwb 2012-04-10
  • 打赏
  • 举报
 回复
试试：
[mysqld]
innodb_force_recovery = 4(1-6都试试)
iihero_ 2012-04-10
  • 打赏
  • 举报
 回复
[Quote=引用 8 楼 的回复:]

问题是什么操作都没有...正在往数据库里录入数据突然就服务停止了...再也启动不了了...目前只好重做数据库了...
[/Quote]
如果只有这个录入来访问，应该不会有太大问题，会不会中间有别的会话进行误操作。....
可能性太多了。
yq510457 2012-04-10
  • 打赏
  • 举报
 回复
是不是数据不同步造成的呢？
重新导入导出试试……
freedragonle 2012-04-10
  • 打赏
  • 举报
 回复
问题是什么操作都没有...正在往数据库里录入数据突然就服务停止了...再也启动不了了...目前只好重做数据库了...
wwwwb 2012-04-10
  • 打赏
  • 举报
 回复
如果不是直接COPY的数据文件，估计是数据库损坏
珠海-天堂 2012-04-10
  • 打赏
  • 举报
 回复 


Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files.


看看这个。
freedragonle 2012-04-09
  • 打赏
  • 举报
 回复
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 341 log sequence number 2589992
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 470 log sequence number 2590246
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 416 log sequence number 2590572
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 222 log sequence number 2591182
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 418 log sequence number 2591182
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 508 log sequence number 2591182
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 471 log sequence number 2591582
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 226 log sequence number 2592176
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 422 log sequence number 2592176
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 426 log sequence number 2592176
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 399 log sequence number 2601032
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 344 log sequence number 2602932
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 235 log sequence number 2603379
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 434 log sequence number 2603379
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 493 log sequence number 2603379
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 236 log sequence number 2604504
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 592 log sequence number 2604504
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 237 log sequence number 2606065
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 435 log sequence number 2606065
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 239 log sequence number 2607999
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:26 InnoDB: Error: page 367 log sequence number 2607999
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:27 InnoDB: Error: page 249 log sequence number 2610459
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:27 InnoDB: Error: page 466 log sequence number 2610459
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:27 InnoDB: Error: page 272 log sequence number 2612054
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:27 InnoDB: Error: page 318 log sequence number 2612054
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:27 InnoDB: Error: page 274 log sequence number 2613709
InnoDB: is in the future! Current system log sequence number 2587660.
freedragonle 2012-04-09
  • 打赏
  • 举报
 回复
120409 23:53:22 [Note] Plugin 'FEDERATED' is disabled.
120409 23:53:22 InnoDB: The InnoDB memory heap is disabled
120409 23:53:22 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120409 23:53:22 InnoDB: Compressed tables use zlib 1.2.3
120409 23:53:22 InnoDB: Initializing buffer pool, size = 47.0M
120409 23:53:22 InnoDB: Completed initialization of buffer pool
120409 23:53:23 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!
120409 23:53:23 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...
120409 23:53:24 InnoDB: Error: page 7 log sequence number 2599620
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:24 InnoDB: Error: page 1 log sequence number 2599809
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:24 InnoDB: Error: page 11 log sequence number 2606126
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:24 InnoDB: Error: page 46 log sequence number 2595814
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:24 InnoDB: Error: page 459 log sequence number 2595814
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 194 log sequence number 2587708
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 457 log sequence number 2587708
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 197 log sequence number 2588333
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 425 log sequence number 2588333
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 454 log sequence number 2588333
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 337 log sequence number 2588751
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 334 log sequence number 2589063
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 413 log sequence number 2589297
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 467 log sequence number 2589515
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
120409 23:53:25 InnoDB: Error: page 507 log sequence number 2589753
InnoDB: is in the future! Current system log sequence number 2587660.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

freedragonle 2012-04-09
  • 打赏
  • 举报
 回复
这个..
InnoDB: Error: trying to access tablespace 3085274529 page no. 3837493288,
InnoDB: but the tablespace does not exist or is just being dropped.
rucypli 2012-04-09
  • 打赏
  • 举报
 回复
看看原datadir目录里面的err文件有什么报错信息,估计是文件损坏
80端口被占用导致Apache启动失败怎么解决
Apache启动不了，电脑80端口被占有如何解决 问题如下： 1. 80端口被占用，Apache启动失败。√MySQL5.1已启动。2.Apache启动不了，80端口被httpd.exe占用~急！！ 我们用电脑做服务器时，我们通常要配置环境，当我们在配置服务器的时候，经常需要用到一些端口，而经常要用到的就是80端口了，但往往都会出现被占有，在这里跟大家分享一下，电脑80端口被占有应该怎样解决。 环境：win xp系统 win7系统 解决办法： 1.首先按win+R打开运行，然后输入CMD 2.在里面输入命令netstat -aon，之后就会显示哪些程序占用了80端口 3.找到80端口（
MySQL无法启动的问题-＞MySQL 服务正在启动 . MySQL 服务无法启动。服务没有报告任何错误。 请键入 NET HELPMSG 3534 以获得更多的帮助。
今天安装了MySQL，卡在了一个问题上卡了很久，始终没有解决好。 如图： 强迫症的我，急死。吃过晚饭继续折腾，心想着必须解决这个问题！ 原先我是按照网上的步骤一步一步下载、安装MySQL，结果就是上面的图。经过我查资料，网上搜集了一大批解决的教程，诸如什么运行mysqld --console查看运行日志，结果还是上图。 经过我一波尝试之后，我最后的解决办法是这样的： 把网上安装教程的配置文件my.ini文件放置在bin目录下，重新在命令行运行net start mysql即可成功启动MySQL： 我看别
MySQL无法启动的问题->MySQL 服务正在启动 . MySQL 服务无法启动。服务没有报告任何错误。 请键入 NET HELPMSG 3534 以获得更多的帮助。
今天安装了MySQL，卡在了一个问题上卡了很久，始终没有解决好。 如图： 强迫症的我，急死。吃过晚饭继续折腾，心想着必须解决这个问题！ 原先我是按照网上的步骤一步一步下载、安装MySQL，结果就是上面的图。经过我查资料，网上搜集了一大批解决的教程，诸如什么运行mysqld --console查看运行日志，结果还是上图。 经过我一波尝试之后，我最后的解决办法是这样的： 把网上安装...
mysql开机跳出更新_mysql 启动出现问题.急等解决办法.
你的位置:问答吧-> 数据库-> 问题详情mysql 启动出现问题.急等解决办法.ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)作者: zwangxi...
mysql8.0服务没有报告任何错误_win10启动mysql-8.0.13时报错：MySQL 服务正在启动 .. MySQL 服务无法启动。 服务没有报告任何错误。 请键入 NET...
先看报错：环境变量：(请忽略那些不厚道的马赛克)my.ini文件第一个：(第一次用的没成功)[mysql]# 设置mysql客户端默认字符集default-character-set=utf8[mysqld]#设置3306端口port = 3306# 设置mysql的安装目录basedir=F:\mysql-8.0.13-winx64# 设置mysql数据库的数据的存放目录datadir=F:\m...
MySQL

56,677

社区成员

56,708

社区内容

发帖
与我相关
我的任务
社区描述
MySQL相关内容讨论专区
社区管理员
  • MySQL
加入社区
  • 近7日
  • 近30日
  • 至今

加载中

查看更多榜单
社区公告
暂无公告

试试用AI创作助手写篇文章吧

+ 用AI写文章