MySQL startup error solution example

Source: Internet
Author: User
Because the project had to toss MySQL, the latest MySQL5.6 startup error was installed on RedHatLinux: [root @ tservermysql] # etcinit. dmysqlst

The latest MySQL 5.6 startup error on RedHat Linux is reported as follows: [root @ tserver MySQL] #/etc/init. d/mysql st

Because the project had to toss MySQL, the latest MySQL 5.6 startup error was installed on RedHat Linux:

[Root @ tserver mysql] #/etc/init. d/mysql start
Starting MySQL. The server quit without updating PID file (/var/lib/mysql/tserver. pid). [FAILED]

Check the error message tserver. err.

Cat tserver. err

140121 06:03:29 mysqld_safe Starting mysqld daemon with databases from/var/lib/mysql
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 ).
06:03:29 14964 [Note] Plugin 'federated 'is disabled.
06:03:29 14964 [Note] InnoDB: The InnoDB memory heap is disabled
06:03:29 14964 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
06:03:29 14964 [Note] InnoDB: Compressed tables use zlib 1.2.3
06:03:29 14964 [Note] InnoDB: Using Linux native AIO
06:03:29 14964 [Note] InnoDB: Using CPU crc32 instructions
06:03:29 14964 [Note] InnoDB: Initializing buffer pool, size = 128.0 M
06:03:29 14964 [Note] InnoDB: Completed initialization of buffer pool
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. cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
06:03:29 14964 [ERROR] InnoDB: cocould not open or create the system tablespace. if you tried to add new data files to the system tablespace, and it failed here, you shocould 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!
06:03:29 14964 [ERROR] Plugin 'innodb' init function returned error.
06:03:29 14964 [ERROR] Plugin 'innodb' registry as a storage engine failed.
06:03:29 14964 [ERROR] Unknown/unsupported storage engine: InnoDB
06:03:29 14964 [ERROR] Aborting

06:03:29 14964 [Note] Binlog end
06:03:29 14964 [Note] Shutting down plugin 'partition'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ SYS_DATAFILES'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ SYS_TABLESPACES'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ sys_foreign_cols'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ sys_foreign'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ SYS_FIELDS'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ SYS_COLUMNS'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ sys_indexes'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ sys_tablestats'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ SYS_TABLES'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ FT_INDEX_TABLE'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ FT_INDEX_CACHE'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ FT_CONFIG'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ ft_being_deleted'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ ft_deleted'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ ft_default_stopword'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ metrics'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ buffer_pool_stats'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ buffer_page_lru'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ BUFFER_PAGE'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ CMP_PER_INDEX_RESET'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ CMP_PER_INDEX'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ cmpmem_reset'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ CMPMEM'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ cmp_reset'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ CMP'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ LOCK_WAITS'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ locks'
06:03:29 14964 [Note] Shutting down plugin 'innodb _ trx'
06:03:29 14964 [Note] Shutting down plugin 'performance _ Scheme'
06:03:29 14964 [Note] Shutting down plugin 'blackhole'
06:03:29 14964 [Note] Shutting down plugin 'archive'
06:03:29 14964 [Note] Shutting down plugin 'csv'
06:03:29 14964 [Note] Shutting down plugin 'memory'
06:03:29 14964 [Note] Shutting down plugin 'mrg _ myisam'
06:03:29 14964 [Note] Shutting down plugin 'myisam'
06:03:29 14964 [Note] Shutting down plugin 'sha256 _ password'
06:03:29 14964 [Note] Shutting down plugin 'mysql _ old_password'
06:03:29 14964 [Note] Shutting down plugin 'mysql _ native_password'
06:03:29 14964 [Note] Shutting down plugin 'binlog'
06:03:29 14964 [Note]/usr/sbin/mysqld: Shutdown complete

Check that the mysql directory contains the following files:


[Root @ tserver mysql] # ls
Ibdata1 ib_logfile0 ib_logfile1 mysql RPM_UPGRADE_HISTORY RPM_UPGRADE_MARKER-LAST test tserver. err

The following three files are deleted:

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.