Ich starte mein XAMPP von meiner externen Festplatte, so wie immer, kann nun aber apache und mysql nicht mehr starten
setup_xampp.bat hab ich ganz normal ausgeführt.
Bitte ausführliche Lösung antworten. Habe nicht sehr viel Ahnung davon. Danke
apache errorlog:
2014-05-09 21:14:04 988 [Note] Plugin 'FEDERATED' is disabled.
2014-05-09 21:14:04 10d0 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-05-09 21:14:04 988 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-05-09 21:14:04 988 [Note] InnoDB: The InnoDB memory heap is disabled
2014-05-09 21:14:04 988 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-05-09 21:14:04 988 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-05-09 21:14:04 988 [Note] InnoDB: Not using CPU crc32 instructions
2014-05-09 21:14:04 988 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-05-09 21:14:04 988 [Note] InnoDB: Completed initialization of buffer pool
2014-05-09 21:14:04 988 [Note] InnoDB: Highest supported file format is Barracuda.
2014-05-09 21:14:04 988 [Note] InnoDB: The log sequence numbers 1625987 and 1625987 in ibdata files do not match the log sequence number 9794438 in the ib_logfiles!
2014-05-09 21:14:04 988 [Note] InnoDB: Database was not shutdown normally!
2014-05-09 21:14:04 988 [Note] InnoDB: Starting crash recovery.
2014-05-09 21:14:04 988 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-05-09 21:14:04 988 [ERROR] InnoDB: Space id in fsp header 1635149088,but in the page header 1819025512
2014-05-09 21:14:04 988 [ERROR] InnoDB: innodb-page-size mismatch in tablespace .\mysql\slave_relay_log_info.ibd (table mysql/slave_relay_log_info)
2014-05-09 21:14:04 988 [Note] InnoDB: Page size:1024 Pages to analyze:64
2014-05-09 21:14:04 988 [Note] InnoDB: Page size: 1024, Possible space_id count:0
2014-05-09 21:14:04 988 [Note] InnoDB: Page size:2048 Pages to analyze:48
2014-05-09 21:14:04 988 [Note] InnoDB: Page size: 2048, Possible space_id count:0
2014-05-09 21:14:04 988 [Note] InnoDB: Page size:4096 Pages to analyze:24
2014-05-09 21:14:04 988 [Note] InnoDB: Page size: 4096, Possible space_id count:0
2014-05-09 21:14:04 988 [Note] InnoDB: Page size:8192 Pages to analyze:12
2014-05-09 21:14:04 988 [Note] InnoDB: Page size: 8192, Possible space_id count:0
2014-05-09 21:14:04 988 [Note] InnoDB: Page size:16384 Pages to analyze:6
2014-05-09 21:14:04 988 [Note] InnoDB: Page size: 16384, Possible space_id count:0
InnoDB: Error: could not open single-table tablespace file .\mysql\slave_relay_log_info.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.
mysql errorlog:
2014-05-09 21:14:04 988 [Note] Plugin 'FEDERATED' is disabled.
2014-05-09 21:14:04 10d0 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-05-09 21:14:04 988 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-05-09 21:14:04 988 [Note] InnoDB: The InnoDB memory heap is disabled
2014-05-09 21:14:04 988 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-05-09 21:14:04 988 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-05-09 21:14:04 988 [Note] InnoDB: Not using CPU crc32 instructions
2014-05-09 21:14:04 988 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-05-09 21:14:04 988 [Note] InnoDB: Completed initialization of buffer pool
2014-05-09 21:14:04 988 [Note] InnoDB: Highest supported file format is Barracuda.
2014-05-09 21:14:04 988 [Note] InnoDB: The log sequence numbers 1625987 and 1625987 in ibdata files do not match the log sequence number 9794438 in the ib_logfiles!
2014-05-09 21:14:04 988 [Note] InnoDB: Database was not shutdown normally!
2014-05-09 21:14:04 988 [Note] InnoDB: Starting crash recovery.
2014-05-09 21:14:04 988 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-05-09 21:14:04 988 [ERROR] InnoDB: Space id in fsp header 1635149088,but in the page header 1819025512
2014-05-09 21:14:04 988 [ERROR] InnoDB: innodb-page-size mismatch in tablespace .\mysql\slave_relay_log_info.ibd (table mysql/slave_relay_log_info)
2014-05-09 21:14:04 988 [Note] InnoDB: Page size:1024 Pages to analyze:64
2014-05-09 21:14:04 988 [Note] InnoDB: Page size: 1024, Possible space_id count:0
2014-05-09 21:14:04 988 [Note] InnoDB: Page size:2048 Pages to analyze:48
2014-05-09 21:14:04 988 [Note] InnoDB: Page size: 2048, Possible space_id count:0
2014-05-09 21:14:04 988 [Note] InnoDB: Page size:4096 Pages to analyze:24
2014-05-09 21:14:04 988 [Note] InnoDB: Page size: 4096, Possible space_id count:0
2014-05-09 21:14:04 988 [Note] InnoDB: Page size:8192 Pages to analyze:12
2014-05-09 21:14:04 988 [Note] InnoDB: Page size: 8192, Possible space_id count:0
2014-05-09 21:14:04 988 [Note] InnoDB: Page size:16384 Pages to analyze:6
2014-05-09 21:14:04 988 [Note] InnoDB: Page size: 16384, Possible space_id count:0
InnoDB: Error: could not open single-table tablespace file .\mysql\slave_relay_log_info.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.