MYSQL 服务自动停止

liveplus 2010-06-09 04:07:49
昨天mysql原来存放数据的磁盘没有空间了，就把数据文件全部copy到一个大容量的磁盘上面，
修改完配置；重启服务后，服务没过一段时间就被自动停掉，不知道什么原因，请高人指点，
下面是错误日志文件的一段信息。

InnoDB: log sequence number 412 456343084.
InnoDB: Doing recovery: scanned up to log sequence number 412 461585920
InnoDB: Doing recovery: scanned up to log sequence number 412 466828800
InnoDB: Doing recovery: scanned up to log sequence number 412 472071680
InnoDB: Doing recovery: scanned up to log sequence number 412 477314560
InnoDB: Doing recovery: scanned up to log sequence number 412 481998366
100609 15:33:23 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
100609 15:33:25 InnoDB: Started; log sequence number 412 481998366
100609 15:33:25 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
100609 15:35:20 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...
100609 15:35:20 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 412 482108120.
InnoDB: Doing recovery: scanned up to log sequence number 412 482108120
100609 15:35:20 InnoDB: Started; log sequence number 412 482108120
100609 15:35:20 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
100609 15:38:20 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...
100609 15:38:20 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 412 482108130.
InnoDB: Doing recovery: scanned up to log sequence number 412 482108130
100609 15:38:20 InnoDB: Started; log sequence number 412 482108130
100609 15:38:20 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
100609 15:41:27 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...
100609 15:41:28 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 412 482117079.
InnoDB: Doing recovery: scanned up to log sequence number 412 482117079
100609 15:41:28 InnoDB: Started; log sequence number 412 482117079
100609 15:41:28 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
100609 15:44:20 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...
100609 15:44:20 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 412 547322718.
InnoDB: Doing recovery: scanned up to log sequence number 412 547322718
100609 15:44:20 InnoDB: Started; log sequence number 412 547322718
100609 15:44:20 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
100609 15:47: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...
100609 15:47:32 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 412 547322728.
InnoDB: Doing recovery: scanned up to log sequence number 412 547322728
100609 15:47:32 InnoDB: Started; log sequence number 412 547322728
100609 15:47:32 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
100609 15:50:52 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...
100609 15:50:52 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 412 547322738.
InnoDB: Doing recovery: scanned up to log sequence number 412 547322738
100609 15:50:53 InnoDB: Started; log sequence number 412 547322738
100609 15:50:53 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
100609 15:53:20 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...
100609 15:53:20 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 412 554202186.
InnoDB: Doing recovery: scanned up to log sequence number 412 554202186
100609 15:53:20 InnoDB: Started; log sequence number 412 554202186
100609 15:53:20 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
100609 15:56:20 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...
100609 15:56:20 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 412 554232119.
InnoDB: Doing recovery: scanned up to log sequence number 412 554232119
100609 15:56:20 InnoDB: Started; log sequence number 412 554232119
100609 15:56:20 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
100609 15:59:20 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...
100609 15:59:20 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 412 624944384.
InnoDB: Doing recovery: scanned up to log sequence number 412 624944384
100609 15:59:20 InnoDB: Started; log sequence number 412 624944384
100609 15:59:20 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
100609 16:02:36 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...
100609 16:02:36 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 412 624944394.
InnoDB: Doing recovery: scanned up to log sequence number 412 624944394
100609 16:02:37 InnoDB: Started; log sequence number 412 624944394
100609 16:02:37 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
100609 16:05:34 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...
100609 16:05:35 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 412 624944394.
InnoDB: Doing recovery: scanned up to log sequence number 412 624944404
100609 16:05:35 InnoDB: Started; log sequence number 412 624944404
100609 16:05:35 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
...全文
986 4 打赏 收藏 转发到动态 举报
写回复
用AI写文章
4 条回复
切换为时间正序
请发表友善的回复…
发表回复
littleline 2010-06-10
  • 打赏
  • 举报
 回复
