MySQL Server startet nicht

Einrichten des lokalen Netzes, Verbindung zu anderen Computern und Diensten.
Antworten
Felix5566
Beiträge: 3
Registriert: 28.07.2017 01:23:52

MySQL Server startet nicht

Beitrag von Felix5566 » 28.07.2017 01:38:14

Das kommt wenn ich den starten möchte:
/etc/init.d/mysql start
[....] Starting mysql (via systemctl): mysql.serviceJob for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details.
failed!
Das kommt dann wenn ich systemctl status mysql.service mache:
● mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql)
Active: failed (Result: exit-code) since Fr 2017-07-28 01:29:03 CEST; 2min 56s ago
Process: 6557 ExecStop=/etc/init.d/mysql stop (code=exited, status=0/SUCCESS)
Process: 10360 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)

Jul 28 01:29:03 g203 mysql[10360]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Jul 28 01:29:03 g203 systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 28 01:29:03 g203 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jul 28 01:29:03 g203 systemd[1]: Unit mysql.service entered failed state.
Und wenn ich journalctl -xn mach kommt das:
-- Logs begin at Sa 2017-05-20 00:39:01 CEST, end at Fr 2017-07-28 01:34:10 CEST. --
Jul 28 01:32:01 g203 CRON[11159]: pam_unix(cron:session): session closed for user bot
Jul 28 01:33:01 g203 CRON[11168]: pam_unix(cron:session): session opened for user bot by (uid=0)
Jul 28 01:33:01 g203 CRON[11169]: (bot) CMD (/var/tmp/ /update >/dev/null 2>&1)
Jul 28 01:33:01 g203 CRON[11168]: pam_unix(cron:session): session closed for user bot
Jul 28 01:34:01 g203 CRON[11175]: pam_unix(cron:session): session opened for user bot by (uid=0)
Jul 28 01:34:01 g203 CRON[11176]: (bot) CMD (/var/tmp/ /update >/dev/null 2>&1)
Jul 28 01:34:01 g203 CRON[11175]: pam_unix(cron:session): session closed for user bot
Jul 28 01:34:08 g203 sshd[7705]: pam_unix(sshd:session): session closed for user root
Jul 28 01:34:10 g203 sshd[11178]: Accepted password for root from 95.91.225.201 port 52476 ssh2
Jul 28 01:34:10 g203 sshd[11178]: pam_unix(sshd:session): session opened for user root by (uid=0)
Ich bitte um Hilfe ich verzweifel bereitz.

Mit freundlich grüßen:
Felix5566

DeletedUserReAsG

Re: MySQL Server startet nicht

Beitrag von DeletedUserReAsG » 28.07.2017 06:07:43

In deinem Logauszug fehlen leider schon die Zeilen für die Zeit, in der der Fehler aufgetreten ist. Die mit dem Fehler zusammenhängenden Einträge sollten in der Ausgabe von ›journalctl --unit mysql‹ zu finden sein. Zudem sollte es /var/log/mysql/error.log geben, wo ebenfalls Hinweise auf den Fehler zu finden sein könnten.

Infos zum eingesetzten System sind auch immer eine gute Idee.

Felix5566
Beiträge: 3
Registriert: 28.07.2017 01:23:52

Re: MySQL Server startet nicht

Beitrag von Felix5566 » 28.07.2017 10:26:12

Daten zu dem System:
Linux / Debian 8.8

