我无法在 linux 上启动 MySQL - 错误 mysqld_safe

声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow 原文地址: http://stackoverflow.com/questions/19117487/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me): StackOverFlow

提示:将鼠标放在中文语句上可以显示对应的英文。显示中英文
时间:2020-08-07 00:59:24  来源:igfitidea点击:

I can't start MySQL on linux - Error mysqld_safe

mysqllinux

提问by Rafael Soufraz

I found in many forums around the web, but I did not find my solution. When I start the service mysql in linux ubuntu server 12.04, I get this error:

我在网络上的许多论坛上都找到了,但没有找到我的解决方案。当我在 linux ubuntu server 12.04 中启动服务 mysql 时,出现此错误:

root@stroke:/# mysqld_safe &
[1] 5789
root@stroke:/# 131001 10:12:29 mysqld_safe Logging to syslog.
131001 10:12:29 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
131001 10:12:29 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

I've already given permission to the folder mysql, I've also tried to create a new password for the root mysql. But so far nothing has worked.

我已经授予文件夹 mysql 的权限,我还尝试为根 mysql 创建一个新密码。但到目前为止,一切都没有奏效。

Thanks for help.

感谢帮助。

Some information:

一些信息:

root@stroke:/# /etc/init.d/mysql start
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service mysql start

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start mysql
start: Job failed to start

The /etc/mysql/my.cnf file

/etc/mysql/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
#
innodb_force_recovery = 4
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /tmp
lc-messages-dir = /usr/share/mysql
#skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address            =  0.0.0.0
#
# * Fine Tuning
#
key_buffer              = 256M
max_allowed_packet      = 16M
thread_stack            = 192K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover         = BACKUP
#max_connections        = 100
#table_cache            = 64
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit       = 16M
query_cache_size        = 48M
#
# * 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
#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


[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/

采纳答案by kworr

MySQL is working under it's own user so starting it under root is not a wise decision. And now when you had already tried that some of your files can be owned by root so the service will fail to start.

MySQL 在它自己的用户下工作,所以在 root 下启动它不是一个明智的决定。现在,当您已经尝试过让 root 拥有您的某些文件时,该服务将无法启动。

  • Check that all directory with MySQL database is owned by mysqluser.
  • Try to start service via upstart: start mysql
  • In the directory with MySQL database check the log file.
  • 检查所有包含 MySQL 数据库的目录是否归mysql用户所有。
  • 尝试通过 upstart 启动服务: start mysql
  • 在 MySQL 数据库目录中检查日志文件。

回答by dwjv

Is port 3306 already in use? Try:

端口 3306 是否已被使用?尝试:

netstat -an | grep 3306

Edit: how are you starting MySQL? Try:

编辑:你是如何启动 MySQL 的?尝试:

/etc/init.d/mysql start 

回答by ZhukV

This error often there is if the MySQL cannot work with own directories.

如果 MySQL 无法使用自己的目录,则通常会出现此错误。

In this error you should:

在此错误中,您应该:

  • Check the databases directory (often - /var/lib/mysql)
  • The check directory where mysql store pid file (often - /var/run/mysqld).
  • 检查数据库目录(通常 - /var/lib/mysql
  • mysql 存储 pid 文件的检查目录(通常 - /var/run/mysqld)。

This directory should have a mysql:mysqluser and group (or other, if MySQL runs from other user).

这个目录应该有一个mysql:mysql用户和组(或其他,如果 MySQL 从其他用户运行)。

In your case, the directory /var/run/mysqld/is not writable. You should change the user and group for this directory:

在您的情况下,该目录/var/run/mysqld/不可写。您应该更改此目录的用户和组:

chown mysql:mysql /var/run/mysqld

回答by rubo77

Check permissions of

检查权限

  • /var/lib/mysql
  • /var/run/mysqld

    Those folders have to be owned by user and group mysql.

  • /tmp/

    has to be global writable +t

    chmod 777 /tmp/
    chmod +t /tmp/
    chown root:root /tmp/
    
    $ ls -lahd /tmp/
    
    drwxrwxrwt 7 root root 4,0K Okt 28 22:54 /tmp/
    
  • /var/lib/mysql
  • /var/run/mysqld

    这些文件夹必须归用户和组所有mysql

  • /tmp/

    必须是全局可写的 +t

    chmod 777 /tmp/
    chmod +t /tmp/
    chown root:root /tmp/
    
    $ ls -lahd /tmp/
    
    drwxrwxrwt 7 root root 4,0K Okt 28 22:54 /tmp/