MySQL Server kann nicht gestartet werden...

Marschl · 14. April 2017

Hallo,

woran kann es liegen dass ich auf meinem vServer MySQL nichtmehr starten kann?

Spoiler anzeigen

Hoffe ihr könnt mir helfen
Grüße

seegras · 14. April 2017

Logfiles wären ein Traum, dir wird quasi der Befehl dafür ins Gesicht geklatscht

journalctl -xn oder direkt mal in /var/log/mysql/mysql.log bzw error.log

Marschl · 14. April 2017

Spoiler anzeigen

Code

170413 11:24:29 [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.
170413 11:24:29 [Note] Plugin 'FEDERATED' is disabled.
170413 11:24:29 InnoDB: The InnoDB memory heap is disabled
170413 11:24:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170413 11:24:29 InnoDB: Compressed tables use zlib 1.2.8
170413 11:24:29 InnoDB: Using Linux native AIO
170413 11:24:29 InnoDB: Initializing buffer pool, size = 128.0M
170413 11:24:29 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
170413 11:24:29  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
170413 11:24:29  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
170413 11:24:29  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
170413 11:24:29  InnoDB: Waiting for the background threads to start
170413 11:24:30 InnoDB: 5.5.54 started; log sequence number 0
170413 11:24:30  InnoDB: Starting shutdown...
170413 11:24:31  InnoDB: Shutdown completed; log sequence number 1595675
170413 11:24:31 [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.
170413 11:24:31 [Note] Plugin 'FEDERATED' is disabled.
170413 11:24:31 InnoDB: The InnoDB memory heap is disabled
170413 11:24:31 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170413 11:24:31 InnoDB: Compressed tables use zlib 1.2.8
170413 11:24:31 InnoDB: Using Linux native AIO
170413 11:24:31 InnoDB: Initializing buffer pool, size = 128.0M
170413 11:24:31 InnoDB: Completed initialization of buffer pool
170413 11:24:31 InnoDB: highest supported file format is Barracuda.
170413 11:24:31  InnoDB: Waiting for the background threads to start
170413 11:24:32 InnoDB: 5.5.54 started; log sequence number 1595675
170413 11:24:32  InnoDB: Starting shutdown...
170413 11:24:33  InnoDB: Shutdown completed; log sequence number 1595675
170413 11:24: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.
170413 11:24:33 [Note] Plugin 'FEDERATED' is disabled.
170413 11:24:33 InnoDB: The InnoDB memory heap is disabled
170413 11:24:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170413 11:24:33 InnoDB: Compressed tables use zlib 1.2.8
170413 11:24:33 InnoDB: Using Linux native AIO
170413 11:24:33 InnoDB: Initializing buffer pool, size = 128.0M
170413 11:24:33 InnoDB: Completed initialization of buffer pool
170413 11:24:33 InnoDB: highest supported file format is Barracuda.
170413 11:24:33  InnoDB: Waiting for the background threads to start
170413 11:24:34 InnoDB: 5.5.54 started; log sequence number 1595675
ERROR: 1064  You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ALTER TABLE user ADD column Show_view_priv enum('N','Y') CHARACTER SET utf8 NOT ' at line 1
170413 11:24:34 [ERROR] Aborting


170413 11:24:34  InnoDB: Starting shutdown...
170413 11:24:35  InnoDB: Shutdown completed; log sequence number 1595675
170413 11:24:35 [Note] /usr/sbin/mysqld: Shutdown complete


170413 11:24:35 [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.
170413 11:24:35 [Note] Plugin 'FEDERATED' is disabled.
170413 11:24:35 InnoDB: The InnoDB memory heap is disabled
170413 11:24:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170413 11:24:35 InnoDB: Compressed tables use zlib 1.2.8
170413 11:24:35 InnoDB: Using Linux native AIO
170413 11:24:35 InnoDB: Initializing buffer pool, size = 128.0M
170413 11:24:35 InnoDB: Completed initialization of buffer pool
170413 11:24:35 InnoDB: highest supported file format is Barracuda.
170413 11:24:35  InnoDB: Waiting for the background threads to start
170413 11:24:36 InnoDB: 5.5.54 started; log sequence number 1595675
170413 11:24:36  InnoDB: Starting shutdown...
170413 11:24:37  InnoDB: Shutdown completed; log sequence number 1595675
170413 11:24:37 [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.
170413 11:24:37 [Note] Plugin 'FEDERATED' is disabled.
170413 11:24:37 InnoDB: The InnoDB memory heap is disabled
170413 11:24:37 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170413 11:24:37 InnoDB: Compressed tables use zlib 1.2.8
170413 11:24:37 InnoDB: Using Linux native AIO
170413 11:24:37 InnoDB: Initializing buffer pool, size = 128.0M
170413 11:24:37 InnoDB: Completed initialization of buffer pool
170413 11:24:37 InnoDB: highest supported file format is Barracuda.
170413 11:24:37  InnoDB: Waiting for the background threads to start
170413 11:24:38 InnoDB: 5.5.54 started; log sequence number 1595675
ERROR: 1050  Table 'plugin' already exists
170413 11:24:38 [ERROR] Aborting


170413 11:24:38  InnoDB: Starting shutdown...
170413 11:24:39  InnoDB: Shutdown completed; log sequence number 1595675
170413 11:24:39 [Note] /usr/sbin/mysqld: Shutdown complete


170413 11:24:39 [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.
170413 11:24:39 [Note] Plugin 'FEDERATED' is disabled.
170413 11:24:39 InnoDB: The InnoDB memory heap is disabled
170413 11:24:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170413 11:24:39 InnoDB: Compressed tables use zlib 1.2.8
170413 11:24:39 InnoDB: Using Linux native AIO
170413 11:24:39 InnoDB: Initializing buffer pool, size = 128.0M
170413 11:24:39 InnoDB: Completed initialization of buffer pool
170413 11:24:39 InnoDB: highest supported file format is Barracuda.
170413 11:24:39  InnoDB: Waiting for the background threads to start
170413 11:24:40 InnoDB: 5.5.54 started; log sequence number 1595675
170413 11:24:40 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170413 11:24:40 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
170413 11:24:40 [Note] Server socket created on IP: '127.0.0.1'.
170413 11:24:40 [Note] Event Scheduler: Loaded 0 events
170413 11:24:40 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.54-0+deb8u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
170414  8:55:19 [Note] /usr/sbin/mysqld: Normal shutdown


170414  8:55:19 [Note] Event Scheduler: Purging the queue. 0 events
170414  8:55:21 [Warning] /usr/sbin/mysqld: Forcing close of thread 578  user: 'root'


170414  8:55:21 [Warning] /usr/sbin/mysqld: Forcing close of thread 577  user: 'root'


170414  8:55:21 [Warning] /usr/sbin/mysqld: Forcing close of thread 576  user: 'root'


170414  8:55:21 [Warning] /usr/sbin/mysqld: Forcing close of thread 575  user: 'root'


170414  8:55:22  InnoDB: Starting shutdown...
170414  8:55:23  InnoDB: Shutdown completed; log sequence number 1793762
170414  8:55:24 [Note] /usr/sbin/mysqld: Shutdown complete

Alles anzeigen

seegras · 14. April 2017

Was hast du vorher damit angestellt? Updates installiert, Backups eingespielt, ist der Server eventuell abgestürzt?

Alf21 · 14. April 2017

Falls du es komplett nicht hinbekommen solltest, backup der Datenbanken holen und der Dateien und neuinstallieren bzw. einfach updaten.
Ich hab bei mir auch Debian8 draufgehabt und die Standardinstallation von MySQL ist die v5.5, wobei es schon viel neuere gibt. Hab deshalb gestern erstmal v5.6 raufgepackt, hat viele Fehler behoben. Btw. hast mal deine Config überprüft? Server komplett neugestartet? Vielleicht hat sich was verhaspelt, ne Instanz mit Port oder so, auch wenns nicht inner Fehlermeldung steht...

Marschl · 14. April 2017

Server schon mehrmals neugestartet...
ich hab eigentlich nicht wirklich was als letztes gemacht. Ich hab bei meinem Script was in die Datenbank eintragen lassen wollte dann schauen und konnte nichtmehr bei phpmyadmin einloggen.

MySQL Server kann nicht gestartet werden...

seegras 27. Oktober 2021

breadfish.de 12. März 2022

Ähnliche Themen

[SAMMELTHREAD] Kleine Scripting Fragen

pRP Edit Download!

MySQL Verbindung kann nicht hergestellt werden