Mysql Service startet nicht

[Hal9000]

Habe kürzlich unseren Debian 7.0 Server neu aufgesetzt, bekomme aber den Mysql Server nicht zum Laufen.

Mysql auf das jungfräuliche System habe ich installiert mit

apt-get install mysql-server

Danach:

/etc/init.d/mysql start
was aber prompt scheitert (gibt nur 'failed' aus).

Ein

mysqld start

ergibt folgende Meldung:

140604 10:07:26 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
140604 10:07:26 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140604 10:07:26 [Note] Plugin 'FEDERATED' is disabled.
mysqld: Table 'mysql.plugin' doesn't exist
140604 10:07:26 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
140604 10:07:26 InnoDB: The InnoDB memory heap is disabled
140604 10:07:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140604 10:07:26 InnoDB: Compressed tables use zlib 1.2.7
140604 10:07:26 InnoDB: Using Linux native AIO
140604 10:07:26 InnoDB: Initializing buffer pool, size = 128.0M
140604 10:07:26 InnoDB: Completed initialization of buffer pool
140604 10:07:26 InnoDB: highest supported file format is Barracuda.
140604 10:07:26 InnoDB: Waiting for the background threads to start
140604 10:07:27 InnoDB: 5.5.37 started; log sequence number 1595675
mysqld: Too many arguments (first extra is 'start').
Use --verbose --help to get a list of available options
140604 10:07:27 [ERROR] Aborting

140604 10:07:27 InnoDB: Starting shutdown...
140604 10:07:28 InnoDB: Shutdown completed; log sequence number 1595675
140604 10:07:28 [Note] mysqld: Shutdown complete

mysql.error und mysql.log sind beide leer.

Die letzten 20 Zeilen der syslog sehen wie folgt aus:


Jun 4 10:08:01 rs203047 mysqld: 140604 10:08:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jun 4 10:08:01 rs203047 mysqld: 140604 10:08:01 InnoDB: Compressed tables use zlib 1.2.7
Jun 4 10:08:01 rs203047 mysqld: 140604 10:08:01 InnoDB: Using Linux native AIO
Jun 4 10:08:01 rs203047 mysqld: 140604 10:08:01 InnoDB: Initializing buffer pool, size = 128.0M
Jun 4 10:08:01 rs203047 mysqld: 140604 10:08:01 InnoDB: Completed initialization of buffer pool
Jun 4 10:08:01 rs203047 mysqld: 140604 10:08:01 InnoDB: highest supported file format is Barracuda.
Jun 4 10:08:01 rs203047 mysqld: 140604 10:08:01 InnoDB: Waiting for the background threads to start
Jun 4 10:08:02 rs203047 mysqld: 140604 10:08:02 InnoDB: 5.5.37 started; log sequence number 1595675
Jun 4 10:08:02 rs203047 mysqld: 140604 10:08:02 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
Jun 4 10:08:02 rs203047 mysqld: 140604 10:08:02 [Note] - '127.0.0.1' resolves to '127.0.0.1';
Jun 4 10:08:02 rs203047 mysqld: 140604 10:08:02 [Note] Server socket created on IP: '127.0.0.1'.
Jun 4 10:08:02 rs203047 mysqld: 140604 10:08:02 [ERROR] Can't start server : Bind on unix socket: Permission denied
Jun 4 10:08:02 rs203047 mysqld: 140604 10:08:02 [ERROR] Do you already have another mysqld server running on socket: /var/run/mysqld/mysqld.sock ?
Jun 4 10:08:02 rs203047 mysqld: 140604 10:08:02 [ERROR] Aborting
Jun 4 10:08:02 rs203047 mysqld:
Jun 4 10:08:02 rs203047 mysqld: 140604 10:08:02 InnoDB: Starting shutdown...
Jun 4 10:08:03 rs203047 mysqld: 140604 10:08:03 InnoDB: Shutdown completed; log sequence number 1595675
Jun 4 10:08:03 rs203047 mysqld: 140604 10:08:03 [Note] /usr/sbin/mysqld: Shutdown complete
Jun 4 10:08:03 rs203047 mysqld:
Jun 4 10:08:03 rs203047 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended

Folgende (erfolglosen) Versuche nach Einsatz von Google habe ich unternommen:

1) /tmp Rechte testweise auf 777 gesetzt
2) Eigentümer und Gruppe von /var/lib/mysql auf mysql gesetzt
3) basedir in my.cnf auskommentiert
4) bind-address in my.cnf durch Server IP ersetzt
5) Neuinstallation von Mysql (apt-get --purge remove mysql-server)

Die /etc/mysql/my.cnf sieht so aus:

[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0
[mysqld]
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
bind-address = 127.0.0.1
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8
myisam-recover = BACKUP
query_cache_limit = 1M
query_cache_size = 16M
expire_logs_days = 10
max_binlog_size = 100M
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
[mysql]
[isamchk]
key_buffer = 16M
!includedir /etc/mysql/conf.d/

var mein_Latein = "am Ende";

[stefaan]

Seruvs,


Jun 4 10:08:02 rs203047 mysqld: 140604 10:08:02 [ERROR] Do you already have another mysqld server running on socket: /var/run/mysqld/mysqld.sock ?

Sollte dir einen Lösungshinweis geben. Entweder stimmen die Rechte nicht oder das Socket ist schon belegt...

Was sagt ein

dpkg -l | grep mysql?

Grüße, Stefan

[Hal9000]

Hi Stefan,

die Lösung versteckte sich (mal wieder) an einem Ort, wo man sie nicht vermutet, nämlich:

1) in /var/lib/mysql die beiden Dateien ib_logfile0 und ib_logfile1 löschen
2) /etc/init.d/mysql start
3) mysql_secure_installation

Trotzdem danke!

- Hal.

EDIT:
Diese Lösung sollte tunlichst nur mit einem frischen System probiert werden, nicht wenn ein ähnlicher Fehler bei einem Upgrade von Mysql auftritt und somit alte Daten vorhanden sind.