mysql 启动不了
来源:互联网 发布:管家婆软件销售单抹零 编辑:程序博客网 时间:2024/04/27 12:01
昨天挂机插入1亿条数据,今早来mysql 就再也起不来了 。用的是wamp环境,错误日志如下:
2015-02-06 09:07:29 4884 [Note] Plugin 'FEDERATED' is disabled.2015-02-06 09:07:29 4884 [Note] InnoDB: Using atomics to ref count buffer pool pages2015-02-06 09:07:29 4884 [Note] InnoDB: The InnoDB memory heap is disabled2015-02-06 09:07:29 4884 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions2015-02-06 09:07:29 4884 [Note] InnoDB: Compressed tables use zlib 1.2.32015-02-06 09:07:29 4884 [Note] InnoDB: Not using CPU crc32 instructions2015-02-06 09:07:29 4884 [Note] InnoDB: Initializing buffer pool, size = 512.0M2015-02-06 09:07:29 4884 [Note] InnoDB: Completed initialization of buffer pool2015-02-06 09:07:29 4884 [Note] InnoDB: Highest supported file format is Barracuda.2015-02-06 09:07:29 4884 [Note] InnoDB: Log scan progressed past the checkpoint lsn 93607977082015-02-06 09:07:29 4884 [Note] InnoDB: Database was not shutdown normally!2015-02-06 09:07:29 4884 [Note] InnoDB: Starting crash recovery.2015-02-06 09:07:29 4884 [Note] InnoDB: Reading tablespace information from the .ibd files...2015-02-06 09:07:29 4884 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace api/pc07_email_token uses space ID: 1 at filepath: .\api\pc07_email_token.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibdInnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_stats.ibdInnoDB: We do not continue the crash recovery, because the table may becomeInnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.InnoDB: To fix the problem and start mysqld:InnoDB: 1) If there is a permission problem in the file and mysqld cannotInnoDB: open the file, you should modify the permissions.InnoDB: 2) If the table is not needed, or you can restore it from a backup,InnoDB: then you can remove the .ibd file, and InnoDB will do a normalInnoDB: crash recovery and ignore that table.InnoDB: 3) If the file system or the disk is broken, and you cannot removeInnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnfInnoDB: and force InnoDB to continue crash recovery here.好一串..... 估计是突然关机引起的。
解决方法:
再mysql ini配置文件中加:
innodb_force_recovery = 1 //强制重启mysql
然后重启wamp 稍等片刻 就会发现mysql 又活了,但是 不能执行 insert 、update、delete操作,接着再把 上面的配置删除 再重启。就真正的复活了 0 0
- linux启动不了mysql
- MySQL启动不了
- wamp mysql启动不了
- Mysql服务启动不了
- win7 启动不了mysql
- mysql 启动不了
- mysql 启动不了
- mysql服务启动不了
- mysql服务启动不了
- Mysql启动不了?
- MySQL启动不了,无法启动MySQL服务
- MySql的服务启动不了
- MYSQL 启动不了的解决方法
- mysql突然启动不了了
- [Mysql] 安装后启动不了
- mysql服务启动不了解决方案
- mac xampp mysql启动不了
- mysql服务启动不了解决方案
- 算法导论 第14章 数据结构的扩张(四) 14-1 最大重叠点
- thinkphp3.2 上传图片找不到根目录问题
- mysql笔记----PHP操作mysql数据库
- 【转载】进程和线程的区别
- 黑马程序员----OC基础--核心语法、关键字
- mysql 启动不了
- 几何问题。点线向量面积等模版。
- java字节流和字符流
- bzoj 2005 [Noi2010]能量采集 数学
- Android 通过ViewPager实现微信选项卡滑动的效果
- ZOJ 3600 Taxi Fare
- LeetCode-Two Sum(编程之美-快速寻找满足条件的两个数字)
- android:Tabhost
- ubuntu登陆root用户