SQL stopped working

Problems with the Windows version of XAMPP, questions, comments, and anything related.

SQL stopped working

Postby jzhang172 » 16. July 2015 19:57

Turned it off because I was running into an issue with phpadmin and when I tried to restart it, it didn't work.

2:51:04 PM [mysql] Attempting to start MySQL app...
2:51:04 PM [mysql] Status change detected: running
2:51:05 PM [mysql] Status change detected: stopped
2:51:05 PM [mysql] Error: MySQL shutdown unexpectedly.
2:51:05 PM [mysql] This may be due to a blocked port, missing dependencies,
2:51:05 PM [mysql] improper privileges, a crash, or a shutdown by another method.
2:51:05 PM [mysql] Press the Logs button to view error logs and check
2:51:05 PM [mysql] the Windows Event Viewer for more clues
2:51:05 PM [mysql] If you need more help, copy and post this
2:51:05 PM [mysql] entire log window on the forums







[[[LOG:]]]
2015-07-15 23:36:41 9512 [Note] Plugin 'FEDERATED' is disabled.
2015-07-15 23:36:41 11b4 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.
2015-07-15 23:36:41 9512 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-07-15 23:36:41 9512 [Note] InnoDB: The InnoDB memory heap is disabled
2015-07-15 23:36:41 9512 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-07-15 23:36:41 9512 [Note] InnoDB: Memory barrier is not used
2015-07-15 23:36:41 9512 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-07-15 23:36:41 9512 [Note] InnoDB: Not using CPU crc32 instructions
2015-07-15 23:36:41 9512 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-07-15 23:36:41 9512 [Note] InnoDB: Completed initialization of buffer pool
2015-07-15 23:36:42 9512 [Note] InnoDB: Highest supported file format is Barracuda.
2015-07-15 23:36:42 9512 [Note] InnoDB: 128 rollback segment(s) are active.
2015-07-15 23:36:42 9512 [Note] InnoDB: Waiting for purge to start
2015-07-15 23:36:42 9512 [Note] InnoDB: 5.6.24 started; log sequence number 1665234
2015-07-15 23:36:42 9512 [Note] Server hostname (bind-address): '*'; port: 3306
2015-07-15 23:36:42 9512 [Note] IPv6 is available.
2015-07-15 23:36:42 9512 [Note] - '::' resolves to '::';
2015-07-15 23:36:42 9512 [Note] Server socket created on IP: '::'.
2015-07-16 11:44:49 7452 [Note] Plugin 'FEDERATED' is disabled.
2015-07-16 11:44:49 1c94 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.
2015-07-16 11:44:49 7452 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-07-16 11:44:49 7452 [Note] InnoDB: The InnoDB memory heap is disabled
2015-07-16 11:44:49 7452 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-07-16 11:44:49 7452 [Note] InnoDB: Memory barrier is not used
2015-07-16 11:44:49 7452 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-07-16 11:44:49 7452 [Note] InnoDB: Not using CPU crc32 instructions
2015-07-16 11:44:49 7452 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-07-16 11:44:49 7452 [Note] InnoDB: Completed initialization of buffer pool
2015-07-16 11:44:50 7452 [Note] InnoDB: Highest supported file format is Barracuda.
2015-07-16 11:44:50 7452 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665244 in the ib_logfiles!
2015-07-16 11:44:50 7452 [Note] InnoDB: Database was not shutdown normally!
2015-07-16 11:44:50 7452 [Note] InnoDB: Starting crash recovery.
2015-07-16 11:44:50 7452 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-07-16 11:44:50 7452 [Note] InnoDB: Restoring possible half-written data pages
2015-07-16 11:44:50 7452 [Note] InnoDB: from the doublewrite buffer...
2015-07-16 11:44:51 7452 [Note] InnoDB: 128 rollback segment(s) are active.
2015-07-16 11:44:51 7452 [Note] InnoDB: Waiting for purge to start
2015-07-16 11:44:51 7452 [Note] InnoDB: 5.6.24 started; log sequence number 1665244
2015-07-16 11:44:51 7452 [Note] Server hostname (bind-address): '*'; port: 3306
2015-07-16 11:44:51 7452 [Note] IPv6 is available.
2015-07-16 11:44:51 7452 [Note] - '::' resolves to '::';
2015-07-16 11:44:51 7452 [Note] Server socket created on IP: '::'.
2015-07-16 14:49:01 8532 [Note] Plugin 'FEDERATED' is disabled.
2015-07-16 14:49:01 1a08 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.
2015-07-16 14:49:01 8532 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-07-16 14:49:01 8532 [Note] InnoDB: The InnoDB memory heap is disabled
2015-07-16 14:49:01 8532 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-07-16 14:49:01 8532 [Note] InnoDB: Memory barrier is not used
2015-07-16 14:49:01 8532 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-07-16 14:49:01 8532 [Note] InnoDB: Not using CPU crc32 instructions
2015-07-16 14:49:01 8532 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-07-16 14:49:01 8532 [Note] InnoDB: Completed initialization of buffer pool
2015-07-16 14:49:02 8532 [Note] InnoDB: Highest supported file format is Barracuda.
2015-07-16 14:49:02 8532 [Note] InnoDB: Log scan progressed past the checkpoint lsn 17585574
2015-07-16 14:49:02 8532 [Note] InnoDB: Database was not shutdown normally!
2015-07-16 14:49:02 8532 [Note] InnoDB: Starting crash recovery.
2015-07-16 14:49:02 8532 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-07-16 14:49:02 8532 [ERROR] InnoDB: space header page consists of zero bytes in tablespace .\magento\core_url_rewrite.ibd (table magento/core_url_rewrite)
2015-07-16 14:49:02 8532 [Note] InnoDB: Page size:1024 Pages to analyze:64
2015-07-16 14:49:02 8532 [Note] InnoDB: Page size: 1024, Possible space_id count:0
2015-07-16 14:49:02 8532 [Note] InnoDB: Page size:2048 Pages to analyze:32
2015-07-16 14:49:02 8532 [Note] InnoDB: Page size: 2048, Possible space_id count:0
2015-07-16 14:49:02 8532 [Note] InnoDB: Page size:4096 Pages to analyze:16
2015-07-16 14:49:02 8532 [Note] InnoDB: Page size: 4096, Possible space_id count:0
2015-07-16 14:49:02 8532 [Note] InnoDB: Page size:8192 Pages to analyze:8
2015-07-16 14:49:02 8532 [Note] InnoDB: Page size: 8192, Possible space_id count:0
2015-07-16 14:49:02 8532 [Note] InnoDB: Page size:16384 Pages to analyze:4
2015-07-16 14:49:02 8532 [Note] InnoDB: Page size: 16384, Possible space_id count:0
InnoDB: Error: could not open single-table tablespace file .\magento\core_url_rewrite.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.
2015-07-16 14:49:08 2060 [Note] Plugin 'FEDERATED' is disabled.
2015-07-16 14:49:08 15a0 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.
2015-07-16 14:49:08 2060 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-07-16 14:49:08 2060 [Note] InnoDB: The InnoDB memory heap is disabled
2015-07-16 14:49:08 2060 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-07-16 14:49:08 2060 [Note] InnoDB: Memory barrier is not used
2015-07-16 14:49:08 2060 [Note] InnoDB: Compr2s015-07-les14use :lib 01.2.03
[Note] Plugin 'FEDERATED' is disabled.
2015-07-16 14:49:08 2060 [Note] InnoDB: Not using CPU crc32 instructions
2015-07-16 14:49:08 23b4 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.
2015-07-16 14:49:08 10020 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-07-16 14:49:08 10020 [Note] InnoDB: The InnoDB memory heap is disabled
2015-07-16 14:49:08 10020 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-07-16 14:49:08 10020 [Note] InnoDB: Memory barrier is not used
2015-07-16 14:49:08 10020 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-07-16 14:49:08 10020 [Note] InnoDB: Not using CPU crc32 instructions
2015-07-16 14:49:08 2060 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-07-16 14:49:08 2060 [Note] InnoDB: Completed initialization of buffer pool
2015-07-16 14:49:08 10020 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-07-16 14:49:08 10020 [Note] InnoDB: Completed initialization of buffer pool
2015-07-16 14:49:08 10020 [ERROR] InnoDB: C:\xampp\mysql\data\ibdata1 can't be opened in read-write mode
2015-07-16 14:49:08 10020 [ERROR] InnoDB: The system tablespace must be writable!
2015-07-16 14:49:08 10020 [ERROR] Plugin 'InnoDB' init function returned error.
2015-07-16 14:49:08 10020 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2015-07-16 14:49:08 10020 [ERROR] Unknown/unsupported storage engine: InnoDB
2015-07-16 14:49:08 10020 [ERROR] Aborting

