MySql in XAMPP starten

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

MySql in XAMPP starten

Postby juelin » 14. January 2019 20:02

Hallo,
bin neu hier.
Habe XAMPP 7.2.10 auf Windows 10.
Bis gestern lief noch alles ok.
Seit heute kann ich MySql nicht mehr starten.
Fehlermeldung:

Fehler: MySQL wurde unerwartet beendet
20:01:20 [mysql] Ursache könnte ein geblockter Port, fehlende Abhängigkeiten,
20:01:20 [mysql] fehlende Berechtigungen, ein Absturz oder ein Abbruch einer anderen Methode sein.
20:01:20 [mysql] Drücke den Logs Button um error logs zu sehen und prüfe
20:01:20 [mysql] im Windows Event Viewer für weitere Hinweise
20:01:20 [mysql] Wenn du weitere Hilfe benötigst, kopiere den kompletten Inhalt des Log Fensters
20:01:20 [mysql] und füge ihn als Ergänzung in einem neuen Forum Eintrag hinzu.


Logfile:

2019-01-14 20:01:18 24b0 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.
2019-01-14 20:01:18 9392 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-01-14 20:01:18 9392 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-01-14 20:01:18 9392 [Note] InnoDB: The InnoDB memory heap is disabled
2019-01-14 20:01:18 9392 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-01-14 20:01:18 9392 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-01-14 20:01:18 9392 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-01-14 20:01:18 9392 [Note] InnoDB: Using generic crc32 instructions
2019-01-14 20:01:18 9392 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-01-14 20:01:18 9392 [Note] InnoDB: Completed initialization of buffer pool
2019-01-14 20:01:18 9392 [Note] InnoDB: Highest supported file format is Barracuda.
2019-01-14 20:01:18 9392 [Note] InnoDB: The log sequence number 9307614 in ibdata file do not match the log sequence number 9307624 in the ib_logfiles!
2019-01-14 20:01:18 9392 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bibhefig/figur uses space ID: 31 at filepath: .\bibhefig\figur.ibd. Cannot open tablespace lotto/spielarchiv which uses space ID: 31 at filepath: .\lotto\spielarchiv.ibd
InnoDB: Error: could not open single-table tablespace file .\lotto\spielarchiv.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.
190114 20:01:18 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.1.36-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787136 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlAreBitsSet()
ntdll.dll!RtlAreBitsSet()
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.



Kann jemand helfen?


Danke und Gruß

Jürgen
juelin
 
Posts: 4
Joined: 14. January 2019 19:53
XAMPP version: 7.2.10
Operating System: Windows 10

Re: MySql in XAMPP starten

Postby Nobbie » 15. January 2019 12:46

Die InnoDB Datenbank ist kaputt, meistens als Folge von unkonrolliertem Ausschalten des PCs, ohne vorher MySQL ordentlich im Xampp Dialog herunterzufahren. Alternativ kann die Festplatte defekt sein.

Im Log steht ja eine ausführliche Erklärung und Anleitung, wie man vorgehen soll. Hast Du die Schritte ausgeführt? Hier noch einmal die Erklärungen:

InnoDB: Error: could not open single-table tablespace file .\lotto\spielarchiv.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.
190114 20:01:18 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Nobbie
 
Posts: 11091
Joined: 09. March 2008 13:04

Re: MySql in XAMPP starten

Postby juelin » 15. January 2019 17:22

Schritt 1 und 2 bringen nix.
Schritt 3: File my.cnf nicht vorhanden.

Gruß
Jürgen
juelin
 
Posts: 4
Joined: 14. January 2019 19:53
XAMPP version: 7.2.10
Operating System: Windows 10

Re: MySql in XAMPP starten

Postby juelin » 15. January 2019 17:30

Habe die Datenbank Lotto aus MySql/Data rausgenommen.
Jetzt läuft MySql wieder.
gibt es eine Möglichkeit die Tabellen wieder herzustellen?
Gruß
Jürgen
juelin
 
Posts: 4
Joined: 14. January 2019 19:53
XAMPP version: 7.2.10
Operating System: Windows 10

Re: MySql in XAMPP starten

Postby Altrea » 15. January 2019 17:54

Vielleicht...
wenn die defekte Datenbank wieder in Mariadb drin ist und Mariadb mit innodb_force_recovery höher 0 gestartet wird.
Ich würde empfehlen innodb_force_recovery in der my.ini erstmal auf 4 zu stellen. Startet Mariadb dann, solltest du schleunigst einen Datenbankdump der defekten Datenbank machen. Startet Mariadb nicht kann man es auch mit noch höheren Werten probieren, 4 ist aber meist ausreichend.

Hast du einen dump stoppst du Mariadb wieder, stellst
innodb_force_recovery wieder auf 0 und entfernst die defekte Datenbank wieder. Dann Mariadb wieder starten und aus dem Dump eine neue saubere Datenbank wiederherstellen
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 9760
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

Re: MySql in XAMPP starten

Postby juelin » 15. January 2019 18:45

Danke,
Datenbank ist leider nicht mehr zu retten,
aber Hauptsache MySql läuft wieder.
Gruß
Jürgen
juelin
 
Posts: 4
Joined: 14. January 2019 19:53
XAMPP version: 7.2.10
Operating System: Windows 10


Return to XAMPP für Windows

Who is online

Users browsing this forum: No registered users and 21 guests