MySQL startet nicht

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

MySQL startet nicht

Postby llia » 15. November 2017 18:52

Hallo zusammen,

mein MYSQL startet plötzlich nicht mehr. Wenige Minuten davor lief es noch, jetzt kommt folgende Meldung:18:47:46 [mysql] Versuche MySQL zu starten...
18:47:46 [mysql] Statusänderung erkannt: gestartet
18:47:47 [mysql] Statusänderung erkannt: gestoppt
18:47:47 [mysql] Fehler: MySQL wurde unerwartet beendet
18:47:47 [mysql] Ursache könnte ein geblockter Port, fehlende Abhängigkeiten,
18:47:47 [mysql] fehlende Berechtigungen, ein Absturz oder ein Abbruch einer anderen Methode sein.
18:47:47 [mysql] Drücke den Logs Button um error logs zu sehen und prüfe
18:47:47 [mysql] im Windows Event Viewer für weitere Hinweise
18:47:47 [mysql] Wenn du weitere Hilfe benötigst, kopiere den kompletten Inhalt des Log Fensters
18:47:47 [mysql] und füge ihn als Ergänzung in einem neuen Forum Eintrag hinzu.

Im Log steht Folgendes:
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2017-11-15 18:18:15 1b04 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.
2017-11-15 18:18:15 6916 [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.

2017-11-15 18:18:15 6916 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-15 18:18:15 6916 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-15 18:18:15 6916 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-15 18:18:15 6916 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-15 18:18:15 6916 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-15 18:18:15 6916 [Note] InnoDB: Using generic crc32 instructions
2017-11-15 18:18:15 6916 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-15 18:18:15 6916 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15 18:18:15 6916 [Note] InnoDB: Highest supported file format is Barracuda.
2017-11-15 18:18:15 6916 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 13218450 in the ib_logfiles!
2017-11-15 18:18:15 6916 [Note] InnoDB: Database was not shutdown normally!
2017-11-15 18:18:15 6916 [Note] InnoDB: Starting crash recovery.
2017-11-15 18:18:15 6916 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-11-15 18:18:16 6916 [Note] InnoDB: Restoring possible half-written data pages
2017-11-15 18:18:16 6916 [Note] InnoDB: from the doublewrite buffer...
2017-11-15 18:18:16 6916 [Note] InnoDB: 128 rollback segment(s) are active.
2017-11-15 18:18:16 6916 [Note] InnoDB: Waiting for purge to start
2017-11-15 18:18:16 6916 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 13218450
2017-11-15 18:18:16 1252 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-11-15 18:18:16 6916 [Note] Plugin 'FEEDBACK' is disabled.
2017-11-15 18:18:16 6916 [Note] Server socket created on IP: '::'.
2017-11-15 18:18:16 6916 [Note] c:\users\lhian\onedrive\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2017-11-15 18:39:37 1c48 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.
2017-11-15 18:39:37 7240 [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.

2017-11-15 18:39:37 7240 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-15 18:39:37 7240 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-15 18:39:37 7240 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-15 18:39:37 7240 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-15 18:39:37 7240 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-15 18:39:37 7240 [Note] InnoDB: Using generic crc32 instructions
2017-11-15 18:39:37 7240 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-15 18:39:37 7240 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15 18:39:37 7240 [Note] InnoDB: Highest supported file format is Barracuda.
2017-11-15 18:39:37 7240 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 14225262 in the ib_logfiles!
2017-11-15 18:39:37 7240 [Note] InnoDB: Database was not shutdown normally!
2017-11-15 18:39:37 7240 [Note] InnoDB: Starting crash recovery.
2017-11-15 18:39:37 7240 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-11-15 18:39:37 7240 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_wordpress/wp_options-DESKTOP-L9K8C9Q uses space ID: 39 at filepath: .\bitnami_wordpress\wp_options-desktop-l9k8c9q.ibd. Cannot open tablespace bitnami_wordpress/wp_options which uses space ID: 39 at filepath: .\bitnami_wordpress\wp_options.ibd
InnoDB: Error: could not open single-table tablespace file .\bitnami_wordpress\wp_options.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.
171115 18:39:37 [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.21-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 = 787106 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!my_wildcmp_mb_bin()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?set_required_privilege@Settable_routine_parameter@@UAEX_N@Z()
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()
mysqld.exe!my_wildcmp_mb_bin()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
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.
2017-11-15 18:39:47 1a1c 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.
2017-11-15 18:39:47 6684 [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.

2017-11-15 18:39:47 6684 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-15 18:39:47 6684 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-15 18:39:47 6684 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-15 18:39:47 6684 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-15 18:39:47 6684 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-15 18:39:47 6684 [Note] InnoDB: Using generic crc32 instructions
2017-11-15 18:39:47 6684 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-15 18:39:47 6684 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15 18:39:47 6684 [Note] InnoDB: Highest supported file format is Barracuda.
2017-11-15 18:39:47 6684 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 14225262 in the ib_logfiles!
2017-11-15 18:39:47 6684 [Note] InnoDB: Database was not shutdown normally!
2017-11-15 18:39:47 6684 [Note] InnoDB: Starting crash recovery.
2017-11-15 18:39:47 6684 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-11-15 18:39:47 6684 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_wordpress/wp_options-DESKTOP-L9K8C9Q uses space ID: 39 at filepath: .\bitnami_wordpress\wp_options-desktop-l9k8c9q.ibd. Cannot open tablespace bitnami_wordpress/wp_options which uses space ID: 39 at filepath: .\bitnami_wordpress\wp_options.ibd
InnoDB: Error: could not open single-table tablespace file .\bitnami_wordpress\wp_options.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.
171115 18:39:47 [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.21-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 = 787106 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!my_wildcmp_mb_bin()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?set_required_privilege@Settable_routine_parameter@@UAEX_N@Z()
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()
mysqld.exe!my_wildcmp_mb_bin()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
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.
2017-11-15 18:47:18 44c 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.
2017-11-15 18:47:18 1100 [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.

2017-11-15 18:47:18 1100 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-15 18:47:18 1100 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-15 18:47:18 1100 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-15 18:47:18 1100 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-15 18:47:18 1100 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-15 18:47:18 1100 [Note] InnoDB: Using generic crc32 instructions
2017-11-15 18:47:18 1100 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-15 18:47:18 1100 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15 18:47:18 1100 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-11-15 18:47:18 1100 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-11-15 18:47:18 1100 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\lhian\OneDrive\XAMPP\mysql\data\ibdata1
2017-11-15 18:47:18 1100 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-11-15 18:47:18 1100 [ERROR] Plugin 'InnoDB' init function returned error.
2017-11-15 18:47:18 1100 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-11-15 18:47:18 1100 [Note] Plugin 'FEEDBACK' is disabled.
2017-11-15 18:47:18 1100 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-11-15 18:47:18 1100 [ERROR] Aborting

2017-11-15 18:47:29 2df4 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.
2017-11-15 18:47:29 11764 [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.

2017-11-15 18:47:29 11764 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-15 18:47:29 11764 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-15 18:47:29 11764 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-15 18:47:29 11764 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-15 18:47:29 11764 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-15 18:47:29 11764 [Note] InnoDB: Using generic crc32 instructions
2017-11-15 18:47:29 11764 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-15 18:47:29 11764 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15 18:47:29 11764 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-11-15 18:47:29 11764 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-11-15 18:47:29 11764 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\lhian\OneDrive\XAMPP\mysql\data\ibdata1
2017-11-15 18:47:29 11764 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-11-15 18:47:29 11764 [ERROR] Plugin 'InnoDB' init function returned error.
2017-11-15 18:47:29 11764 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-11-15 18:47:29 11764 [Note] Plugin 'FEEDBACK' is disabled.
2017-11-15 18:47:29 11764 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-11-15 18:47:29 11764 [ERROR] Aborting

2017-11-15 18:47:46 2154 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.
2017-11-15 18:47:46 8532 [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.

2017-11-15 18:47:46 8532 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-15 18:47:46 8532 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-15 18:47:46 8532 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-15 18:47:46 8532 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-15 18:47:46 8532 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-15 18:47:46 8532 [Note] InnoDB: Using generic crc32 instructions
2017-11-15 18:47:46 8532 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-15 18:47:46 8532 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15 18:47:46 8532 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-11-15 18:47:46 8532 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-11-15 18:47:46 8532 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\Users\lhian\OneDrive\XAMPP\mysql\data\ibdata1
2017-11-15 18:47:46 8532 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-11-15 18:47:46 8532 [ERROR] Plugin 'InnoDB' init function returned error.
2017-11-15 18:47:46 8532 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-11-15 18:47:46 8532 [Note] Plugin 'FEEDBACK' is disabled.
2017-11-15 18:47:46 8532 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-11-15 18:47:46 8532 [ERROR] Aborting


Kann mir jemand weiterhelfen? Ich muss morgen mein Arbeitsergebnis präsentieren und stehe jetzt völlig auf dem Schlauch.

Danke schonmal!
llia
 
Posts: 1
Joined: 15. November 2017 18:45
XAMPP version: v3.2.2
Operating System: Windows 10

Re: MySQL startet nicht

Postby Nobbie » 16. November 2017 10:48

Das sieht nach einem Datenbankcrash aus. Die Ursachen sind vielfältig, entweder ein Absturz des PCs, eine defekte Windows DLL, die Datenbank nicht richtig heruntergefahren (einfach PC ausgemacht) usw. etc. pp.

Es sieht nicht so aus, als wenn das reparabel ist, das Beste wäre, ein Backup einzuspielen - wenn Du eines gemacht hast (was leider die meisten nicht machen).

P.S.: Ich sehe gerade, Du hast Xampp auf OneDrive installiert. Das ist absolut tödlich, genau deswegen was Dir jetzt passiert ist. Wenn Du mit verschiedenen Rechnern auf OneDrive zugreifst wird mit hoher Wahrscheinlichkeit die Datenbank zerschossen. Das liegt daran, dass OneDrive immer alle Rechner aktuell halten will, aber das funktioniert nicht mit Systemen wie InnoDB, wo alle Dateien nicht offen auf der Platte liegen, sondern ihrerseits "verpackt" sind in einer Gemeinschaftsdatei. Wenn Du vor der Installation auf OneDrive hier gefragt hättest, hätte ich strikt davon abgeraten.
Nobbie
 
Posts: 9809
Joined: 09. March 2008 13:04


Return to XAMPP für Windows

Who is online

Users browsing this forum: No registered users and 13 guests