Xampp Error: Mysql Unerwartet beendet.

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

Re: Xampp Error: Mysql Unerwartet beendet.

Postby jstaerk » 11. September 2013 16:04

Hallo,

Gibt es einen Grund warum mir MySQL ab XAMPP 1.8.3 (unter win7 64 bit und einer full-disk-encryption, mit dem XAMPP-installer installiert) innodb-Tabellen reproduzierbar beim Neustart des Rechners zerschießt?

Steps to reproduce:

Situation: Ich habe zwei Datenbanken als .SQL-Dateien, 0.5 und 15 MB groß. Ich installiere ins vorher nicht vorhandene c:\xampp.

Erstens: Ich wähle "Bitnami informationen anzeigen" ab. Bei der Installation erscheint zusätzlich zum Installationsfenster ein leeres, titel- und caretloses schwarzes Konsolenfenster, dass die Prozessliste als conhost.exe ausgibt. Dieses Fenster schließt sich nicht alleine, obwohl sich die Installation wie gewohnt beenden lässt. Es lässt sich jedoch durch Klick auf das Schließen-Icon anstandslos schließen. Es ist auch nach 180s noch zu sehen, ich habe es dann manuell geschlossen.

Zweitens: Ich lasse die XAMPP-Console öffnen und starte MySQL und Apache.

Ich lese meine Datenbank ein indem ich mit dem MySQL-Kommandozeilenclient zwei Datenbanken und einen Nutzer @localhost erstelle, diesem Nutzer alle Rechte auf die Datenbanken gebe und durchflushe. Danach beende ich mysql.exe und importiere die Datenbanken mit c:\xampp\mysql\bin\mysql -u <nutzername> -p --database <datenbank1> < <datenbank1.sql> bzw. c:\xampp\mysql\bin\mysql -u <nutzername> -p --database <datenbank2> < <datenbank2.sql> . Um zu sehen dass alles funktioniert hat kann man hier gern ein c:\xampp\mysql\bin\mysqldump -u root --all-databases durchführen.

Jetzt wirds interessant: Den kompletten Rechner einmal neustarten. Es spielt dabei interessanterweise scheinbar keine Rolle, ob ich MySQL als Service laufen lasse oder nicht und ob ich MySQL über die XAMPP-Konsole vorher sauber runterfahre oder nicht.

Nach dem neustarten des Rechners lässt sich MySQL nicht mehr starten (und startet auch nicht als Service).

Log:

2013-09-11 16:30:43 4728 [Note] Plugin 'FEDERATED' is disabled.
2013-09-11 16:30:43 104c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-09-11 16:30:43 4728 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-11 16:30:43 4728 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-11 16:30:43 4728 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-11 16:30:43 4728 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-11 16:30:43 4728 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-11 16:30:43 4728 [Note] InnoDB: Completed initialization of buffer pool
2013-09-11 16:30:43 4728 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-09-11 16:30:43 4728 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2013-09-11 16:30:43 4728 [Note] InnoDB: Database physically writes the file full: wait...
2013-09-11 16:30:44 4728 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-09-11 16:30:44 4728 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-09-11 16:30:44 4728 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-09-11 16:30:44 4728 [Warning] InnoDB: New log files created, LSN=45781
2013-09-11 16:30:44 4728 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-09-11 16:30:44 4728 [Note] InnoDB: Doublewrite buffer created
2013-09-11 16:30:45 4728 [Note] InnoDB: 128 rollback segment(s) are active.
2013-09-11 16:30:45 4728 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-09-11 16:30:45 4728 [Note] InnoDB: Foreign key constraint system tables created
2013-09-11 16:30:45 4728 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-09-11 16:30:45 4728 [Note] InnoDB: Tablespace and datafile system tables created.
2013-09-11 16:30:45 4728 [Note] InnoDB: Waiting for purge to start
2013-09-11 16:30:45 4728 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-09-11 16:30:45 4728 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: be89318b-1aee-11e3-b27b-b8763fdf14fe.
2013-09-11 16:30:45 4728 [Note] Server hostname (bind-address): '*'; port: 3306
2013-09-11 16:30:45 4728 [Note] IPv6 is available.
2013-09-11 16:30:45 4728 [Note] - '::' resolves to '::';
2013-09-11 16:30:45 4728 [Note] Server socket created on IP: '::'.
2013-09-11 16:30:45 4728 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-09-11 16:30:45 4728 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-09-11 16:30:45 4728 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-09-11 16:30:45 4728 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-09-11 16:30:45 4728 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-09-11 16:30:45 4728 [Note] Event Scheduler: Loaded 0 events
2013-09-11 16:30:45 4728 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2013-09-11 16:34:12 754 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:12 754 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:12 754 InnoDB: Error: Fetch of persistent statistics requested for table "test_nathan"."dbadd" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-09-11 16:34:12 754 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:12 754 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:12 754 InnoDB: Error: Fetch of persistent statistics requested for table "test_nathan"."dbicon" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-09-11 16:34:12 754 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:12 754 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:12 754 InnoDB: Error: Fetch of persistent statistics requested for table "test_nathan"."dbjoin" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-09-11 16:34:12 754 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:12 754 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:12 754 InnoDB: Error: Fetch of persistent statistics requested for table "test_nathan"."dbtable" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-09-11 16:34:12 754 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:12 754 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:12 754 InnoDB: Error: Fetch of persistent statistics requested for table "test_nathan"."dbtablecolumn" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-09-11 16:34:12 754 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:22 1314 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:22 1314 InnoDB: Recalculation of persistent statistics requested for table "test_nathan"."dbicon" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-09-11 16:34:32 1314 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:32 1314 InnoDB: Recalculation of persistent statistics requested for table "test_nathan"."dbtable" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-09-11 16:34:42 1314 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:42 1314 InnoDB: Recalculation of persistent statistics requested for table "test_nathan"."dbadd" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-09-11 16:34:51 4728 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-09-11 16:34:52 1314 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:34:52 1314 InnoDB: Recalculation of persistent statistics requested for table "test_nathan"."dbtablecolumn" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-09-11 16:35:02 1314 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-09-11 16:35:02 1314 InnoDB: Recalculation of persistent statistics requested for table "test_nathan"."dbjoin" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-09-11 16:42:26 4152 [Note] Plugin 'FEDERATED' is disabled.
2013-09-11 16:42:26 1194 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-09-11 16:42:26 4152 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-11 16:42:26 4152 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-11 16:42:26 4152 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-11 16:42:26 4152 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-11 16:42:26 4152 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-11 16:42:26 4152 [Note] InnoDB: Completed initialization of buffer pool
2013-09-11 16:42:26 4152 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-11 16:42:26 4152 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1681112 in the ib_logfiles!
2013-09-11 16:42:26 4152 [Note] InnoDB: Database was not shutdown normally!
2013-09-11 16:42:26 4152 [Note] InnoDB: Starting crash recovery.
2013-09-11 16:42:26 4152 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-11 16:42:27 4152 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd. Cannot open tablespace test_nathan/dbadd which uses space ID: 1 at filepath: .\test_nathan\dbadd.ibd
InnoDB: Error: could not open single-table tablespace file .\test_nathan\dbadd.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.


Wenn ich die IBD-Datei der ersten kaputten Tabelle lösche meldet XAMPP noch eine zweite. Lösche ich auch diese hängt sich MySQL beim starten auf und schreibt auch nix mehr ins log.

Mit XAMPP 1.8.2 funktioniert das ganze übrigens wunderbar.


ciao
Jochen
jstaerk
 
Posts: 1
Joined: 11. September 2013 15:22
XAMPP Version: 5.5.19
Operating System: Win7 64 bit

Previous

Return to XAMPP für Windows

Who is online

Users browsing this forum: No registered users and 17 guests