换个干净的环境试试，一样一样慢慢排查！
jiahehao 2010-06-10
  • 打赏
  • 举报
 回复
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
100609 15:35:20 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 412 482108120.
****************************************************

数据有冲突，系统试图从上一个检查点恢复。。。。。
我估计楼主是真正的"copy"，记得下回要用“mysqldump”。
ACMAIN_CHM 2010-06-09
  • 打赏
  • 举报
 回复
100609 15:38:20 InnoDB: Database was not shut down normally!


检查一下你的文件是否损坏，另外检查一下你的杀毒软件。
iihero_ 2010-06-09
  • 打赏
  • 举报
 回复
就不知道你当初执行“把数据文件全部copy到一个大容量的磁盘上面”是什么时机，不会是没有停止mysql服务的时候copy的吧？

MySQL 数据库备份并自动发送备份邮件
注:建议将视频播放速度调整为1.5倍速左右。MySQL数据库备份与自动发送备份邮件本课程详细介绍和演示了在Linux平台下MySQL数据库的备份，以及备份完成以后自动发送备份告警邮件,为了安全的考虑，数据库备份完成以后，备份文件会自动拷贝一份到指定的备份服务器上。为了方便了解和学习，课程中环境的部署分手动安装部署和一键安装部署。手动安装部署使大家可以熟悉环境的构成和安装操作。一键安装部署使大家可以快速且方便的快速完成环境的部署操作。课程课程包括以下内容:1.课程的介绍2.整个系统的效果演示3.备份服务器环境配置4.一键部署备份服务器环境配置5.备份服务器数据库配置6.所有数据库服务器的配置7.生成备份与发送邮件程序8.课程总结 
Navicat备份数据库时，mysql服务自动停止解决办法
单次修改 修改mysql的最大连接数, 使用内存变量修改法修改mysql的最大连接数： 命令提示符下： 1、cd进入：E:\mysql\mysql\bin> 2、E:\mysql\mysql\bin>mysql -uroot -p 3、输入密码 4、mysql> set global max_connections=500; 缺点：重启计算机或者mysql后最大连接数又会复位成初始值，需要重新设定。 修改配置文件 修改my.ini(需要重启mysql) windows系统下打开E:\mys
mysql服务总是自动停止_关于Mysql服务自动停止的问题
分析原因一：Mysql的自动备份功能可能导致数据库在备份的时候先关闭服务，而在此启动的时候服务器不响应，开始-运行-services.msc，打开windows服务找到mysql的服务并双击，点击恢复选项卡，第一次失败：默认是“不操作”,改成"重新启动服务"。在下方的“重新启动服务：分钟后”添上“0”表示如果服务意外终止则立即重启动。点击确定使设置生效。这时候你在任务管理器里结束mysql-nt进...
MySQL自动停止的解决办法
自动停止错误一： MySQL日志显示： 解决方法： 1、在服务中设置mysql自动重启； 2、在my.ini中[mysqld]下添加：federated即可； 3、重启mysql后日志“Plugin ‘FEDERATED’ is disabled”消失，如下图。 自动停止错误二： MYSQL启动报1067错误，系统日志中是“服务 mysql 意外停止”，Mysql日志中是“Plugin ‘FEDERATED’ is disabled”。 MySQL日志显示： 原因：是MySQL在安装的时候不会自动初始
Mysql服务启动后自动停止
首先，找到对应的mysql安装目录，若是没有配置文件，就如图创建一个，改后缀名即可，里面的配置信息可以自行百度，大体都是差不多的。鼠标右击修改，找到你mysql所安装的路径，如图所示，复制进去，一般来说只要改变bin目录前面的就行，bin目录后面的大体差不多。这方面是原来就有安装过mysql文件，导致启动mysql服务时无法启动，或者出现以下问题。1、控制面板-管理工具-服务->选中mysql服务->右键->属性。win + R 显示出的页面，输入regedit。例如：我的是mysql。
MySQL

56,679

社区成员

56,709

社区内容

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

加载中

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

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

+ 用AI写文章