当前位置:首页 > > 充电吧
[导读]由于项目需要不得不折腾mysql,redhat上安装了最新的mysql 5.6启动报错如下:[root@tserver mysql]# /etc/init.d/mysql startStarting

由于项目需要不得不折腾mysql,redhat上安装了最新的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

删除了如下三个文件:

[root@tserver mysql]# rm ibdata1  ib_logfile0  ib_logfile1 
rm: remove regular file `ibdata1'? yes       
rm: remove regular file `ib_logfile0'? yes
rm: remove regular file `ib_logfile1'? yes

重新启动mysql server就可以了:

[root@tserver mysql]# /etc/init.d/mysql start
Starting MySQL.[  OK  ]
[root@tserver mysql]# ps -ef|grep mysql
root     15166     1  0 06:12 pts/0    00:00:00 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/tserver.pid
mysql    15257 15166  9 06:12 pts/0    00:00:00 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=/var/lib/mysql/tserver.err --pid-file=/var/lib/mysql/tserver.pid
root     15284 14224  0 06:12 pts/0    00:00:00 grep mysql


本站声明: 本文章由作者或相关机构授权发布,目的在于传递更多信息,并不代表本站赞同其观点,本站亦不保证或承诺内容真实性等。需要转载请联系该专栏作者,如若文章内容侵犯您的权益,请及时联系本站删除。
换一批
延伸阅读

LED驱动电源的输入包括高压工频交流(即市电)、低压直流、高压直流、低压高频交流(如电子变压器的输出)等。

关键字: 驱动电源

在工业自动化蓬勃发展的当下,工业电机作为核心动力设备,其驱动电源的性能直接关系到整个系统的稳定性和可靠性。其中,反电动势抑制与过流保护是驱动电源设计中至关重要的两个环节,集成化方案的设计成为提升电机驱动性能的关键。

关键字: 工业电机 驱动电源

LED 驱动电源作为 LED 照明系统的 “心脏”,其稳定性直接决定了整个照明设备的使用寿命。然而,在实际应用中,LED 驱动电源易损坏的问题却十分常见,不仅增加了维护成本,还影响了用户体验。要解决这一问题,需从设计、生...

关键字: 驱动电源 照明系统 散热

根据LED驱动电源的公式,电感内电流波动大小和电感值成反比,输出纹波和输出电容值成反比。所以加大电感值和输出电容值可以减小纹波。

关键字: LED 设计 驱动电源

电动汽车(EV)作为新能源汽车的重要代表,正逐渐成为全球汽车产业的重要发展方向。电动汽车的核心技术之一是电机驱动控制系统,而绝缘栅双极型晶体管(IGBT)作为电机驱动系统中的关键元件,其性能直接影响到电动汽车的动力性能和...

关键字: 电动汽车 新能源 驱动电源

在现代城市建设中,街道及停车场照明作为基础设施的重要组成部分,其质量和效率直接关系到城市的公共安全、居民生活质量和能源利用效率。随着科技的进步,高亮度白光发光二极管(LED)因其独特的优势逐渐取代传统光源,成为大功率区域...

关键字: 发光二极管 驱动电源 LED

LED通用照明设计工程师会遇到许多挑战,如功率密度、功率因数校正(PFC)、空间受限和可靠性等。

关键字: LED 驱动电源 功率因数校正

在LED照明技术日益普及的今天,LED驱动电源的电磁干扰(EMI)问题成为了一个不可忽视的挑战。电磁干扰不仅会影响LED灯具的正常工作,还可能对周围电子设备造成不利影响,甚至引发系统故障。因此,采取有效的硬件措施来解决L...

关键字: LED照明技术 电磁干扰 驱动电源

开关电源具有效率高的特性,而且开关电源的变压器体积比串联稳压型电源的要小得多,电源电路比较整洁,整机重量也有所下降,所以,现在的LED驱动电源

关键字: LED 驱动电源 开关电源

LED驱动电源是把电源供应转换为特定的电压电流以驱动LED发光的电压转换器,通常情况下:LED驱动电源的输入包括高压工频交流(即市电)、低压直流、高压直流、低压高频交流(如电子变压器的输出)等。

关键字: LED 隧道灯 驱动电源
关闭