无法启动MariaDB

Question

这个周末我关闭服务器后，我无法启动MariaDB。 我在日志中看到了这一点：

171030 10:09:18 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
171030 10:09:18 [Note] /usr/sbin/mysqld (mysqld 5.5.45-MariaDB) starting as process 2583 ...
171030 10:09:18 InnoDB: The InnoDB memory heap is disabled
171030 10:09:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins
171030 10:09:18 InnoDB: Compressed tables use zlib 1.2.3
171030 10:09:18 InnoDB: Using Linux native AIO
171030 10:09:18 InnoDB: Initializing buffer pool, size = 128.0M
171030 10:09:18 InnoDB: Completed initialization of buffer pool
171030 10:09:18  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: File name /var/lib/mysql//var/lib/mysql/ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.
171030 10:09:18 mysqld_safe mysqld from pid file /var/lib/mysql/db05.pid ended

这看起来很有趣：

InnoDB: File name /var/lib/mysql//var/lib/mysql/ibdata1

我不确定它从哪里得到的。 这是my.cnf文件：

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
# Settings user and group are ignored when systemd is used.
# If you need to run mysqld under a different user or group,
# customize your systemd unit file for mariadb according to the
# instructions in http://fedoraproject.org/wiki/Systemd
# innodb_force_recovery = 4
lower_case_table_names = 1
character-set-server=utf8
collation-server=utf8_bin
default-storage-engine=INNODB
max_allowed_packet=256M
innodb_data_home_dir = /var/lib/mysql
innodb_data_file_path = /var/lib/mysql/ibdata1:3000M;/var/lib/mysql/ibdata2:586M:autoextend
transaction-isolation=READ-COMMITTED

innodb_log_buffer_size          = 32M
innodb_buffer_pool_size         = 3G
innodb_log_file_size            = 768M

[mysqld_safe]
log-error=/var/log/mariadb/mariadb.log
pid-file=/var/run/mariadb/mariadb.pid

#
# include all files from the config directory
#
!includedir /etc/my.cnf.d

我已尝试根据显示的其他错误添加显示的日志文件条目，并在innodb_data_file_path参数中增加ibdata1的大小，我不再认为这是相关的。

Answer 1

您的服务器正在生成一个奇怪的路径名来设置ibdata1容器文件。 当它执行/var/lib/mysql//var/lib/mysql/ibdata1时，它正在执行Path/Path/Filename 。

您可以尝试在my.cnf更改此行

innodb_data_file_path = /var/lib/mysql/ibdata1:3000M;/var/lib/mysql/ibdata2:586M:autoextend

对此：

innodb_data_file_path =  ibdata1:3000M;ibdata2:586M:autoextend

如果这样不起作用，请放回原始值。 然后做

 px axuww | grep mysql 

到shell，然后尝试确定您的mysqld服务器程序是否正在使用不需要的额外路径变量运行。

Answer 2

显然， innodb_data_home_dir设置中存在/var/lib/mysql路径：

innodb_data_home_dir = /var/lib/mysql

但是它也存在于innodb_data_file_path 。 因此，只需更改此：

innodb_data_file_path = /var/lib/mysql/ibdata1:3000M;/var/lib/mysql/ibdata2:586M:autoextend

对此：

innodb_data_file_path = ibdata1:3000M;ibdata2:586M:autoextend