Mysql5.5 startup ERROR: ERROR!

 

An ERROR is reported when mysql is started in FreeBSD! The server quit without updating PID file, which is usually used to view The. err log in The database directory. It records some specific error information, which is quite useful for troubleshooting. The content is as follows:

110805 17:30:19 mysqld_safe Starting mysqld daemon with databases from/usr/local/mysql5.5/data

110805 17:30:19 InnoDB: The InnoDB memory heap is disabled

110805 17:30:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins

110805 17:30:19 InnoDB: Compressed tables use zlib 1.2.3

110805 17:30:19 InnoDB: Initializing buffer pool, size = 256.0 M

110805 17:30:19 InnoDB: Completed initialization of buffer pool

InnoDB: Error: log file/usr/local/mysql5.5/data/ib_logfile0 is of different size 0 5242880 bytes

InnoDB: than specified in the. cnf file 0 67108864 bytes!

110805 17:30:19 [ERROR] Plugin 'innodb' init function returned error.

110805 17:30:19 [ERROR] Plugin 'innodb' registry as a storage engine failed.

110805 17:30:19 [ERROR] Unknown/unsupported storage engine: InnoDB

110805 17:30:19 [ERROR] Aborting

 

110805 17:30:19 [Note]/usr/local/mysql5.5/bin/mysqld: Shutdown complete

The error is displayed in the red font above. The log file size is incorrect. view the mysql configuration file/etc/my. cnf.

# Uncomment the following if you are using InnoDB tables

Innodb_data_home_dir =/usr/local/mysql5.5/data

Innodb_data_file_path = ibdata1: 10 M: autoextend

Innodb_log_group_home_dir =/usr/local/mysql5.5/data

# You can set .. _ buffer_pool_size up to 50-80%

# Of RAM but beware of setting memory usage too high

Innodb_buffer_pool_size = 256 M

Innodb_additional_mem_pool_size = 20 M

# Set .. _ log_file_size to 25% of buffer pool size

Innodb_log_file_size = 64 M

Innodb_log_buffer_size = 8 M

Innodb_flush_log_at_trx_commit = 1

Innodb_lock_wait_timeout = 50

Innodb_log_file_size = 64 M is specified in the configuration file. Check whether the log file size is 64 M in my database directory. If any problem is found, the log file size is 5242880 or 5 M.

 

If the problem is found, you can change the configuration file, delete the current log, and then start mysql to regenerate the two log files.

 

How can this problem occur?

In general, it is because, in my. some configurations of INNODB in cnf are commented out, and the default value is used when no changes are made. In this way, when you comment out the configuration options of innodb, this error will occur!