Ich kann MySQL unter Linux nicht starten - Fehler mysqld_safe

Question

Ich fand in vielen Foren im Internet, aber ich habe meine Lösung nicht gefunden. Wenn ich den Dienst mysql in Linux Ubuntu Server 12.04 starten, ich diesen Fehler:

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 

ich bereits die Erlaubnis zu dem Ordner, mysql gegeben habe, habe ich auch versucht, ein neues Passwort für den Root-mysql zu erstellen . Aber bisher hat nichts funktioniert.

Danke für Hilfe.

Einige Informationen:

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 

Die /etc/mysql/my.cnf Datei

# 
# 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 arbeitet unter seinem eigenen Benutzer, so dass es unter root starten ist keine weise Entscheidung. Und jetzt, wenn Sie bereits versucht haben, dass einige Ihrer Dateien im Besitz von root sein können, wird der Dienst nicht gestartet.

• Überprüfen Sie, ob das gesamte Verzeichnis mit der MySQL-Datenbank dem Benutzer mysql gehört.
• Versuchen Sie, über Upstart den Dienst zu starten: start mysql
• Im Verzeichnis mit MySQL-Datenbank überprüfen Sie die Protokolldatei.

Answer 2

Ist Port 3306 bereits im Einsatz? Versuchen Sie:

netstat -an | grep 3306 

Edit: Wie starten Sie MySQL? Versuchen Sie: