XAMPP 1.7.4 MySQL started nicht mehr

Irgendwelche Probleme mit XAMPP für Windows? Dann ist hier genau der richtige Ort um nachzufragen.

XAMPP 1.7.4 MySQL started nicht mehr

Postby Ottilie » 04. April 2014 16:49

Hallo zusammen,

bisher lief MySQL bei mir problemlos, seit heute startet es nicht mehr.
Ich verwende XAMPP 1.7.4 unter Windows 7.
Apache startet problemlos auf Port 80, bei MySQL steht MySQL started[Port 3306] und das war's es wird nicht wirlich gestartet. Mit localhost kann ich die korrekte Startseite aufrufen, Klicke ich auf phpMyAdmin kommt
Fehler

MySQL meldet:
#2002 - Der Server antwortet nicht. (evtl. ist auch der Socket des lokalen MySQL-Servers socket nicht korrekt konfiguriert)
Verbindung für den controluser, wie er in Ihrer Konfiguration angegeben ist, ist fehlgeschlagen.
Wie kommt das?

Welche Möglichkeiten habe ich jetzt das Ganze wieder ans Laufen zu bringen?

Gruß

Ottilie
Ottilie
 
Posts: 8
Joined: 20. February 2011 20:09

Re: XAMPP 1.7.4 MySQL started nicht mehr

Postby Nobbie » 05. April 2014 10:51

Ottilie wrote:Wie kommt das?

Welche Möglichkeiten habe ich jetzt das Ganze wieder ans Laufen zu bringen?


Indem Du die Ursache findest. Nur mit dieser Meldung kann hier niemand irgendetwas dazu sagen, das ist wie "mein Fernseher geht nicht an, was muss ich machen". Es gibt zu MySQL eine Logdatei, wo Fehler usw. protokolliert werden. Unter Windows befindet sich diese Datei im data Verzeichnis und hat den Namen mysql_error.log. Schaue dort mit einem Editor (Notepad o.ä.) hinein und/oder kopiere die letzten 50 Zeilen hier in das Forum.
Nobbie
 
Posts: 8783
Joined: 09. March 2008 13:04

Re: XAMPP 1.7.4 MySQL started nicht mehr

Postby   » 06. April 2014 20:28

Habe die selbe Meldung beim ersten Start von mySQL bekommen.
In meinem Log steht:
140404 17:47:21 [Note] Plugin 'FEDERATED' is disabled.
140404 17:47:22 InnoDB: The InnoDB memory heap is disabled
140404 17:47:22 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140404 17:47:22 InnoDB: Compressed tables use zlib 1.2.3
140404 17:47:22 InnoDB: Initializing buffer pool, size = 16.0M
140404 17:47:22 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist:
InnoDB: a new database to be created!
140404 17:47:22 InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
140404 17:47:22 InnoDB: Log file C:\xampp\mysql\data\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
140404 17:47:23 InnoDB: Log file C:\xampp\mysql\data\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file C:\xampp\mysql\data\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
140404 17:47:24 InnoDB: Waiting for the background threads to start
140404 17:47:25 InnoDB: 1.1.8 started; log sequence number 0
140404 17:47:27 [Note] Event Scheduler: Loaded 0 events
140404 17:47:27 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.16' socket: '' port: 3306 MySQL Community Server (GPL)
140404 18:53:41 [Note] Plugin 'FEDERATED' is disabled.
140404 18:53:41 InnoDB: The InnoDB memory heap is disabled
140404 18:53:41 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140404 18:53:41 InnoDB: Compressed tables use zlib 1.2.3
140404 18:53:41 InnoDB: Initializing buffer pool, size = 16.0M
140404 18:53:41 InnoDB: Completed initialization of buffer pool
140404 18:53:41 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140404 18:53:41 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140404 18:53:42 InnoDB: Waiting for the background threads to start
140404 18:53:43 InnoDB: 1.1.8 started; log sequence number 1595675
140404 18:53:44 [Note] Event Scheduler: Loaded 0 events
140404 18:53:44 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.16' socket: '' port: 3306 MySQL Community Server (GPL)
140404 18:54:54 [Note] Plugin 'FEDERATED' is disabled.
140404 18:54:54 InnoDB: The InnoDB memory heap is disabled
140404 18:54:54 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140404 18:54:54 InnoDB: Compressed tables use zlib 1.2.3
140404 18:54:54 InnoDB: Initializing buffer pool, size = 16.0M
140404 18:54:54 InnoDB: Completed initialization of buffer pool
140404 18:54:54 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140404 18:54:54 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140404 18:54:54 InnoDB: Waiting for the background threads to start
140404 18:54:55 InnoDB: 1.1.8 started; log sequence number 1595675
140404 18:54:55 [Note] Event Scheduler: Loaded 0 events
140404 18:54:55 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.16' socket: '' port: 3306 MySQL Community Server (GPL)
140404 21:49:00 [Note] Plugin 'FEDERATED' is disabled.
140404 21:49:01 InnoDB: The InnoDB memory heap is disabled
140404 21:49:01 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140404 21:49:01 InnoDB: Compressed tables use zlib 1.2.3
140404 21:49:01 InnoDB: Initializing buffer pool, size = 16.0M
140404 21:49:01 InnoDB: Completed initialization of buffer pool
140404 21:49:01 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140404 21:49:01 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140404 21:49:02 InnoDB: Waiting for the background threads to start
140404 21:49:03 InnoDB: 1.1.8 started; log sequence number 1595675
140404 21:49:05 [Note] Event Scheduler: Loaded 0 events
140404 21:49:05 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.16' socket: '' port: 3306 MySQL Community Server (GPL)
140404 21:52:19 [Note] Plugin 'FEDERATED' is disabled.
140404 21:52:19 InnoDB: The InnoDB memory heap is disabled
140404 21:52:19 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140404 21:52:19 InnoDB: Compressed tables use zlib 1.2.3
140404 21:52:19 InnoDB: Initializing buffer pool, size = 16.0M
140404 21:52:19 InnoDB: Completed initialization of buffer pool
140404 21:52:19 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140404 21:52:19 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140404 21:52:21 InnoDB: Waiting for the background threads to start
140404 21:52:22 InnoDB: 1.1.8 started; log sequence number 1595675
140404 21:52:22 [Note] Event Scheduler: Loaded 0 events
140404 21:52:22 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.16' socket: '' port: 3306 MySQL Community Server (GPL)
140404 21:54:20 [Note] Plugin 'FEDERATED' is disabled.
140404 21:54:20 InnoDB: The InnoDB memory heap is disabled
140404 21:54:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140404 21:54:20 InnoDB: Compressed tables use zlib 1.2.3
140404 21:54:20 InnoDB: Initializing buffer pool, size = 16.0M
140404 21:54:20 InnoDB: Completed initialization of buffer pool
140404 21:54:20 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140404 21:54:20 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140404 21:54:21 InnoDB: Waiting for the background threads to start
140404 21:54:22 InnoDB: 1.1.8 started; log sequence number 1595675
140404 21:54:22 [Note] Event Scheduler: Loaded 0 events
140404 21:54:22 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.16' socket: '' port: 3306 MySQL Community Server (GPL)

Im Statusfenster von xampp steht:
XAMPP Control Panel Version 2.5 (16. Maxch, 2011)
Wind- 6-0 Build 6001 Platfomn 2 Service Pack 1
Current Directory: c:\xampp
Install(er) Directory: c:\xampp
WARN:This program must be rum from your XAMPP root. directory.
INFO:Perhaps this program running on a 64 bit plattfom please ignore the mssage above.
Busy...
MySql started [Port 3306]
XAMPP Application Status 1.1.2.2
httpd State 1 Service 0 Start 0 Thread 0 Op 0 Port 80
mysql State 1 Service 0 Start 0 Thread 10c Op 0 Port 3306
ftp State 0 Service 0 Start 0 Thread 0 Op 0 Port 21
mercury State 0 Service 0 Start 0 Thread 0 Op 0 Port 25
java State 0 S-ice 0 Start 0 Thread 0 Op 0 Port 8080
 
 
Posts: 2
Joined: 06. April 2014 20:01
Operating System: Win 6 Vista

Re: XAMPP 1.7.4 MySQL started nicht mehr

Postby Ottilie » 08. April 2014 07:36

Nobbie wrote:
Ottilie wrote:Wie kommt das?

Welche Möglichkeiten habe ich jetzt das Ganze wieder ans Laufen zu bringen?


Indem Du die Ursache findest. Nur mit dieser Meldung kann hier niemand irgendetwas dazu sagen, das ist wie "mein Fernseher geht nicht an, was muss ich machen". Es gibt zu MySQL eine Logdatei, wo Fehler usw. protokolliert werden. Unter Windows befindet sich diese Datei im data Verzeichnis und hat den Namen mysql_error.log. Schaue dort mit einem Editor (Notepad o.ä.) hinein und/oder kopiere die letzten 50 Zeilen hier in das Forum.


Hallo Nobbie,

