MySQL启动报错解决一例
由于项目需要不得不折腾MySQL,RedHat Linux上安装了最新的MySQL 5.6启动报错如下:[root@tserver mysql]# /etc/init.d/mysql st
由于项目需要不得不折腾MySQL,,RedHat Linux上安装了最新的MySQL 5.6启动报错如下:
[root@tserver mysql]# /etc/init.d/mysql start
Starting MySQL.The server quit without updating PID file (/var/lib/mysql/tserver.pid).[FAILED]
检查报错信息tserver.err。
cat tserver.err
140121 06:03:29 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2014-01-21 06:03:29 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-01-21 06:03:29 14964 [Note] Plugin 'FEDERATED' is disabled.
2014-01-21 06:03:29 14964 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-21 06:03:29 14964 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-01-21 06:03:29 14964 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-21 06:03:29 14964 [Note] InnoDB: Using Linux native AIO
2014-01-21 06:03:29 14964 [Note] InnoDB: Using CPU crc32 instructions
2014-01-21 06:03:29 14964 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-01-21 06:03:29 14964 [Note] InnoDB: Completed initialization of buffer pool
2014-01-21 06:03:29 14964 [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!
2014-01-21 06:03:29 14964 [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!
2014-01-21 06:03:29 14964 [ERROR] Plugin 'InnoDB' init function returned error.
2014-01-21 06:03:29 14964 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2014-01-21 06:03:29 14964 [ERROR] Unknown/unsupported storage engine: InnoDB
2014-01-21 06:03:29 14964 [ERROR] Aborting
2014-01-21 06:03:29 14964 [Note] Binlog end
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'partition'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_METRICS'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_CMP'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'INNODB_TRX'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'BLACKHOLE'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'ARCHIVE'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'CSV'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'MEMORY'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'MRG_MYISAM'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'MyISAM'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'sha256_password'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'mysql_old_password'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'mysql_native_password'
2014-01-21 06:03:29 14964 [Note] Shutting down plugin 'binlog'
2014-01-21 06:03:29 14964 [Note] /usr/sbin/mysqld: Shutdown complete
检查发现mysql的目录下有如下文件:
[root@tserver mysql]# ls
ibdata1 ib_logfile0 ib_logfile1 mysql RPM_UPGRADE_HISTORY RPM_UPGRADE_MARKER-LAST test tserver.err
删除了如下三个文件:
上一篇: Photoshop打造发光的蓝色数码眼睛
下一篇: 程序员如何挽救日渐失控的项目?
推荐阅读
-
php 启动时报错的简单解决方法
-
Linux 初始化MySQL 数据库报错解决办法
-
MySQL启动时InnoDB引擎被禁用了的解决方法
-
解决“无法启动mysql服务 错误1069”的方法
-
完美解决mysql启动后随即关闭的问题(ibdata1文件损坏导致)
-
CentOS7下MySQL服务启动失败原因及解决方法
-
连接MySQL报错误代码 ERROR 1045时的解决方案
-
MySQL保存中文字段时报错的解决办法
-
使用cmd运行mysql数据库的时候,报错:"不是内部命令也不是可有运行的程序"问题的解决办法
-
mysql执行sql文件报错Error: Unknown storage engine‘InnoDB’的解决方法