宝塔 BT 面板 宝塔 BT 面板
宝塔 BT 面板

宝塔 BT – MySQL 5.6 无法启动

更新: 宝塔 V4.0 已修复该问题, 未来会自动修复 my.cnf 档案 -- 宝塔 v3.9 出现了 MySQL 的问题, 部分MySQL版本5.6会自动关闭并且无法重启. 主要的问题在于 MySQL 的配置档案被清理变成空白档, 具体原因不知道. 需要修复文件 /etc/my.cnf. 麻烦的方法是在其他空间架设同样的宝塔然后复制 /etc/my.cnf 的设置内容. 我刚好有另一个面板也使用 MySQL 5.6 所以可以直接复制过去. 这是 my.cnf 的设置内容, 你可以试试:
[client]
#password	= your_password
port		= 3306
socket		= /tmp/mysql.sock

[mysqld]
port		= 3306
socket		= /tmp/mysql.sock
datadir = /www/server/data
default_storage_engine = MyISAM
#skip-external-locking
#loose-skip-innodb
key_buffer_size = 8M
max_allowed_packet = 1M
table_open_cache = 32
sort_buffer_size = 256K
net_buffer_length = 4K
read_buffer_size = 128K
read_rnd_buffer_size = 256K
myisam_sort_buffer_size = 4M
thread_cache_size = 4
query_cache_size = 4M
tmp_table_size = 8M
sql-mode=NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTIO

#skip-networking
#skip-name-resolve
max_connections = 500
max_connect_errors = 100
open_files_limit = 65535

log-bin=mysql-bin
binlog_format=mixed
server-id	= 1
expire_logs_days = 10

default_storage_engine = InnoDB
innodb_data_home_dir = /www/server/data
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /www/server/data
innodb_buffer_pool_size = 16M
innodb_additional_mem_pool_size = 2M
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash

[myisamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout
本文由 Felicoz https://felicoz.com/ 原创发布,转载请保留地址!
bt MySQL 修复 宝塔