2015-07-16 14:49:08 10020 [Note] Binlog end
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'partition'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_METRICS'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_CMPMEM'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_CMP'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_LOCKS'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'INNODB_TRX'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'BLACKHOLE'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'ARCHIVE'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'MRG_MYISAM'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'MyISAM'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'MEMORY'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'CSV'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'sha256_password'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'mysql_old_password'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'mysql_native_password'
2015-07-16 14:49:08 10020 [Note] Shutting down plugin 'binlog'
2015-07-16 14:49:08 10020 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2015-07-16 14:49:08 2060 [Note] InnoDB: Highest supported file format is Barracuda.
2015-07-16 14:49:09 2060 [Note] InnoDB: Log scan progressed past the checkpoint lsn 17585574
2015-07-16 14:49:09 2060 [Note] InnoDB: Database was not shutdown normally!
2015-07-16 14:49:09 2060 [Note] InnoDB: Starting crash recovery.
2015-07-16 14:49:09 2060 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-07-16 14:49:09 2060 [ERROR] InnoDB: space header page consists of zero bytes in tablespace .\magento\core_url_rewrite.ibd (table magento/core_url_rewrite)
2015-07-16 14:49:09 2060 [Note] InnoDB: Page size:1024 Pages to analyze:64
2015-07-16 14:49:09 2060 [Note] InnoDB: Page size: 1024, Possible space_id count:0
2015-07-16 14:49:09 2060 [Note] InnoDB: Page size:2048 Pages to analyze:32
2015-07-16 14:49:09 2060 [Note] InnoDB: Page size: 2048, Possible space_id count:0
2015-07-16 14:49:09 2060 [Note] InnoDB: Page size:4096 Pages to analyze:16
2015-07-16 14:49:09 2060 [Note] InnoDB: Page size: 4096, Possible space_id count:0
2015-07-16 14:49:09 2060 [Note] InnoDB: Page size:8192 Pages to analyze:8
2015-07-16 14:49:09 2060 [Note] InnoDB: Page size: 8192, Possible space_id count:0
2015-07-16 14:49:09 2060 [Note] InnoDB: Page size:16384 Pages to analyze:4
2015-07-16 14:49:09 2060 [Note] InnoDB: Page size: 16384, Possible space_id count:0
InnoDB: Error: could not open single-table tablespace file .\magento\core_url_rewrite.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.
2015-07-16 14:49:22 9956 [Note] Plugin 'FEDERATED' is disabled.
2015-07-16 14:49:22 2318 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.
2015-07-16 14:49:22 9956 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-07-16 14:49:22 9956 [Note] InnoDB: The InnoDB memory heap is disabled
2015-07-16 14:49:22 9956 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-07-16 14:49:22 9956 [Note] InnoDB: Memory barrier is not used
2015-07-16 14:49:22 9956 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-07-16 14:49:22 9956 [Note] InnoDB: Not using CPU crc32 instructions
2015-07-16 14:49:22 9956 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-07-16 14:49:22 9956 [Note] InnoDB: Completed initialization of buffer pool
2015-07-16 14:49:22 9956 [Note] InnoDB: Highest supported file format is Barracuda.
2015-07-16 14:49:23 9956 [Note] InnoDB: Log scan progressed past the checkpoint lsn 17585574
2015-07-16 14:49:23 9956 [Note] InnoDB: Database was not shutdown normally!
2015-07-16 14:49:23 9956 [Note] InnoDB: Starting crash recovery.
2015-07-16 14:49:23 9956 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-07-16 14:49:23 9956 [ERROR] InnoDB: space header page consists of zero bytes in tablespace .\magento\core_url_rewrite.ibd (table magento/core_url_rewrite)
2015-07-16 14:49:23 9956 [Note] InnoDB: Page size:1024 Pages to analyze:64
2015-07-16 14:49:23 9956 [Note] InnoDB: Page size: 1024, Possible space_id count:0
2015-07-16 14:49:23 9956 [Note] InnoDB: Page size:2048 Pages to analyze:32
2015-07-16 14:49:23 9956 [Note] InnoDB: Page size: 2048, Possible space_id count:0
2015-07-16 14:49:23 9956 [Note] InnoDB: Page size:4096 Pages to analyze:16
2015-07-16 14:49:23 9956 [Note] InnoDB: Page size: 4096, Possible space_id count:0
2015-07-16 14:49:23 9956 [Note] InnoDB: Page size:8192 Pages to analyze:8
2015-07-16 14:49:23 9956 [Note] InnoDB: Page size: 8192, Possible space_id count:0
2015-07-16 14:49:23 9956 [Note] InnoDB: Page size:16384 Pages to analyze:4
2015-07-16 14:49:23 9956 [Note] InnoDB: Page size: 16384, Possible space_id count:0
InnoDB: Error: could not open single-table tablespace file .\magento\core_url_rewrite.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.
2015-07-16 14:50:09 7568 [Note] Plugin 'FEDERATED' is disabled.
2015-07-16 14:50:09 11c8 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.
2015-07-16 14:50:09 7568 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-07-16 14:50:09 7568 [Note] InnoDB: The InnoDB memory heap is disabled
2015-07-16 14:50:09 7568 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-07-16 14:50:09 7568 [Note] InnoDB: Memory barrier is not used
2015-07-16 14:50:09 7568 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-07-16 14:50:09 7568 [Note] InnoDB: Not using CPU crc32 instructions
2015-07-16 14:50:09 7568 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-07-16 14:50:09 7568 [Note] InnoDB: Completed initialization of buffer pool
2015-07-16 14:50:10 7568 [Note] InnoDB: Highest supported file format is Barracuda.
2015-07-16 14:50:10 7568 [Note] InnoDB: Log scan progressed past the checkpoint lsn 17585574
2015-07-16 14:50:10 7568 [Note] InnoDB: Database was not shutdown normally!
2015-07-16 14:50:10 7568 [Note] InnoDB: Starting crash recovery.
2015-07-16 14:50:10 7568 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-07-16 14:50:10 7568 [ERROR] InnoDB: space header page consists of zero bytes in tablespace .\magento\core_url_rewrite.ibd (table magento/core_url_rewrite)
2015-07-16 14:50:10 7568 [Note] InnoDB: Page size:1024 Pages to analyze:64
2015-07-16 14:50:10 7568 [Note] InnoDB: Page size: 1024, Possible space_id count:0
2015-07-16 14:50:10 7568 [Note] InnoDB: Page size:2048 Pages to analyze:32
2015-07-16 14:50:10 7568 [Note] InnoDB: Page size: 2048, Possible space_id count:0
2015-07-16 14:50:10 7568 [Note] InnoDB: Page size:4096 Pages to analyze:16
2015-07-16 14:50:10 7568 [Note] InnoDB: Page size: 4096, Possible space_id count:0
2015-07-16 14:50:10 7568 [Note] InnoDB: Page size:8192 Pages to analyze:8
2015-07-16 14:50:10 7568 [Note] InnoDB: Page size: 8192, Possible space_id count:0
2015-07-16 14:50:10 7568 [Note] InnoDB: Page size:16384 Pages to analyze:4
2015-07-16 14:50:10 7568 [Note] InnoDB: Page size: 16384, Possible space_id count:0
InnoDB: Error: could not open single-table tablespace file .\magento\core_url_rewrite.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.
2015-07-16 14:51:04 5592 [Note] Plugin 'FEDERATED' is disabled.
2015-07-16 14:51:04 24f8 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.
2015-07-16 14:51:04 5592 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-07-16 14:51:04 5592 [Note] InnoDB: The InnoDB memory heap is disabled
2015-07-16 14:51:04 5592 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-07-16 14:51:04 5592 [Note] InnoDB: Memory barrier is not used
2015-07-16 14:51:04 5592 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-07-16 14:51:04 5592 [Note] InnoDB: Not using CPU crc32 instructions
2015-07-16 14:51:04 5592 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-07-16 14:51:04 5592 [Note] InnoDB: Completed initialization of buffer pool
2015-07-16 14:51:05 5592 [Note] InnoDB: Highest supported file format is Barracuda.
2015-07-16 14:51:05 5592 [Note] InnoDB: Log scan progressed past the checkpoint lsn 17585574
2015-07-16 14:51:05 5592 [Note] InnoDB: Database was not shutdown normally!
2015-07-16 14:51:05 5592 [Note] InnoDB: Starting crash recovery.
2015-07-16 14:51:05 5592 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-07-16 14:51:05 5592 [ERROR] InnoDB: space header page consists of zero bytes in tablespace .\magento\core_url_rewrite.ibd (table magento/core_url_rewrite)
2015-07-16 14:51:05 5592 [Note] InnoDB: Page size:1024 Pages to analyze:64
2015-07-16 14:51:05 5592 [Note] InnoDB: Page size: 1024, Possible space_id count:0
2015-07-16 14:51:05 5592 [Note] InnoDB: Page size:2048 Pages to analyze:32
2015-07-16 14:51:05 5592 [Note] InnoDB: Page size: 2048, Possible space_id count:0
2015-07-16 14:51:05 5592 [Note] InnoDB: Page size:4096 Pages to analyze:16
2015-07-16 14:51:05 5592 [Note] InnoDB: Page size: 4096, Possible space_id count:0
2015-07-16 14:51:05 5592 [Note] InnoDB: Page size:8192 Pages to analyze:8
2015-07-16 14:51:05 5592 [Note] InnoDB: Page size: 8192, Possible space_id count:0
2015-07-16 14:51:05 5592 [Note] InnoDB: Page size:16384 Pages to analyze:4
2015-07-16 14:51:05 5592 [Note] InnoDB: Page size: 16384, Possible space_id count:0
InnoDB: Error: could not open single-table tablespace file .\magento\core_url_rewrite.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.
jzhang172
 
Posts: 1
Joined: 16. July 2015 19:55
Operating System: Windows 8.1

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 56 guests