MYSQl schmiert immer ab

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

MYSQl schmiert immer ab

Postby A.S. » 07. December 2013 15:19

Habe bei mir auf dem Rechner XAMPP installiert. Ging auch. habe das htdocs Verzeichnis geändert. Server neu gestartet und ging auch ein paar Tage. Habe jetzt nach ca. 2 Wochen das Teil wieder angeschmissen und nun schmiert MySQL nach 5 Sekunden immer wieder ab.

Das war schon einmal habe halt gedacht, dass bei installation was falsch gelaufen ist und habs neu draufgemacht. Aber nun geht es schon wieder nicht. Warum geht es nicht?

hier noch die Log:

2013-12-07 13:57:05 3836 [Note] Plugin 'FEDERATED' is disabled.
2013-12-07 13:57:06 f14 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-12-07 13:57:06 3836 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-07 13:57:06 3836 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-07 13:57:06 3836 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-07 13:57:06 3836 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-07 13:57:06 3836 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-07 13:57:06 3836 [Note] InnoDB: Completed initialization of buffer pool
2013-12-07 13:57:07 3836 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-07 13:57:07 3836 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1658689 in the ib_logfiles!
2013-12-07 13:57:07 3836 [Note] InnoDB: Database was not shutdown normally!
2013-12-07 13:57:07 3836 [Note] InnoDB: Starting crash recovery.
2013-12-07 13:57:07 3836 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-07 13:57:09 3836 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db1312427/script_uebungen uses space ID: 2 at filepath: .\db1312427\script_uebungen.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
2013-12-07 13:57:28 4440 [Note] Plugin 'FEDERATED' is disabled.
2013-12-07 13:57:28 115c 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-12-07 13:57:28 4440 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-07 13:57:28 4440 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-07 13:57:28 4440 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-07 13:57:28 4440 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-07 13:57:28 4440 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-07 13:57:28 4440 [Note] InnoDB: Completed initialization of buffer pool
2013-12-07 13:57:28 4440 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-07 13:57:28 4440 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1658689 in the ib_logfiles!
2013-12-07 13:57:28 4440 [Note] InnoDB: Database was not shutdown normally!
2013-12-07 13:57:28 4440 [Note] InnoDB: Starting crash recovery.
2013-12-07 13:57:28 4440 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-07 13:57:28 4440 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db1312427/script_uebungen uses space ID: 2 at filepath: .\db1312427\script_uebungen.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
2013-12-07 13:57:29 4520 [Note] Plugin 'FEDERATED' is disabled.
2013-12-07 13:57:29 11ac 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-12-07 13:57:29 4520 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-07 13:57:29 4520 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-07 13:57:29 4520 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-07 13:57:29 4520 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-07 13:57:29 4520 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-07 13:57:29 4520 [Note] InnoDB: Completed initialization of buffer pool
2013-12-07 13:57:29 4520 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-07 13:57:29 4520 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1658689 in the ib_logfiles!
2013-12-07 13:57:29 4520 [Note] InnoDB: Database was not shutdown normally!
2013-12-07 13:57:29 4520 [Note] InnoDB: Starting crash recovery.
2013-12-07 13:57:29 4520 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-07 13:57:29 4520 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db1312427/script_uebungen uses space ID: 2 at filepath: .\db1312427\script_uebungen.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
2013-12-07 13:57:31 4588 [Note] Plugin 'FEDERATED' is disabled.
2013-12-07 13:57:31 11f0 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-12-07 13:57:31 4588 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-07 13:57:31 4588 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-07 13:57:31 4588 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-07 13:57:31 4588 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-07 13:57:31 4588 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-07 13:57:31 4588 [Note] InnoDB: Completed initialization of buffer pool
2013-12-07 13:57:31 4588 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-07 13:57:31 4588 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1658689 in the ib_logfiles!
2013-12-07 13:57:31 4588 [Note] InnoDB: Database was not shutdown normally!
2013-12-07 13:57:31 4588 [Note] InnoDB: Starting crash recovery.
2013-12-07 13:57:31 4588 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-07 13:57:31 4588 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db1312427/script_uebungen uses space ID: 2 at filepath: .\db1312427\script_uebungen.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
2013-12-07 13:57:34 4676 [Note] Plugin 'FEDERATED' is disabled.
2013-12-07 13:57:34 1248 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-12-07 13:57:34 4676 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-07 13:57:34 4676 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-07 13:57:34 4676 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-07 13:57:34 4676 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-07 13:57:34 4676 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-07 13:57:34 4676 [Note] InnoDB: Completed initialization of buffer pool
2013-12-07 13:57:34 4676 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-07 13:57:34 4676 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1658689 in the ib_logfiles!
2013-12-07 13:57:34 4676 [Note] InnoDB: Database was not shutdown normally!
2013-12-07 13:57:34 4676 [Note] InnoDB: Starting crash recovery.
2013-12-07 13:57:34 4676 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-07 13:57:34 4676 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db1312427/script_uebungen uses space ID: 2 at filepath: .\db1312427\script_uebungen.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
2013-12-07 13:57:36 4744 [Note] Plugin 'FEDERATED' is disabled.
2013-12-07 13:57:36 128c 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-12-07 13:57:36 4744 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-07 13:57:36 4744 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-07 13:57:36 4744 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-07 13:57:36 4744 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-07 13:57:36 4744 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-07 13:57:36 4744 [Note] InnoDB: Completed initialization of buffer pool
2013-12-07 13:57:36 4744 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-07 13:57:36 4744 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1658689 in the ib_logfiles!
2013-12-07 13:57:36 4744 [Note] InnoDB: Database was not shutdown normally!
2013-12-07 13:57:36 4744 [Note] InnoDB: Starting crash recovery.
2013-12-07 13:57:36 4744 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-07 13:57:36 4744 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db1312427/script_uebungen uses space ID: 2 at filepath: .\db1312427\script_uebungen.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
2013-12-07 13:57:37 4852 [Note] Plugin 'FEDERATED' is disabled.
2013-12-07 13:57:37 12f8 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-12-07 13:57:37 4852 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-07 13:57:37 4852 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-07 13:57:37 4852 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-07 13:57:37 4852 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-07 13:57:37 4852 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-07 13:57:37 4852 [Note] InnoDB: Completed initialization of buffer pool
2013-12-07 13:57:37 4852 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-07 13:57:37 4852 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1658689 in the ib_logfiles!
2013-12-07 13:57:37 4852 [Note] InnoDB: Database was not shutdown normally!
2013-12-07 13:57:37 4852 [Note] InnoDB: Starting crash recovery.
2013-12-07 13:57:37 4852 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-07 13:57:37 4852 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db1312427/script_uebungen uses space ID: 2 at filepath: .\db1312427\script_uebungen.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
2013-12-07 13:57:39 4920 [Note] Plugin 'FEDERATED' is disabled.
2013-12-07 13:57:39 133c 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-12-07 13:57:39 4920 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-07 13:57:39 4920 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-07 13:57:39 4920 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-07 13:57:39 4920 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-07 13:57:39 4920 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-07 13:57:39 4920 [Note] InnoDB: Completed initialization of buffer pool
2013-12-07 13:57:39 4920 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-07 13:57:39 4920 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1658689 in the ib_logfiles!
2013-12-07 13:57:39 4920 [Note] InnoDB: Database was not shutdown normally!
2013-12-07 13:57:39 4920 [Note] InnoDB: Starting crash recovery.
2013-12-07 13:57:39 4920 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-07 13:57:39 4920 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db1312427/script_uebungen uses space ID: 2 at filepath: .\db1312427\script_uebungen.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
2013-12-07 14:41:41 5356 [Note] Plugin 'FEDERATED' is disabled.
2013-12-07 14:41:41 173c 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-12-07 14:41:41 5356 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-07 14:41:41 5356 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-07 14:41:41 5356 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-07 14:41:41 5356 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-07 14:41:41 5356 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-07 14:41:41 5356 [Note] InnoDB: Completed initialization of buffer pool
2013-12-07 14:41:41 5356 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-07 14:41:41 5356 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1658689 in the ib_logfiles!
2013-12-07 14:41:41 5356 [Note] InnoDB: Database was not shutdown normally!
2013-12-07 14:41:41 5356 [Note] InnoDB: Starting crash recovery.
2013-12-07 14:41:41 5356 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-07 14:41:41 5356 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db1312427/script_uebungen uses space ID: 2 at filepath: .\db1312427\script_uebungen.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
2013-12-07 14:49:33 4872 [Note] Plugin 'FEDERATED' is disabled.
2013-12-07 14:49:33 1588 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-12-07 14:49:33 4872 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-07 14:49:33 4872 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-07 14:49:33 4872 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-07 14:49:33 4872 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-07 14:49:33 4872 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-07 14:49:33 4872 [Note] InnoDB: Completed initialization of buffer pool
2013-12-07 14:49:33 4872 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-07 14:49:33 4872 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1658689 in the ib_logfiles!
2013-12-07 14:49:33 4872 [Note] InnoDB: Database was not shutdown normally!
2013-12-07 14:49:33 4872 [Note] InnoDB: Starting crash recovery.
2013-12-07 14:49:33 4872 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-07 14:49:33 4872 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db1312427/script_uebungen uses space ID: 2 at filepath: .\db1312427\script_uebungen.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
2013-12-07 15:02:49 1336 [Note] Plugin 'FEDERATED' is disabled.
2013-12-07 15:02:51 fc4 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-12-07 15:02:51 1336 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-07 15:02:51 1336 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-07 15:02:51 1336 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-07 15:02:51 1336 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-07 15:02:51 1336 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-07 15:02:51 1336 [Note] InnoDB: Completed initialization of buffer pool
2013-12-07 15:02:52 1336 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-07 15:02:52 1336 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1658689 in the ib_logfiles!
2013-12-07 15:02:52 1336 [Note] InnoDB: Database was not shutdown normally!
2013-12-07 15:02:52 1336 [Note] InnoDB: Starting crash recovery.
2013-12-07 15:02:52 1336 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-07 15:02:52 1336 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace db1312427/script_uebungen uses space ID: 2 at filepath: .\db1312427\script_uebungen.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
A.S.
 
Posts: 2
Joined: 07. December 2013 14:59
XAMPP Version: 5.5.19
Operating System: Windows 7

Re: MYSQl schmiert immer ab

Postby Altrea » 07. December 2013 15:46

viewtopic.php?f=16&t=66746#p230644

Empfohlene Lösung: Die aktuelle XAMPP version 1.8.3-2 verwenden, in der das Problem gelöst sein soll.
Alternativ: Auf den XAMPP 1.8.2 Zweig ausweichen. Hier wurde dieses Problem noch nicht beobachtet.
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: 6697
Joined: 17. August 2009 13:05
XAMPP Version: 5.5.19
Operating System: W7Ux64

Re: MYSQl schmiert immer ab

Postby A.S. » 07. December 2013 16:48

okay ich hab jetzt das neue xampp installiert. Soweit läuft es. Schaue dann in ein paar Tagen nochmal ob es läuft. Sollte es nicht gehen melde ich mich noch einmal.

THX
A.S.
 
Posts: 2
Joined: 07. December 2013 14:59
XAMPP Version: 5.5.19
Operating System: Windows 7


Return to XAMPP für Windows

Who is online

Users browsing this forum: No registered users and 20 guests