Datenbank kann beim 2. Aufruf nicht gestartet werden

[AHY]

Hallo,
habe Xampp 1.8.3 und Mediawiki installiert, ein Passwort für den Super User (Admin) und den Verzeichnisschutz festgelegt,
die LocalSettings.php (in mediawiki>htdocs) etwas konfiguriert und dann alles geschlossen bzw. weggeklickt-evtl. nicht über das Xampp Control Paneel geschlossen, nach einem Neuaufruf des Paneels ging die Datenbank nicht mehr zu starten, habe sämtliche zu googelnden und hier zu findenden Anleitungen durchprobiert, es geht einfach nicht, die mysql_error.log spuckt immer wieder das Gleiche aus, obwohl die Anweisungen dort auch schon eingearbeitet sind, wie z. B "innodb_force_recovery > 0" in die my.cnf geschrieben, die ich übrigens erst mal erstellen musste und in xampp/bin gespeichert habe
(bin leider auch ganz neu mit dieser Materie am Werkeln)
auch unter Tools eine neu Datenbank anlegen geht nicht, da kommt: MySQL meldet: Dokumentation

#2002 - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.

Der Server antwortet nicht (evtl. ist der Socket des lokalen MySQL-Servers nicht korrekt konfiguriert).

hier die mysql_error.log:
2014-03-28 14:45:03 6140 [Note] Plugin 'FEDERATED' is disabled.
2014-03-28 14:45:03 b20 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.
2014-03-28 14:45:03 6140 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-28 14:45:03 6140 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-28 14:45:03 6140 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-28 14:45:04 6140 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-28 14:45:04 6140 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-03-28 14:45:04 6140 [Note] InnoDB: Completed initialization of buffer pool
2014-03-28 14:45:04 6140 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2014-03-28 14:45:04 6140 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2014-03-28 14:45:04 6140 [Note] InnoDB: Database physically writes the file full: wait...
2014-03-28 14:45:04 6140 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2014-03-28 14:45:05 6140 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2014-03-28 14:45:06 6140 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2014-03-28 14:45:06 6140 [Warning] InnoDB: New log files created, LSN=45781
2014-03-28 14:45:06 6140 [Note] InnoDB: Doublewrite buffer not found: creating new
2014-03-28 14:45:06 6140 [Note] InnoDB: Doublewrite buffer created
2014-03-28 14:45:11 6140 [Note] InnoDB: 128 rollback segment(s) are active.
2014-03-28 14:45:11 6140 [Warning] InnoDB: Creating foreign key constraint system tables.
2014-03-28 14:45:11 6140 [Note] InnoDB: Foreign key constraint system tables created
2014-03-28 14:45:11 6140 [Note] InnoDB: Creating tablespace and datafile system tables.
2014-03-28 14:45:11 6140 [Note] InnoDB: Tablespace and datafile system tables created.
2014-03-28 14:45:11 6140 [Note] InnoDB: Waiting for purge to start
2014-03-28 14:45:11 6140 [Note] InnoDB: 5.6.11 started; log sequence number 0
2014-03-28 14:45:11 6140 [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: 2eee65c8-b67f-11e3-a8e3-002185e424f1.
2014-03-28 14:45:11 6140 [Note] Server hostname (bind-address): '*'; port: 3306
2014-03-28 14:45:11 6140 [Note] IPv6 is available.
2014-03-28 14:45:11 6140 [Note] - '::' resolves to '::';
2014-03-28 14:45:11 6140 [Note] Server socket created on IP: '::'.
2014-03-28 14:45:13 6140 [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.
2014-03-28 14:45:13 6140 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2014-03-28 14:45:13 6140 [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.
2014-03-28 14:45:13 6140 [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.
2014-03-28 14:45:13 6140 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2014-03-28 14:45:14 6140 [Note] Event Scheduler: Loaded 0 events
2014-03-28 14:45:14 6140 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2014-03-28 15:51:14 121c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-28 15:51:14 121c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-28 15:51:14 121c InnoDB: Error: Fetch of persistent statistics requested for table "bitnami_mediawiki"."user" 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.
2014-03-28 15:51:15 121c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-28 15:51:15 121c InnoDB: Recalculation of persistent statistics requested for table "bitnami_mediawiki"."user" index "user_name" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2014-03-28 15:51:15 121c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2014-03-28 15:51:15 121c InnoDB: Error: Fetch of persistent statistics requested for table "bitnami_mediawiki"."user" 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.
2014-03-28 15:51:16 121c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
...(hier gekürzt-passt sonst nicht hinein).......................
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_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.
2014-03-31 13:11:46 5980 [Note] Plugin 'FEDERATED' is disabled.
2014-03-31 13:11:46 1708 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.
2014-03-31 13:11:46 5980 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-31 13:11:46 5980 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-31 13:11:46 5980 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-31 13:11:46 5980 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-31 13:11:46 5980 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-03-31 13:11:46 5980 [Note] InnoDB: Completed initialization of buffer pool
2014-03-31 13:11:46 5980 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-31 13:11:46 5980 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4698311 in the ib_logfiles!
2014-03-31 13:11:46 5980 [Note] InnoDB: Database was not shutdown normally!
2014-03-31 13:11:46 5980 [Note] InnoDB: Starting crash recovery.
2014-03-31 13:11:46 5980 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-03-31 13:11:46 5980 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_mediawiki/user uses space ID: 1 at filepath: .\bitnami_mediawiki\user.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_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.
2014-03-31 13:15:38 4780 [Note] Plugin 'FEDERATED' is disabled.
2014-03-31 13:15:38 15d4 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.
2014-03-31 13:15:38 4780 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-31 13:15:38 4780 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-31 13:15:38 4780 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-31 13:15:38 4780 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-31 13:15:38 4780 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-03-31 13:15:38 4780 [Note] InnoDB: Completed initialization of buffer pool
2014-03-31 13:15:38 4780 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-31 13:15:38 4780 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4698311 in the ib_logfiles!
2014-03-31 13:15:38 4780 [Note] InnoDB: Database was not shutdown normally!
2014-03-31 13:15:38 4780 [Note] InnoDB: Starting crash recovery.
2014-03-31 13:15:38 4780 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-03-31 13:15:38 4780 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_mediawiki/user uses space ID: 1 at filepath: .\bitnami_mediawiki\user.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_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.
2014-03-31 13:15:40 1564 [Note] Plugin 'FEDERATED' is disabled.
2014-03-31 13:15:40 fb8 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.
2014-03-31 13:15:40 1564 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-31 13:15:40 1564 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-31 13:15:40 1564 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-31 13:15:40 1564 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-31 13:15:40 1564 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-03-31 13:15:40 1564 [Note] InnoDB: Completed initialization of buffer pool
2014-03-31 13:15:40 1564 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-31 13:15:40 1564 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4698311 in the ib_logfiles!
2014-03-31 13:15:40 1564 [Note] InnoDB: Database was not shutdown normally!
2014-03-31 13:15:40 1564 [Note] InnoDB: Starting crash recovery.
2014-03-31 13:15:40 1564 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-03-31 13:15:40 1564 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_mediawiki/user uses space ID: 1 at filepath: .\bitnami_mediawiki\user.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_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.
2014-03-31 13:15:43 5512 [Note] Plugin 'FEDERATED' is disabled.
2014-03-31 13:15:43 d18 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.
2014-03-31 13:15:43 5512 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-31 13:15:43 5512 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-31 13:15:43 5512 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-31 13:15:43 5512 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-31 13:15:43 5512 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-03-31 13:15:43 5512 [Note] InnoDB: Completed initialization of buffer pool
2014-03-31 13:15:43 5512 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-31 13:15:43 5512 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4698311 in the ib_logfiles!
2014-03-31 13:15:43 5512 [Note] InnoDB: Database was not shutdown normally!
2014-03-31 13:15:43 5512 [Note] InnoDB: Starting crash recovery.
2014-03-31 13:15:43 5512 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-03-31 13:15:43 5512 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_mediawiki/user uses space ID: 1 at filepath: .\bitnami_mediawiki\user.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_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.
2014-03-31 13:16:45 2856 [Note] Plugin 'FEDERATED' is disabled.
2014-03-31 13:16:45 13bc 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.
2014-03-31 13:16:45 2856 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-31 13:16:45 2856 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-31 13:16:45 2856 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-31 13:16:45 2856 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-31 13:16:45 2856 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-03-31 13:16:45 2856 [Note] InnoDB: Completed initialization of buffer pool
2014-03-31 13:16:45 2856 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-31 13:16:45 2856 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4698311 in the ib_logfiles!
2014-03-31 13:16:45 2856 [Note] InnoDB: Database was not shutdown normally!
2014-03-31 13:16:45 2856 [Note] InnoDB: Starting crash recovery.
2014-03-31 13:16:45 2856 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-03-31 13:16:45 2856 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_mediawiki/user uses space ID: 1 at filepath: .\bitnami_mediawiki\user.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_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.
2014-03-31 13:34:26 5652 [Note] Plugin 'FEDERATED' is disabled.
2014-03-31 13:34:26 1250 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.
2014-03-31 13:34:26 5652 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-31 13:34:26 5652 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-31 13:34:26 5652 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-31 13:34:26 5652 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-31 13:34:26 5652 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-03-31 13:34:26 5652 [Note] InnoDB: Completed initialization of buffer pool
2014-03-31 13:34:26 5652 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-31 13:34:26 5652 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4698311 in the ib_logfiles!
2014-03-31 13:34:26 5652 [Note] InnoDB: Database was not shutdown normally!
2014-03-31 13:34:26 5652 [Note] InnoDB: Starting crash recovery.
2014-03-31 13:34:26 5652 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-03-31 13:34:26 5652 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_mediawiki/user uses space ID: 1 at filepath: .\bitnami_mediawiki\user.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_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.
2014-03-31 13:57:51 4420 [Note] Plugin 'FEDERATED' is disabled.
2014-03-31 13:57:51 1148 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.
2014-03-31 13:57:51 4420 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-31 13:57:51 4420 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-31 13:57:51 4420 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-31 13:57:51 4420 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-31 13:57:51 4420 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-03-31 13:57:51 4420 [Note] InnoDB: Completed initialization of buffer pool
2014-03-31 13:57:52 4420 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-31 13:57:52 4420 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4698311 in the ib_logfiles!
2014-03-31 13:57:52 4420 [Note] InnoDB: Database was not shutdown normally!
2014-03-31 13:57:52 4420 [Note] InnoDB: Starting crash recovery.
2014-03-31 13:57:52 4420 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-03-31 13:57:52 4420 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_mediawiki/user uses space ID: 1 at filepath: .\bitnami_mediawiki\user.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_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.
................................(nochmal gekürzt.wiederholt sich alles)............................................
2014-03-31 14:58:08 4484 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_mediawiki/user uses space ID: 1 at filepath: .\bitnami_mediawiki\user.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_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.
2014-03-31 14:58:18 5980 [Note] Plugin 'FEDERATED' is disabled.
2014-03-31 14:58:18 12fc 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.
2014-03-31 14:58:18 5980 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-31 14:58:18 5980 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-31 14:58:18 5980 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-31 14:58:18 5980 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-31 14:58:18 5980 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-03-31 14:58:18 5980 [Note] InnoDB: Completed initialization of buffer pool
2014-03-31 14:58:18 5980 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-31 14:58:18 5980 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4698311 in the ib_logfiles!
2014-03-31 14:58:18 5980 [Note] InnoDB: Database was not shutdown normally!
2014-03-31 14:58:18 5980 [Note] InnoDB: Starting crash recovery.
2014-03-31 14:58:18 5980 [Note] InnoDB: Reading tablespace information from the .ibd files...
..................gekürzt....................
2014-03-31 15:10:32 992 [Note] Plugin 'FEDERATED' is disabled.
2014-03-31 15:10:32 1438 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.
2014-03-31 15:10:32 992 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-31 15:10:32 992 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-31 15:10:32 992 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-31 15:10:32 992 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-31 15:10:32 992 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-03-31 15:10:32 992 [Note] InnoDB: Completed initialization of buffer pool
2014-03-31 15:10:32 992 [Note] InnoDB: Highest supported file format is Barracuda.
2014-03-31 15:10:32 992 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4698311 in the ib_logfiles!
2014-03-31 15:10:32 992 [Note] InnoDB: Database was not shutdown normally!
2014-03-31 15:10:32 992 [Note] InnoDB: Starting crash recovery.
2014-03-31 15:10:32 992 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-03-31 15:10:32 992 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_mediawiki/user uses space ID: 1 at filepath: .\bitnami_mediawiki\user.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_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.


die mysql\innodb_table_stats.ibd existiert gar nicht

es wäre superklasse, wenn jemand Rat wüsste, danke!

[Nobbie]

Hallo,
habe Xampp 1.8.3 und Mediawiki installiert

Und wohin genau?

[AHY]

Oh, sorry, ich dachte nicht, das jemand geantwortet hat- bei anderen Foren bekommt man ein Email wenn eine Antwort eintrifft,
danke für die Reaktion!
Xampp wurde unter direkt c installiert ( -also Festplattenbereich der Programme),
Mediawiki über die Installationsapplikation von/ in Xampp direkt