我正在尝试使用easyPHP启动MySQL:响应是日志文件的警报窗口。主要错误是。
通过在线研究，我发现解决方案是将联合选项添加到my.ini文件中。我这样做了，但仍然无法正常工作。
以下是日志文件的摘录，以获取更多信息:
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服务器上未开启。默认情况下不使用。如果您不需要它，则无需关心此消息。
可以在以下链接中找到有关联合引擎的更多信息:
关于mysql - 插件 'FEDERATED'已禁用，我们在Stack Overflow上找到一个类似的问题：https://stackoverflow.com/questions/16416183/