Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Mysql5.5 startup error: what to do with ERROR

2025-01-26 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)05/31 Report--

Today, I will talk to you about mysql5.5 startup error report: what to do with ERROR, many people may not know much about it. In order to make you understand better, the editor summed up the following content for you. I hope you can get something according to this article.

Error when starting MySQL in FreeBSD, ERROR! The server quit without updating PID file, usually you can view the .err log in the directory, in which some specific error messages are recorded, which are very useful for troubleshooting, as follows:

110805 17:30:19 d_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.0M

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

InnoDB: Error: logfile / 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' registration 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

See the red font above and show that the error is on the log file size, so look at mysql's 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:10M: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 = 256m

Innodb_additional_mem_pool_size = 20m

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

Innodb_log_file_size = 64m

Innodb_log_buffer_size = 8m

Innodb_flush_log_at_trx_commit = 1

Innodb_lock_wait_timeout = 50

Innodb_log_file_size=64M is specified in the configuration file. Check my database directory to see if the log file size is 64m. As shown in the figure below, a problem is found. The log file is 5242880 and 5m.

If you find the problem, you can change the configuration file, or you can delete the current log, and then start mysql so that it will regenerate the two log files.

How did this problem happen?

In general, it is because some configurations about INNODB in my.cnf are annotated, and the system uses the default values without change, so that this error occurs when you leave out the comments on the configuration options for innodb!

After reading the above, do you have any further understanding of mysql5.5 startup error: what to do with ERROR? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 268

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report