我有一个大问题。
我尝试在 ubuntu 中启动 mysql,但是出现此错误:
130323 0:13:55 [Note] Plugin 'FEDERATED' is disabled.
130323 0:13:55 InnoDB: The InnoDB memory heap is disabled
130323 0:13:55 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130323 0:13:55 InnoDB: Compressed tables use zlib 1.2.3.4
130323 0:13:55 InnoDB: Initializing buffer pool, size = 8.0G
130323 0:13:55 InnoDB: Completed initialization of buffer pool
130323 0:13:55 InnoDB: highest supported file format is Barracuda.
130323 0:13:55 InnoDB: Waiting for the background threads to start
130323 0:13:56 InnoDB: 1.1.8 started; log sequence number 1195255849922
130323 0:13:56 [ERROR] /usr/sbin/mysqld: unknown option '--query_cache_size-128M'
130323 0:13:56 [ERROR] Aborting
130323 0:13:56 InnoDB: Starting shutdown...
130323 0:13:57 InnoDB: Shutdown completed; log sequence number 1195255849922
130323 0:13:57 [Note] /usr/sbin/mysqld: Shutdown complete
这没有意义,因为我没有在 my.cnf 中使用它:
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
# Here is entries for some specific programs
# The following values assume you have at least 32M ram
# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0
[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
#datadir = /var/lib/mysql
datadir = /home/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
#innodb_force_recovery = 3
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1
#
# * Fine Tuning
#
key_buffer = 500M
max_allowed_packet = 128M
thread_stack = 192K
thread_cache_size = 8
default-storage-engine = INNODB
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover = BACKUP
max_connections = 75
sort_buffer_size = 4M
join_buffer_size = 4M
table_cache = 128K
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
general_log_file = /var/log/mysql/mysql.log
log-error=/var/log/mysql.err
#general_log = 1
#
# Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
# other settings you may need to change.
#server-id = 1
#log_bin = /var/log/mysql/mysql-bin.log
expire_logs_days = 10
max_binlog_size = 100M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem
innodb_additional_mem_pool_size = 50M
innodb_thread_concurrency = 8
innodb_flush_method = O_DSYNC
innodb_flush_log_at_trx_commit = 2
innodb_buffer_pool_size = 8G
innodb_log_files_in_group = 2
innodb_log_file_size = 32M
innodb_log_buffer_size = 16M
innodb_file_per_table = 1
innodb_table_locks = 0
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
[mysql]
#no-auto-rehash # faster start of mysql but no tab completition
[isamchk]
key_buffer = 16M
#
# * IMPORTANT: Additional settings that can override those from this file!
# The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/
有任何想法吗? :(
答案1
检查 my.cnf 文件中错误日志中列出的选项并将其注释掉。启动 mysql。
答案2
检查您的 /etc/init.d/mysql 是否尝试使用此选项启动 MySQL。
答案3
我遇到了这个问题,显然我的机器 /usr/ 下有一个名为 my.cnf 的文件,其中包含:
nnodb_force_recovery = 6
注释掉后 mysql 就可以正常启动了。
答案4
我遇到了类似的问题,这是 mariadb 系统配置文件上的配置错误。有些行有错误。例如
mariadb.service - MariaDB 10.3.32 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─override.conf
Active: failed (Result: exit-code) since Thu 2021-12-23 09:13:03 -03; 33s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 1638 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 1639 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 1641 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_>
Process: 1688 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/run/mysqld/mysqld.pid --skip-grant-tables --skip-networking (code=exited, status=2)
Main PID: 1688 (code=exited, status=2)
Status: "MariaDB server is down"
Drop-In 选项显示 /etc/systemd/system/mariadb.service.d/override.cnf 中有错误的文件
服务启动时发生了变化,因此没有启动。我修改了这个文件,删除了他的内容并弹出
sudo systemctl 守护进程重新加载
进而
sudo systemctl 启动 mariadb
一切正常。因此,请检查系统上的修改