MySQL startup error (1)--2 examples

First time to install MySQL, start the Times wrong

#/etc/init.d/mysqld startstarting MySQL .... The server quit without updating PID f[failed]tmp/mysql.pid).

View Logs

# tailf/data/mysqldb/log/mysql-error.log160730 00:57:28 Mysqld_safe starting mysqld daemon with databases From/data/mys qldb2016-07-30 00:57:29 0 [Note]/usr/local/mysql/bin/mysqld (mysqld 5.6.31-log) starting as Process 18702 ... 2016-07-30 00:57:29 18702 [Warning] option ' innodb-buffer-pool-instances ': signed value-1 adjusted to 0.........2016-07-  00:57:29 18702 [ERROR] innodb:auto-extending data file./ibdata1 is an different size 768 pages (rounded to MB) than specified in the. CNF file:initial 131072 pages, max 0 (relevant if non-zero) pages!2016-07-30 00:57:29 18702 [Erro R] 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 is, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, and did not yet with them in any. But is careful:do not remove old data Files which contain your precious data!2016-07-30 00:57:29 18702 [ERROR] Plugin ' InnoDB ' init function returned error.201 6-07-30 00:57:29 18702 [ERROR] Plugin ' InnoDB ' registration as a STORAGE ENGINE failed.2016-07-30 00:57:29 18702 [ERROR] U nknown/unsupported storage engine:innodb2016-07-30 00:57:29 18702 [ERROR] aborting ... 160730 00:57:29 mysqld_safe mysqld from PID File/tmp/mysql.pid ended

Workaround

# ls/data/mysqldbbinlog  ibdata1  ib_logfile0  ib_logfile1  log  mysql  performance_schema  Test Rename or delete these three files directly # MV Ibdata1 ibdata1.bak# MV Ib_logfile0 ib_logfile0.bak# mv Ib_logfile1 ib_logfile1.bak#/etc/ Init.d/mysqld startstarting MySQL ...                     ...... ......... Determine

Before because of always power off, start the database report similar to the following error

#/etc/init.d/mysqld Statusmysql isn't running, but lock file (/var/lock/subsys/mysql[failed]ts

View Logs

# tailf/data/mysqldb/log/mysql-error.log Innodb:to Fix the problem and start mysqld:innodb:1) If there is a permission Problem in the file and mysqld cannotinnodb:open the file, you should modify the permissions. INNODB:2) If The table is not needed, or you can restore it from a backup,innodb:then you can remove the. ibd file, and InnoDB would do a normalinnodb:crash recovery and ignore that table. Innodb:3) If the file system or the disk is broken, and you cannot removeinnodb:the. ibd file, can set Innodb_force_ Recovery > 0 in My.cnfInnoDB:and Force InnoDB to continue crash recovery here.160801 19:30:39 Mysqld_safe mysqld from PID File/tmp/mysql.pid Ended

Workaround

Ditto, delete those files to

MySQL startup error (1)--2 examples