插件“FEDERATED”已禁用 [英] Plugin 'FEDERATED' is disabled

查看:1072
本文介绍了插件“FEDERATED”已禁用的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我试图使用easyPHP启动MySQL:响应是一个警告窗口日志文件。主要错误是 < - Plugin'FEDERATED'被禁用 - >

Im trying to start MySQL using easyPHP: the response is an alert window to a log file. The main error is <-- Plugin 'FEDERATED' is disabled -->.

通过在线研究,我发现解决方案是将联合选项添加到 my.ini 文件。

Through research online I found that the solution is to add the federated option to the my.ini file. I did this, but it is still not working.

这是从日志文件中提取更多信息:

Here is an extract from the log file for more information:

2013-05-03 14:12:57 3776 [Note] Plugin 'FEDERATED' is disabled.
2013-05-03 14:12:57 1b4c 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.
2013-05-03 14:12:57 3776 [Note] InnoDB: The InnoDB memory heap is disabled
2013-05-03 14:12:57 3776 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-05-03 14:12:57 3776 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-05-03 14:12:57 3776 [Note] InnoDB: Not using CPU crc32 instructions
2013-05-03 14:12:57 3776 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-05-03 14:12:57 3776 [Note] InnoDB: Completed initialization of buffer pool
2013-05-03 14:12:57 3776 [Note] InnoDB: The first specified data file .\ibdata1 did not exist: a new database to be created!
2013-05-03 14:12:57 3776 [Note] InnoDB: Setting file .\ibdata1 size to 12 MB
2013-05-03 14:12:57 3776 [Note] InnoDB: Database physically writes the file full: wait...
2013-05-03 14:12:57 3776 [Note] InnoDB: Setting log file .\ib_logfile101 size to 5 MB
2013-05-03 14:12:57 3776 [Note] InnoDB: Setting log file .\ib_logfile1 size to 5 MB
2013-05-03 14:12:57 3776 [Note] InnoDB: Renaming log file .\ib_logfile101 to .\ib_logfile0
2013-05-03 14:12:57 3776 [Warning] InnoDB: New log files created, LSN=45781
2013-05-03 14:12:57 3776 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-05-03 14:12:57 3776 [Note] InnoDB: Doublewrite buffer created
2013-05-03 14:12:57 3776 [Note] InnoDB: 128 rollback segment(s) are active.
2013-05-03 14:12:57 3776 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-05-03 14:12:57 3776 [Note] InnoDB: Foreign key constraint system tables created
2013-05-03 14:12:57 3776 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-05-03 14:12:57 3776 [Note] InnoDB: Tablespace and datafile system tables created.
2013-05-03 14:12:57 3776 [Note] InnoDB: Waiting for purge to start
2013-05-03 14:12:57 3776 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-05-03 14:12:58 3776 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: cadcd135-b3ea-11e2-92bc-e0db55e1304d.
2013-05-03 14:12:58 3776 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2013-05-03 14:12:58 3776 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
2013-05-03 14:12:58 3776 [Note] Server socket created on IP: '127.0.0.1'.
2013-05-03 14:12:58 3776 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-05-03 14:12:58 3776 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-05-03 14:12:58 3776 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-05-03 14:12:58 3776 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-05-03 14:12:58 3776 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-05-03 14:12:58 3776 [Note] Event Scheduler: Loaded 0 events
2013-05-03 14:12:58 3776 [Note] C:\PROGRA~1\EASYPH~1.1VC\binaries\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
2013-05-03 14:15:59 3776 [Note] C:\PROGRA~1\EASYPH~1.1VC\binaries\mysql\bin\mysqld.exe: Normal shutdown


推荐答案

关于FEDERATED已禁用的消息不是错误。它只是意味着FEDERATED引擎不为您的mysql服务器。默认情况下不使用它。

The message about FEDERATED disabled is not an error. It just meant that the FEDERATED engine its not ON for your mysql server. It's not used by default. If you don't need it, don't care about this message.


FEDERATED 存储引擎是可从MySQL 5.0.3开始。它是一个访问远程数据库表而不是本地表中的数据的存储引擎。

The FEDERATED storage engine is available beginning with MySQL 5.0.3. It is a storage engine that accesses data in tables of remote databases rather than in local tables.

可以找到联合引擎的更多信息在此链接:

More info on federated engine can be found at this link:

  • The FEDERATED Storage Engine - MySQL Reference Manual

这篇关于插件“FEDERATED”已禁用的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