Das sind die Informationen aus journalctl --unit mysql:
Jul 28 00:52:39 g203 systemd[1]: Unit mysql.service entered failed state.
Jul 28 00:53:03 g203 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jul 28 00:53:03 g203 mysql[7279]: /etc/init.d/mysql: ERROR: The partition with /var/lib/mysql is too full! ... failed!
Jul 28 00:53:03 g203 systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 28 00:53:03 g203 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jul 28 00:53:03 g203 systemd[1]: Unit mysql.service entered failed state.
Jul 28 00:55:40 g203 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jul 28 00:55:40 g203 mysql[7401]: /etc/init.d/mysql: ERROR: The partition with /var/lib/mysql is too full! ... failed!
Jul 28 00:55:40 g203 systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 28 00:55:40 g203 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jul 28 00:55:40 g203 systemd[1]: Unit mysql.service entered failed state.
Jul 28 00:59:36 g203 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jul 28 00:59:36 g203 mysql[7515]: /etc/init.d/mysql: ERROR: The partition with /var/lib/mysql is too full! ... failed!
Jul 28 00:59:36 g203 systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 28 00:59:36 g203 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jul 28 00:59:36 g203 systemd[1]: Unit mysql.service entered failed state.
Jul 28 01:00:25 g203 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jul 28 01:00:25 g203 mysql[7583]: /etc/init.d/mysql: ERROR: The partition with /var/lib/mysql is too full! ... failed!
Jul 28 01:00:25 g203 systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 28 01:00:25 g203 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jul 28 01:00:25 g203 systemd[1]: Unit mysql.service entered failed state.
Jul 28 01:10:13 g203 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jul 28 01:10:44 g203 mysql[7785]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Jul 28 01:10:44 g203 systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 28 01:10:44 g203 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jul 28 01:10:44 g203 systemd[1]: Unit mysql.service entered failed state.
Und
Jul 28 01:10:13 g203 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jul 28 01:10:44 g203 mysql[7785]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Jul 28 01:10:44 g203 systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 28 01:10:44 g203 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jul 28 01:10:44 g203 systemd[1]: Unit mysql.service entered failed state.
Jul 28 01:13:02 g203 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jul 28 01:13:32 g203 mysql[8596]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Jul 28 01:13:32 g203 systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 28 01:13:32 g203 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jul 28 01:13:32 g203 systemd[1]: Unit mysql.service entered failed state.
Jul 28 01:13:39 g203 systemd[1]: Stopped LSB: Start and stop the mysql database server daemon.
Jul 28 01:13:41 g203 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jul 28 01:14:12 g203 mysql[9414]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Jul 28 01:14:12 g203 systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 28 01:14:12 g203 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jul 28 01:14:12 g203 systemd[1]: Unit mysql.service entered failed state.
Jul 28 01:28:33 g203 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jul 28 01:29:03 g203 mysql[10360]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Jul 28 01:29:03 g203 systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 28 01:29:03 g203 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jul 28 01:29:03 g203 systemd[1]: Unit mysql.service entered failed state.
Jul 28 01:59:58 g203 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jul 28 02:00:29 g203 mysql[11491]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Jul 28 02:00:29 g203 systemd[1]: mysql.service: control process exited, code=exited status=1
Jul 28 02:00:29 g203 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jul 28 02:00:29 g203 systemd[1]: Unit mysql.service entered failed state.
Das mit den /var/lib/mysql is too full! bedeitet des der Server keinen Speicher mehr hat. Wenn das stimmt ist es schon behoben.

Und in der Error Log datei steht:
170728 1:13:42 [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.
170728 1:13:42 [Note] Plugin 'FEDERATED' is disabled.
170728 1:13:42 InnoDB: The InnoDB memory heap is disabled
170728 1:13:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170728 1:13:42 InnoDB: Compressed tables use zlib 1.2.8
170728 1:13:42 InnoDB: Using Linux native AIO
170728 1:13:42 InnoDB: Initializing buffer pool, size = 128.0M
170728 1:13:42 InnoDB: Completed initialization of buffer pool
170728 1:13:42 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ib_logfile0
InnoDB: File operation call: 'open'.
InnoDB: Cannot continue operation.
170728 1:28:33 [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.
170728 1:28:33 [Note] Plugin 'FEDERATED' is disabled.
170728 1:28:33 InnoDB: The InnoDB memory heap is disabled
170728 1:28:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170728 1:28:33 InnoDB: Compressed tables use zlib 1.2.8
170728 1:28:33 InnoDB: Using Linux native AIO
170728 1:28:33 InnoDB: Initializing buffer pool, size = 128.0M
170728 1:28:33 InnoDB: Completed initialization of buffer pool
170728 1:28:33 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ib_logfile0
InnoDB: File operation call: 'open'.
InnoDB: Cannot continue operation.
170728 1:59:58 [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.
170728 1:59:58 [Note] Plugin 'FEDERATED' is disabled.
170728 1:59:58 InnoDB: The InnoDB memory heap is disabled
170728 1:59:58 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170728 1:59:58 InnoDB: Compressed tables use zlib 1.2.8
170728 1:59:58 InnoDB: Using Linux native AIO
170728 1:59:58 InnoDB: Initializing buffer pool, size = 128.0M
170728 1:59:58 InnoDB: Completed initialization of buffer pool
170728 1:59:58 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ib_logfile0
InnoDB: File operation call: 'open'.
InnoDB: Cannot continue operation.
Mit freundlichen grüßen:
Felix5566

schwedenmann
Beiträge: 5528
Registriert: 30.12.2004 15:31:07
Wohnort: Wegberg

Re: MySQL Server startet nicht

Beitrag von schwedenmann » 28.07.2017 10:33:14

Hallo

liegt wohl hieran:
Jul 28 00:53:03 g203 mysql[7279]: /etc/init.d/mysql: ERROR: The partition with /var/lib/mysql is too full! ... failed!
mfg
schwedenmann

DeletedUserReAsG

Re: MySQL Server startet nicht

Beitrag von DeletedUserReAsG » 28.07.2017 10:51:41

Ist schon behoben, schrieb er. Wenn er nun noch die kaputten Rechte der Datei fixt, solle es auch wieder hochkommen.

Felix5566
Beiträge: 3
Registriert: 28.07.2017 01:23:52

Re: MySQL Server startet nicht

Beitrag von Felix5566 » 28.07.2017 14:47:04

Ja der Fehler ist behoben, nachdem ich die Datei ib_logfile0 auf meinem PC geladen habe und vom Server gelöscht und wieder drauf geladen habe hatte ich vergessen die Permissions wieder zu geben.

Danke für die Hilfe :D

Antworten