2017-09-30 08:13:02 2816 [Note] Plugin 'FEDERATED' is disabled.
2017-09-30 08:13:02 1c9c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2017-09-30 08:13:02 2816 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-09-30 08:13:02 2816 [Note] InnoDB: The InnoDB memory heap is disabled
2017-09-30 08:13:02 2816 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-09-30 08:13:02 2816 [Note] InnoDB: Memory barrier is not used
2017-09-30 08:13:02 2816 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-09-30 08:13:02 2816 [Note] InnoDB: Not using CPU crc32 instructions
2017-09-30 08:13:02 2816 [Note] InnoDB: Initializing buffer pool, size = 261.0M
2017-09-30 08:13:02 2816 [Note] InnoDB: Completed initialization of buffer pool
2017-09-30 08:13:02 2816 [Note] InnoDB: Highest supported file format is Barracuda.
2017-09-30 08:13:02 2816 [Note] InnoDB: The log sequence numbers 21036463 and 21036463 in ibdata files do not match the log sequence number 22803441 in the ib_logfiles!
2017-09-30 08:13:02 2816 [Note] InnoDB: Database was not shutdown normally!
2017-09-30 08:13:02 2816 [Note] InnoDB: Starting crash recovery.
2017-09-30 08:13:02 2816 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-09-30 08:13:02 2816 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace rsgl_jl/jhsoft_xz_qcb which uses space ID: 2 at filepath: .\rsgl_jl\jhsoft_xz_qcb.ibd
InnoDB: Error: could not open single-table tablespace file .\rsgl_jl\jhsoft_xz_qcb.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: 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 cannot
InnoDB: 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 normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
mysql Plugin 'FEDERATED' is disabled.求解决
答案:2 悬赏:10 手机版
解决时间 2021-02-26 06:11
- 提问者网友:酱爆肉
- 2021-02-25 06:38
最佳答案
- 五星知识达人网友:孤老序
- 2021-02-25 07:03
1、在MY.INI文件中的[mysqld]中增加一行tmpdir="D:/MySQL/data/"修改后,还是启动不了或者能启动但关机后又出现同样问题,接着我做了第二步,重启正常。2、删除DATA目录下除数据库文件夹外的其他文件,重启mysql,问题解决。
全部回答
- 1楼网友:轻雾山林
- 2021-02-25 07:49
服务器宕机后,mysql无法启动 plugin federated is disabled
1、在my.ini文件中的 [mysqld] 中增加一行
tmpdir="d:/mysql/data/"
修改后,还是启动不了或者能启动但关机后又出现同样问题,接着我做了第二步,重启正常。
2、删除data目录下除数据库文件夹外的其他文件,重启mysql,问题解决。
我要举报
如以上回答内容为低俗、色情、不良、暴力、侵权、涉及违法等信息,可以点下面链接进行举报!
点此我要举报以上问答信息
大家都在看
推荐资讯