vielen Dank für Deinen Hinweis. Ich habe mir das error_log angeschaut und bin nicht schlau darau geworden, hier nun die ersten 50 Zeilen:
110810 13:25:38 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use Windows interlocked functions
InnoDB: Compressed tables use zlib 1.2.3
110810 13:25:39 InnoDB: Initializing buffer pool, size = 16.0M
110810 13:25:39 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist:
InnoDB: a new database to be created!
110810 13:25:39 InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
110810 13:25:39 InnoDB: Log file C:\xampp\mysql\data\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
110810 13:25:39 InnoDB: Log file C:\xampp\mysql\data\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file C:\xampp\mysql\data\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
110810 13:25:40 InnoDB: 1.1.4 started; log sequence number 0
110810 13:25:40 [Note] Event Scheduler: Loaded 0 events
110810 13:25:40 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.8' socket: '' port: 3306 MySQL Community Server (GPL)
110810 13:42:43 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use Windows interlocked functions
InnoDB: Compressed tables use zlib 1.2.3
110810 13:42:43 InnoDB: Initializing buffer pool, size = 16.0M
110810 13:42:43 InnoDB: Completed initialization of buffer pool
110810 13:42:44 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
110810 13:42:44 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
110810 13:42:44 InnoDB: 1.1.4 started; log sequence number 1595675
110810 13:42:44 [Note] Event Scheduler: Loaded 0 events
110810 13:42:44 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.8' socket: '' port: 3306 MySQL Community Server (GPL)
110810 18:41:38 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use Windows interlocked functions
InnoDB: Compressed tables use zlib 1.2.3
110810 18:41:38 InnoDB: Initializing buffer pool, size = 16.0M
110810 18:41:38 InnoDB: Completed initialization of buffer pool
110810 18:41:38 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
110810 18:41:38 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...

Am Samstag habe ich die Datei Data zur Sicherheit kopiert und wieder eingespielt. Seither kann ich die Datenbanken wieder aufrufen, und die meisten Anwendungen funktionieren auch wieder. Lediglich mit der Wordpress-Mulitsite gibt es Probleme: Die Unterseiten können nicht mehr aufgerufen werden, Error 404. Dabei ist der Pfad zur Datei localhost/wordpress/subdomain korrekt, d.h. vorher lief es unter diesem Pfad. Soll ich das alte Logfile auch noch senden?

Dia andere Alternative wäre XAMPP zu aktualisieren/neu aufzusetzen. Dabei möchte ich vor allem die Datenbanken mitnehmen und die unter htdocs angelegten Dateien. Wie stelle ich das am geschicktesten an?

Gruß

Ottilie
Ottilie
 
Posts: 8
Joined: 20. February 2011 20:09

Re: XAMPP 1.7.4 MySQL started nicht mehr

Postby Nobbie » 08. April 2014 09:41

Ottilie wrote:hier nun die ersten 50 Zeilen:


Auch schön, fange ich nur nichts mit an, ich schrieb "die letzten" und nicht "die ersten" 50 Zeilen (s.o.). Ich bin auf dem Sprung in den Urlaub, das wird wohl dann eine Weile dauern.
Nobbie
 
Posts: 8783
Joined: 09. March 2008 13:04

Re: XAMPP 1.7.4 MySQL started nicht mehr

Postby Ottilie » 08. April 2014 11:21

Hallo Nobbie,

sorry, lesen sollte der Mensch können.
Hier nun die letzten Zeilen:
nnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use Windows interlocked functions
InnoDB: Compressed tables use zlib 1.2.3
140407 20:53:34 InnoDB: Initializing buffer pool, size = 16.0M
140407 20:53:34 InnoDB: Completed initialization of buffer pool
140407 20:53:34 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140407 20:53:35 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140407 20:53:41 InnoDB: 1.1.4 started; log sequence number 1522871714
140407 20:53:41 [Note] Event Scheduler: Loaded 0 events
140407 20:53:41 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.8' socket: '' port: 3306 MySQL Community Server (GPL)
140408 8:22:43 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use Windows interlocked functions
InnoDB: Compressed tables use zlib 1.2.3
140408 8:22:43 InnoDB: Initializing buffer pool, size = 16.0M
140408 8:22:43 InnoDB: Completed initialization of buffer pool
140408 8:22:43 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140408 8:22:43 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140408 8:22:46 InnoDB: 1.1.4 started; log sequence number 1524016278
140408 8:22:46 [Note] Event Scheduler: Loaded 0 events
140408 8:22:46 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.8' socket: '' port: 3306 MySQL Community Server (GPL)
140408 9:14:03 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use Windows interlocked functions
InnoDB: Compressed tables use zlib 1.2.3
140408 9:14:03 InnoDB: Initializing buffer pool, size = 16.0M
140408 9:14:03 InnoDB: Completed initialization of buffer pool
140408 9:14:03 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140408 9:14:03 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140408 9:14:06 InnoDB: 1.1.4 started; log sequence number 1524249200
140408 9:14:06 [Note] Event Scheduler: Loaded 0 events
140408 9:14:06 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.8' socket: '' port: 3306 MySQL Community Server (GPL)

Dank für Deine Mühe und schönen Urlaub.
Gruß

Ottilie
Ottilie
 
Posts: 8
Joined: 20. February 2011 20:09

Re: XAMPP 1.7.4 MySQL started nicht mehr

Postby   » 06. June 2014 19:34

Gibt es für das Problem eine Lösung?
 
 
Posts: 2
Joined: 06. April 2014 20:01
Operating System: Win 6 Vista


Return to XAMPP für Windows

Who is online

Users browsing this forum: No registered users and 13 guests