主页 / dba / 问题 / 36804
Accepted
thatidiotguy
Asked: 2013-03-16 12:25:25 +0800 CST

MySQL 5.6 失败

  • 772

RPM_UPGRADE_HISTORY我有以下内容/var/lib/mysql

MySQL RPM upgrade to version 5.6.10-1.linux_glibc2.5
'pre' step running at Fri Mar 15 15:41:26 EDT 2013

ERR file(s):
-rw-r----- 1 mysql root 1725 2013-03-15 13:45 /var/lib/mysql/mysql.err

我检查了错误文件以找到以下信息：

2013-03-15 15:43:22 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-03-15 15:43:22 11993 [Note] Plugin 'FEDERATED' is disabled.
2013-03-15 15:43:22 11993 [Note] InnoDB: The InnoDB memory heap is disabled
2013-03-15 15:43:22 11993 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2013-03-15 15:43:22 11993 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-03-15 15:43:22 11993 [Note] InnoDB: CPU does not support crc32 instructions
2013-03-15 15:43:22 11993 [Note] InnoDB: Using Linux native AIO
2013-03-15 15:43:22 11993 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-03-15 15:43:22 11993 [Note] InnoDB: Completed initialization of buffer pool
2013-03-15 15:43:22 11993 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
2013-03-15 15:43:22 11993 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2013-03-15 15:43:22 11993 [ERROR] Plugin 'InnoDB' init function returned error.
2013-03-15 15:43:22 11993 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2013-03-15 15:43:22 11993 [ERROR] Unknown/unsupported storage engine: InnoDB
2013-03-15 15:43:22 11993 [ERROR] Aborting

2013-03-15 15:43:22 11993 [Note] Binlog end
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'partition'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'BLACKHOLE'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'ARCHIVE'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_FT_INSERTED'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_METRICS'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_CMPMEM'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_CMP'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_LOCKS'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'INNODB_TRX'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'MRG_MYISAM'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'MEMORY'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'CSV'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'MyISAM'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'sha256_password'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'mysql_old_password'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'mysql_native_password'
2013-03-15 15:43:22 11993 [Note] Shutting down plugin 'binlog'
2013-03-15 15:43:22 11993 [Note] /usr/sbin/mysqld: Shutdown complete

130315 15:43:22 mysqld_safe mysqld from pid file /var/lib/mysql/mysql.pid ended

我在 MySQL 网站上使用 rpm 包安装。什么地方出了错？

mysql mysql-5.6

7 个回答

  1. Best Answer

    免责声明：不是 MySQL 5.6 的全面专家

    看起来 InnoDB 插件正在抱怨当前的 ibdata1 文件。

    如果 ibdata1 中存在数据和索引页面，它可能使用 Antelope 作为innodb_file_format。

    您可以尝试四 (4) 种方法：

    建议 #1：卸载并重新安装 MySQL 5.6

    • 卸载 MySQL
    • mv /var/lib/mysql /var/lib/mysql_old
    • 重新安装 MySQL

    建议 #2：使用清理后的数据目录

    mv /var/lib/mysql /var/lib/mysql_old
mkdir /var/lib/mysql
mkdir /var/lib/mysql/mysql
cp /var/lib/mysql_old /var/lib/mysql/mysql
chown -R mysql:mysql /var/lib/mysql/mysql
service mysql start

    这将构建全新的 InnoDB 文件

    • /var/lib/mysql/ibdata1
    • /var/lib/mysql/ib_logfile0
    • /var/lib/mysql/ib_logfile1

    建议 #3：切换 innodb_file_format （可能有风险）

    这可能有点冒险，但将其添加到my.cnf

    [mysqld]
innodb_file_format=Barracuda
innodb_file_format_max=Barracuda

    并重新启动mysql

    建议#4：试一试！！！

    • 7

  2. 即使我回答这个问题已经很晚了，但我最近遇到了这个问题，这是一个相当简单的修复......在我找到它之后。

    我正在从 5.1 升级到 5.6，并且在我的 mysqld.log 文件中有相同的错误。

    把它放在你的my.cnf下面[mysqld]：

    innodb_data_file_path = ibdata1:10M:autoextend
    • 3

  3. 删除ibdata1是有风险的。

    我可以通过添加来解决这个问题，

    innodb_data_file_path = ibdata1:10M:autoextend

    my.cnf归档。

    然后重新启动服务器。

    • 1

  4. SUGGESTION #1 帮助我修改

    first rename data dir from /var/lib/mysql to /var/lib/mysql2
apt-get remove mysql-server-5.6
apt-get autoremove
apt-get install mysql-server-5.6
service mysql stop
rename /var/lib/mysql to /var/lib/mysql.clean
rename /var/lib/mysql2 to /var/lib/mysql
    • 0

  5. 我知道它已经解决了，但我也遇到了同样的问题，我的解决方案是释放一些磁盘空间。

    我建议运行df -h以确保我们有可用的磁盘空间。

    • 0

  6. 如果您已从 MySQL 5.x 升级到 5.y，并且在 MySQL 日志 (/var/log/mysqld.log) 中有以下错误：

    error=[ERROR] InnoDB: auto-extending data file ./ibdata1 is of a
different size 640 pages (rounded down to MB) than specified in the
.cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!

    ...然后您必须/etc/my.cnf在该部分下添加一行[mysqld]：

    innodb_data_file_path = ibdata1:10M:autoextend

    ...并通过在 shell 中发出以下命令来重新启动 mysqld：

    service mysqld restart

    这将解决上述错误。

    • -1

  7. 我刚刚删除了以下文件：

    • /var/lib/mysql/ibdata1
    • /var/lib/mysql/ib_logfile0
    • /var/lib/mysql/ib_logfile1

    然后启动mysqld服务并成功运行...

    • -4

相关问题