WDCP open page Times error: Unable to connect to MySQL, please check if MySQL is started and user password is configured correctly

Today, a long time ago, a WDCP integrated Web service has a problem, open Web page display "Unable to connect to MySQL, please check whether MySQL is started and user password is configured correctly"

????

????????????????? (Web Access error message for server failure)

????

???? On the internet for three hours of information, found a lot of friends encountered the problem, and as long as the database connection is not normal or the database does not start normally, all will report this error, the following is my workaround:

1. Check Service operation status

[[Email protected] etc]# service mysqld status

? MySQL is not running.

#mysql服务并未运行

[Email protected] etc]# service mysqld restart

? error! MySQL Manager or server PID file could not being found!

Starting MySQL. error! Manager of Pid-file quit without updating file.

#试图重启服务, result error

[Email protected] etc]# Cat/www/wdlinux/mysql-5.1.69/var/wdcp.err

To view the error log for WDCP

? ? 171209 16:10:02 mysqld_safe mysqld from PID File/www/wdlinux/mysql-5.1.69/var/wdcp.pid ended

???? 171209 16:12:25 Mysqld_safe starting mysqld daemon with databases From/www/wdlinux/mysql-5.1.69/var

???? 171209 16:12:25 [ERROR]/www/wdlinux/mysql-5.1.69/libexec/mysqld:unknown variable 'Innodb_additional_mem_pool_ size=16m'

???? 171209 16:12:25 [ERROR] Aborting

???? #从日志看为止的innodb我觉定把innodb的选项注释掉看一下, the result of restarting the service reported a new error.

???? 171209 16:10:02 mysqld_safe mysqld from PID File/www/wdlinux/mysql-5.1.69/var/wdcp.pid ended

???? 171209 16:12:25 Mysqld_safe starting mysqld daemon with databases From/www/wdlinux/mysql-5.1.69/var

???? 171209 16:12:25 [ERROR]/www/wdlinux/mysql-5.1.69/libexec/mysqld:unknown variable ' innodb_additional_mem_pool_size= 16M '

???? 171209 16:12:25 [ERROR] Aborting

????

???? 171209 16:12:25 [Note]/www/wdlinux/mysql-5.1.69/libexec/mysqld:shutdown complete

????

???? 171209 16:12:25 mysqld_safe mysqld from PID File/www/wdlinux/mysql-5.1.69/var/wdcp.pid ended

???? 171209 16:13:32 Mysqld_safe starting mysqld daemon with databases From/www/wdlinux/mysql-5.1.69/var

???? 171209 16:13:32 [ERROR]/www/wdlinux/mysql-5.1.69/libexec/mysqld:unknown variable 'innodb_buffer_pool_size=2g '

???? 171209 16:13:32 [ERROR] Aborting

???? #还是和innodb有关系, decide all the InnoDB are written off!!???

???? 171209 16:13:32 [Note]/www/wdlinux/mysql-5.1.69/libexec/mysqld:shutdown complete

????

???? 171209 16:13:32 mysqld_safe mysqld from PID File/www/wdlinux/mysql-5.1.69/var/wdcp.pid ended

???? 171209 16:14:34 Mysqld_safe starting mysqld daemon with databases From/www/wdlinux/mysql-5.1.69/var

???? 171209 16:14:35 [ERROR]/www/wdlinux/mysql-5.1.69/libexec/mysqld:unknown variable ' innodb_buffer_pool_size=2g '

???? 171209 16:14:35 [ERROR] Aborting

????

???? 171209 16:14:35 [Note]/www/wdlinux/mysql-5.1.69/libexec/mysqld:shutdown complete

????

???? 171209 16:14:35 mysqld_safe mysqld from PID File/www/wdlinux/mysql-5.1.69/var/wdcp.pid ended

? ? #在/www/wdlinux/etc/my.cnf The options for InnoDB all commented out

???? #innodb_buffer_pool_size = 2G

???? #innodb_data_file_path = Ibdata1:10m:autoextend

???? #innodb_file_io_threads = 4

???? #innodb_thread_concurrency =

???? #innodb_flush_log_at_trx_commit = 1

???? #innodb_log_buffer_size = 8M

???? #innodb_log_file_size = 256M

???? #innodb_log_files_in_group = 3

???? #innodb_max_dirty_pages_pct =

???? #innodb_lock_wait_timeout =

???? Start the MySQL service to test:

????

???? [[Email protected] ~]# service mysqld start

???? Starting MySQL. success!

? ? #mysql启动成功

???? Specific reasons have not been found, mainly because this is not the main business system, and the system is a pre-development staff, so there are some problems, this document only as a simple record, to identify specific problems will be collated detailed documents.

WDCP open page Times error: Unable to connect to MySQL, please check if MySQL is started and user password is configured correctly