Question

我在网络上的许多论坛中找到了，但我找不到我的解决方案。当我在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

我已经获得了mysql文件夹的权限，我也尝试为root mysql创建一个新密码。但到目前为止还没有任何效果。

感谢您的帮助。

一些信息：

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

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

Answer 1

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

检查所有带有MySQL数据库的目录是否由mysql用户拥有。
尝试通过暴发户开始服务：start mysql
在MySQL数据库的目录中检查日志文件。

Answer 2

端口3306是否已被使用？尝试：

netstat -an | grep 3306

编辑：你是如何开始MySQL的？尝试：

/etc/init.d/mysql start

Answer 3

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

在此错误中，您应该：

检查数据库目录（通常-/var/lib/mysql）
mysql存储pid文件的检查目录（通常-/var/run/mysqld）。

此目录应具有一个mysql:mysql用户和组（如果MySQL是从其他用户运行的，则为其他用户和组）。

对于您来说，目录/var/run/mysqld/是不可写的。您应该更改此目录的用户和组：

chown mysql:mysql /var/run/mysqld

Answer 4

检查

的权限

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

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

4 个答案: