XAMPP und MYSQL

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

XAMPP und MYSQL

Postby chinbert » 02. July 2017 12:41

Sorry, es ist ein leidiges Thema. Leider habe ich keinen passenden Lösungsansatz im Forum gefunden.

Seit gestern bekomme ich eine Fehlermeldung, wenn ich MySQL über XAMPP starten möchte:

Errorlog vom 01. Juni 2017:
Code: Select all
2017-07-01 12:29:31 2460 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-07-01 12:29:31 9312 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-07-01 12:29:31 9312 [Note] InnoDB: The InnoDB memory heap is disabled
2017-07-01 12:29:31 9312 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-07-01 12:29:31 9312 [Note] InnoDB: Memory barrier is not used
2017-07-01 12:29:31 9312 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-07-01 12:29:31 9312 [Note] InnoDB: Using generic crc32 instructions
2017-07-01 12:29:31 9312 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-07-01 12:29:31 9312 [Note] InnoDB: Completed initialization of buffer pool
2017-07-01 12:29:31 9312 [Note] InnoDB: Highest supported file format is Barracuda.
2017-07-01 12:29:32 9312 [Note] InnoDB: The log sequence numbers 5732713719 and 5732713719 in ibdata files do not match the log sequence number 5763283359 in the ib_logfiles!
2017-07-01 12:29:32 9312 [Note] InnoDB: Database was not shutdown normally!
2017-07-01 12:29:32 9312 [Note] InnoDB: Starting crash recovery.
2017-07-01 12:29:32 9312 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-07-01 12:29:32 9312 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_wordpress/wp_woocommerce_api_keys uses space ID: 1133 at filepath: .\bitnami_wordpress\wp_woocommerce_api_keys.ibd. Cannot open tablespace drupal/cache_dynamic_page_cache which uses space ID: 1133 at filepath: .\drupal\cache_dynamic_page_cache.ibd
InnoDB: Error: could not open single-table tablespace file .\drupal\cache_dynamic_page_cache.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.


Folgende Schritt habe ich durchgeführt:
1. "innodb_flush_method = normal" zwischen "innodb_lock_wait_timeout = 50" und "## UTF 8 Settings" gespeichert. Mysql lässt sich noch immer nicht starten.
2. Den Drupalordner inklusive "cache_dynamic_page_cache" gelöscht (aus dem MYSQL Data Ordner).
Lösche ich den Ordner, bekomme ich beim nächsten Errorlog einen anderen Ordner ausgegeben.
3. Die my.cnf hätte ich gerne geändert. Ich finde sie allerdings nicht...

Mir fällt leider nicht mehr ein...
Es gab wohl mal einen Fehler beim Shutdown, aber dass dadurch Mysql nicht mehr starten soll?
An diesem Tag habe ich auch mal meinen Glasfaseranschluss neugestartet...

Errorlog vom 30. Juni 2017, der etwas anders aussieht als der gestrige:
Code: Select all
2017-06-30 10:38:48 3eb8 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-06-30 10:38:48 16056 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-06-30 10:38:48 16056 [Note] InnoDB: The InnoDB memory heap is disabled
2017-06-30 10:38:48 16056 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-06-30 10:38:48 16056 [Note] InnoDB: Memory barrier is not used
2017-06-30 10:38:48 16056 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-06-30 10:38:48 16056 [Note] InnoDB: Using generic crc32 instructions
2017-06-30 10:38:48 16056 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-06-30 10:38:48 16056 [Note] InnoDB: Completed initialization of buffer pool
2017-06-30 10:38:48 16056 [Note] InnoDB: Highest supported file format is Barracuda.
2017-06-30 10:38:49 16056 [Note] InnoDB: 128 rollback segment(s) are active.
2017-06-30 10:38:49 16056 [Note] InnoDB: Waiting for purge to start
2017-06-30 10:38:49 16056 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 5732713719
2017-06-30 10:38:49 15844 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-06-30 10:38:49 16056 [Note] Plugin 'FEEDBACK' is disabled.
2017-06-30 10:38:49 16056 [Note] Server socket created on IP: '::'.
2017-06-30 10:38:49 16056 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.13-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
2017-06-30 13:07:07 1fe8 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-06-30 13:07:07 8168 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-06-30 13:07:07 8168 [Note] InnoDB: The InnoDB memory heap is disabled
2017-06-30 13:07:07 8168 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-06-30 13:07:07 8168 [Note] InnoDB: Memory barrier is not used
2017-06-30 13:07:07 8168 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-06-30 13:07:07 8168 [Note] InnoDB: Using generic crc32 instructions
2017-06-30 13:07:07 8168 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-06-30 13:07:07 8168 [Note] InnoDB: Completed initialization of buffer pool
2017-06-30 13:07:08 8168 [Note] InnoDB: Highest supported file format is Barracuda.
2017-06-30 13:07:08 8168 [Note] InnoDB: The log sequence numbers 5732713719 and 5732713719 in ibdata files do not match the log sequence number 5763283359 in the ib_logfiles!
2017-06-30 13:07:08 8168 [Note] InnoDB: Database was not shutdown normally!
2017-06-30 13:07:08 8168 [Note] InnoDB: Starting crash recovery.
2017-06-30 13:07:08 8168 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-06-30 13:07:08 8168 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_wordpress/wp_woocommerce_api_keys uses space ID: 1133 at filepath: .\bitnami_wordpress\wp_woocommerce_api_keys.ibd. Cannot open tablespace drupal/cache_dynamic_page_cache which uses space ID: 1133 at filepath: .\drupal\cache_dynamic_page_cache.ibd
InnoDB: Error: could not open single-table tablespace file .\drupal\cache_dynamic_page_cache.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.


Bei diesem Log hat es noch normal funktioniert:
Code: Select all
2017-06-29 14:46:08 14a4 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-06-29 14:46:08 5284 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-06-29 14:46:08 5284 [Note] InnoDB: The InnoDB memory heap is disabled
2017-06-29 14:46:08 5284 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-06-29 14:46:08 5284 [Note] InnoDB: Memory barrier is not used
2017-06-29 14:46:08 5284 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-06-29 14:46:08 5284 [Note] InnoDB: Using generic crc32 instructions
2017-06-29 14:46:08 5284 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-06-29 14:46:08 5284 [Note] InnoDB: Completed initialization of buffer pool
2017-06-29 14:46:08 5284 [Note] InnoDB: Highest supported file format is Barracuda.
2017-06-29 14:46:08 5284 [Note] InnoDB: 128 rollback segment(s) are active.
2017-06-29 14:46:08 5284 [Note] InnoDB: Waiting for purge to start
2017-06-29 14:46:09 5284 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 5730573403
2017-06-29 14:46:09 13724 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-06-29 14:46:09 5284 [Note] Plugin 'FEEDBACK' is disabled.
2017-06-29 14:46:09 5284 [Note] Server socket created on IP: '::'.
2017-06-29 14:46:09 5284 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.13-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
2017-06-29 23:35:48 20900 [Note] c:\xampp\mysql\bin\mysqld.exe: Normal shutdown

2017-06-29 23:35:48 20900 [Note] Event Scheduler: Purging the queue. 0 events
2017-06-29 23:35:48 720 [Note] InnoDB: FTS optimize thread exiting.
2017-06-29 23:35:48 20900 [Note] InnoDB: Starting shutdown...
2017-06-29 23:35:50 20900 [Note] InnoDB: Shutdown completed; log sequence number 5732713719
2017-06-29 23:35:50 20900 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete
chinbert
 
Posts: 2
Joined: 02. July 2017 12:24
XAMPP version: 3.2.2
Operating System: Windows 10

Re: XAMPP und MYSQL

Postby Nobbie » 02. July 2017 17:27

chinbert wrote:Es gab wohl mal einen Fehler beim Shutdown, aber dass dadurch Mysql nicht mehr starten soll?


Genau das ist die Fehlermeldung. Siehe:

2017-07-01 12:29:32 9312 [Note] InnoDB: The log sequence numbers 5732713719 and 5732713719 in ibdata files do not match the log sequence number 5763283359 in the ib_logfiles!
2017-07-01 12:29:32 9312 [Note] InnoDB: Database was not shutdown normally!
2017-07-01 12:29:32 9312 [Note] InnoDB: Starting crash recovery.


Es gibt jede Menge Postings (auch hier im Forum) wo empfohlen wird, sämtliche *.ibd Dateien zu löschen (nicht nur die eine). Das war auch mal ein Bug in MySQL, aber auch bei unsauberem Shutdown sind diese Dateien kaputt. Aus https://bugs.mysql.com/bug.php?id=67595

1. Delete the data/mysql/*.ibd files and the corresponding .frm files for the .ibd files
2. Start the server with --skip-slave-start

Danach sollten die Daten wieder da sein, die Konfigurationsdatei für Mysql heißt nicht my.cnf unter Windows, sondern my.ini und befindet sich im mysql/bin Ordner. Wo hast Du denn "innodb_flush_method = normal" eingetragen, wenn Du my.ini nicht findest???
Nobbie
 
Posts: 9683
Joined: 09. March 2008 13:04

Re: XAMPP und MYSQL

Postby chinbert » 02. July 2017 18:32

Hallo Nobbie,

vielen Dank für deinen Hinweis. Dann versuche ich es mal und lösche die ibd files. Wenn ich dann noch welche habe... :-)

Ich hab den Eintrag in der my.ini gespeichert. So kenne ich es eigentlich nur.
chinbert
 
Posts: 2
Joined: 02. July 2017 12:24
XAMPP version: 3.2.2
Operating System: Windows 10


Return to XAMPP für Windows

Who is online

Users browsing this forum: No registered users and 14 guests