Can't Connect To the Database

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

Can't Connect To the Database

Postby dreski » 28. July 2014 18:01

For some reason I can't seem to connect to the database. Here are the log files:

2014-07-14 23:29:48 30796 [Note] Plugin 'FEDERATED' is disabled.
2014-07-14 23:29:48 6c58 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-07-14 23:29:48 30796 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-14 23:29:48 30796 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-14 23:29:48 30796 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-14 23:29:48 30796 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-14 23:29:48 30796 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-14 23:29:48 30796 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-14 23:29:48 30796 [Note] InnoDB: Completed initialization of buffer pool
2014-07-14 23:29:48 30796 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-14 23:29:49 30796 [Warning] InnoDB: Resizing redo log from 2*3072 to 2*320 pages, LSN=1625987
2014-07-14 23:29:49 30796 [Warning] InnoDB: Starting to delete and rewrite log files.
2014-07-14 23:29:49 30796 [Note] InnoDB: Setting log file C:\xamppp\mysql\data\ib_logfile101 size to 5 MB
2014-07-14 23:29:49 30796 [Note] InnoDB: Setting log file C:\xamppp\mysql\data\ib_logfile1 size to 5 MB
2014-07-14 23:29:49 30796 [Note] InnoDB: Renaming log file C:\xamppp\mysql\data\ib_logfile101 to C:\xamppp\mysql\data\ib_logfile0
2014-07-14 23:29:49 30796 [Warning] InnoDB: New log files created, LSN=1625987
2014-07-14 23:29:49 30796 [Note] InnoDB: 128 rollback segment(s) are active.
2014-07-14 23:29:49 30796 [Note] InnoDB: Waiting for purge to start
2014-07-14 23:29:50 30796 [Note] InnoDB: 5.6.16 started; log sequence number 1625987
2014-07-14 23:29:50 30796 [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: a8c8bf71-0bd8-11e4-9570-002637bd3942.
2014-07-14 23:29:50 30796 [Note] Server hostname (bind-address): '*'; port: 3306
2014-07-14 23:29:50 30796 [Note] IPv6 is available.
2014-07-14 23:29:50 30796 [Note] - '::' resolves to '::';
2014-07-14 23:29:50 30796 [Note] Server socket created on IP: '::'.
2014-07-14 23:29:50 30796 [Note] Event Scheduler: Loaded 0 events
2014-07-14 23:29:50 30796 [Note] c:\xamppp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)
2014-07-15 23:07:37 7192 [Note] Plugin 'FEDERATED' is disabled.
2014-07-15 23:07:37 314 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-07-15 23:07:37 7192 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-15 23:07:37 7192 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-15 23:07:37 7192 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-15 23:07:37 7192 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-15 23:07:37 7192 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-15 23:07:38 7192 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-15 23:07:38 7192 [Note] InnoDB: Completed initialization of buffer pool
2014-07-15 23:07:38 7192 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-15 23:07:38 7192 [Note] InnoDB: The log sequence numbers 1625987 and 1625987 in ibdata files do not match the log sequence number 1626134 in the ib_logfiles!
2014-07-15 23:07:38 7192 [Note] InnoDB: Database was not shutdown normally!
2014-07-15 23:07:38 7192 [Note] InnoDB: Starting crash recovery.
2014-07-15 23:07:38 7192 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-15 23:07:38 7192 [Note] InnoDB: Restoring possible half-written data pages
2014-07-15 23:07:38 7192 [Note] InnoDB: from the doublewrite buffer...
2014-07-15 23:07:39 7192 [Note] InnoDB: 128 rollback segment(s) are active.
2014-07-15 23:07:39 7192 [Note] InnoDB: Waiting for purge to start
2014-07-15 23:07:39 7192 [Note] InnoDB: 5.6.16 started; log sequence number 1626134
2014-07-15 23:07:39 7192 [Note] Server hostname (bind-address): '*'; port: 3306
2014-07-15 23:07:39 7192 [Note] IPv6 is available.
2014-07-15 23:07:39 7192 [Note] - '::' resolves to '::';
2014-07-15 23:07:39 7192 [Note] Server socket created on IP: '::'.
2014-07-15 23:07:43 7192 [Note] Event Scheduler: Loaded 0 events
2014-07-15 23:07:43 7192 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)
2014-07-15 23:21:29 7192 [Note] mysql\bin\mysqld.exe: Normal shutdown

2014-07-15 23:21:29 7192 [Note] Giving 0 client threads a chance to die gracefully
2014-07-15 23:21:29 7192 [Note] Event Scheduler: Purging the queue. 0 events
2014-07-15 23:21:29 7192 [Note] Shutting down slave threads
2014-07-15 23:21:29 7192 [Note] Forcefully disconnecting 0 remaining clients
2014-07-15 23:21:29 7192 [Note] Binlog end
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'partition'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_METRICS'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_CMP'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'INNODB_TRX'
2014-07-15 23:21:29 7192 [Note] Shutting down plugin 'InnoDB'
2014-07-15 23:21:29 7192 [Note] InnoDB: FTS optimize thread exiting.
2014-07-15 23:21:29 7192 [Note] InnoDB: Starting shutdown...
2014-07-15 23:21:30 7192 [Note] InnoDB: Shutdown completed; log sequence number 1626144
2014-07-15 23:21:30 7192 [Note] Shutting down plugin 'BLACKHOLE'
2014-07-15 23:21:30 7192 [Note] Shutting down plugin 'ARCHIVE'
2014-07-15 23:21:30 7192 [Note] Shutting down plugin 'MRG_MYISAM'
2014-07-15 23:21:30 7192 [Note] Shutting down plugin 'MyISAM'
2014-07-15 23:21:30 7192 [Note] Shutting down plugin 'MEMORY'
2014-07-15 23:21:30 7192 [Note] Shutting down plugin 'CSV'
2014-07-15 23:21:30 7192 [Note] Shutting down plugin 'sha256_password'
2014-07-15 23:21:30 7192 [Note] Shutting down plugin 'mysql_old_password'
2014-07-15 23:21:30 7192 [Note] Shutting down plugin 'mysql_native_password'
2014-07-15 23:21:30 7192 [Note] Shutting down plugin 'binlog'
2014-07-15 23:21:30 7192 [Note] mysql\bin\mysqld.exe: Shutdown complete

2014-07-15 23:27:10 4832 [Note] Plugin 'FEDERATED' is disabled.
2014-07-15 23:27:10 12e4 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-07-15 23:27:10 4832 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-15 23:27:10 4832 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-15 23:27:10 4832 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-15 23:27:10 4832 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-15 23:27:10 4832 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-15 23:27:10 4832 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-15 23:27:10 4832 [Note] InnoDB: Completed initialization of buffer pool
2014-07-15 23:27:10 4832 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-15 23:27:10 4832 [Note] InnoDB: 128 rollback segment(s) are active.
2014-07-15 23:27:10 4832 [Note] InnoDB: Waiting for purge to start
2014-07-15 23:27:10 4832 [Note] InnoDB: 5.6.16 started; log sequence number 1626144
2014-07-15 23:27:10 4832 [Note] Server hostname (bind-address): '*'; port: 3306
2014-07-15 23:27:10 4832 [Note] IPv6 is available.
2014-07-15 23:27:10 4832 [Note] - '::' resolves to '::';
2014-07-15 23:27:10 4832 [Note] Server socket created on IP: '::'.
2014-07-15 23:27:10 4832 [Note] Event Scheduler: Loaded 0 events
2014-07-15 23:27:10 4832 [Note] c:\xamppp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)
2014-07-26 17:36:39 12532 [Note] Plugin 'FEDERATED' is disabled.
2014-07-26 17:36:39 1e20 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-07-26 17:36:39 12532 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-26 17:36:39 12532 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-26 17:36:39 12532 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-26 17:36:39 12532 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-26 17:36:39 12532 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-26 17:36:39 12532 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-26 17:36:39 12532 [Note] InnoDB: Completed initialization of buffer pool
2014-07-26 17:36:39 12532 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-26 17:36:39 12532 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-26 17:36:39 12532 [Note] InnoDB: Database was not shutdown normally!
2014-07-26 17:36:39 12532 [Note] InnoDB: Starting crash recovery.
2014-07-26 17:36:39 12532 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-26 17:36:40 12532 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-26 17:38:05 15128 [Note] Plugin 'FEDERATED' is disabled.
2014-07-26 17:38:05 3b1c 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-07-26 17:38:05 15128 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-26 17:38:05 15128 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-26 17:38:05 15128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-26 17:38:05 15128 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-26 17:38:05 15128 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-26 17:38:05 15128 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-26 17:38:05 15128 [Note] InnoDB: Completed initialization of buffer pool
2014-07-26 17:38:05 15128 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-26 17:38:05 15128 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-26 17:38:05 15128 [Note] InnoDB: Database was not shutdown normally!
2014-07-26 17:38:05 15128 [Note] InnoDB: Starting crash recovery.
2014-07-26 17:38:05 15128 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-26 17:38:05 15128 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-26 17:38:18 15324 [Note] Plugin 'FEDERATED' is disabled.
2014-07-26 17:38:18 3be0 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-07-26 17:38:18 15324 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-26 17:38:18 15324 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-26 17:38:18 15324 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-26 17:38:18 15324 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-26 17:38:18 15324 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-26 17:38:18 15324 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-26 17:38:18 15324 [Note] InnoDB: Completed initialization of buffer pool
2014-07-26 17:38:18 15324 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-26 17:38:18 15324 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-26 17:38:18 15324 [Note] InnoDB: Database was not shutdown normally!
2014-07-26 17:38:18 15324 [Note] InnoDB: Starting crash recovery.
2014-07-26 17:38:18 15324 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-26 17:38:18 15324 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-26 17:38:21 12896 [Note] Plugin 'FEDERATED' is disabled.
2014-07-26 17:38:21 32c0 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-07-26 17:38:21 12896 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-26 17:38:21 12896 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-26 17:38:21 12896 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-26 17:38:21 12896 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-26 17:38:21 12896 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-26 17:38:21 12896 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-26 17:38:21 12896 [Note] InnoDB: Completed initialization of buffer pool
2014-07-26 17:38:21 12896 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-26 17:38:21 12896 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-26 17:38:21 12896 [Note] InnoDB: Database was not shutdown normally!
2014-07-26 17:38:21 12896 [Note] InnoDB: Starting crash recovery.
2014-07-26 17:38:21 12896 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-26 17:38:21 12896 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-26 17:38:24 12332 [Note] Plugin 'FEDERATED' is disabled.
2014-07-26 17:38:24 3658 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-07-26 17:38:24 12332 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-26 17:38:24 12332 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-26 17:38:24 12332 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-26 17:38:24 12332 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-26 17:38:24 12332 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-26 17:38:24 12332 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-26 17:38:24 12332 [Note] InnoDB: Completed initialization of buffer pool
2014-07-26 17:38:24 12332 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-26 17:38:24 12332 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-26 17:38:24 12332 [Note] InnoDB: Database was not shutdown normally!
2014-07-26 17:38:24 12332 [Note] InnoDB: Starting crash recovery.
2014-07-26 17:38:24 12332 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-26 17:38:24 12332 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-26 17:38:36 12580 [Note] Plugin 'FEDERATED' is disabled.
2014-07-26 17:38:36 32f4 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-07-26 17:38:36 12580 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-26 17:38:36 12580 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-26 17:38:36 12580 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-26 17:38:36 12580 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-26 17:38:36 12580 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-26 17:38:36 12580 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-26 17:38:36 12580 [Note] InnoDB: Completed initialization of buffer pool
2014-07-26 17:38:36 12580 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-26 17:38:36 12580 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-26 17:38:36 12580 [Note] InnoDB: Database was not shutdown normally!
2014-07-26 17:38:36 12580 [Note] InnoDB: Starting crash recovery.
2014-07-26 17:38:36 12580 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-26 17:38:36 12580 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-26 17:38:45 13404 [Note] Plugin 'FEDERATED' is disabled.
2014-07-26 17:38:45 3a0c 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-07-26 17:38:45 13404 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-26 17:38:45 13404 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-26 17:38:45 13404 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-26 17:38:45 13404 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-26 17:38:45 13404 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-26 17:38:45 13404 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-26 17:38:45 13404 [Note] InnoDB: Completed initialization of buffer pool
2014-07-26 17:38:45 13404 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-26 17:38:45 13404 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-26 17:38:45 13404 [Note] InnoDB: Database was not shutdown normally!
2014-07-26 17:38:45 13404 [Note] InnoDB: Starting crash recovery.
2014-07-26 17:38:45 13404 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-26 17:38:45 13404 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-28 11:05:42 12940 [Note] Plugin 'FEDERATED' is disabled.
2014-07-28 11:05:42 2cb0 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-07-28 11:05:42 12940 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-28 11:05:42 12940 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-28 11:05:42 12940 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-28 11:05:42 12940 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-28 11:05:42 12940 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-28 11:05:42 12940 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-28 11:05:42 12940 [Note] InnoDB: Completed initialization of buffer pool
2014-07-28 11:05:42 12940 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-28 11:05:42 12940 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-28 11:05:42 12940 [Note] InnoDB: Database was not shutdown normally!
2014-07-28 11:05:42 12940 [Note] InnoDB: Starting crash recovery.
2014-07-28 11:05:42 12940 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-28 11:05:42 12940 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-28 11:05:48 7548 [Note] Plugin 'FEDERATED' is disabled.
2014-07-28 11:05:48 2b04 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-07-28 11:05:48 7548 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-28 11:05:48 7548 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-28 11:05:48 7548 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-28 11:05:48 7548 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-28 11:05:48 7548 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-28 11:05:48 7548 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-28 11:05:48 7548 [Note] InnoDB: Completed initialization of buffer pool
2014-07-28 11:05:48 7548 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-28 11:05:48 7548 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-28 11:05:48 7548 [Note] InnoDB: Database was not shutdown normally!
2014-07-28 11:05:48 7548 [Note] InnoDB: Starting crash recovery.
2014-07-28 11:05:48 7548 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-28 11:05:49 7548 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-28 11:06:16 12708 [Note] Plugin 'FEDERATED' is disabled.
2014-07-28 11:06:16 183c 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-07-28 11:06:16 12708 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-28 11:06:16 12708 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-28 11:06:16 12708 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-28 11:06:16 12708 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-28 11:06:16 12708 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-28 11:06:16 12708 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-28 11:06:16 12708 [Note] InnoDB: Completed initialization of buffer pool
2014-07-28 11:06:16 12708 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-28 11:06:16 12708 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-28 11:06:16 12708 [Note] InnoDB: Database was not shutdown normally!
2014-07-28 11:06:16 12708 [Note] InnoDB: Starting crash recovery.
2014-07-28 11:06:16 12708 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-28 11:06:16 12708 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-28 11:25:42 4332 [Note] Plugin 'FEDERATED' is disabled.
2014-07-28 11:25:42 1a6c 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-07-28 11:25:42 4332 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-28 11:25:42 4332 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-28 11:25:42 4332 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-28 11:25:42 4332 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-28 11:25:42 4332 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-28 11:25:42 4332 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-28 11:25:42 4332 [Note] InnoDB: Completed initialization of buffer pool
2014-07-28 11:25:42 4332 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-28 11:25:42 4332 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-28 11:25:42 4332 [Note] InnoDB: Database was not shutdown normally!
2014-07-28 11:25:42 4332 [Note] InnoDB: Starting crash recovery.
2014-07-28 11:25:42 4332 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-28 11:25:43 4332 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-28 11:26:59 9920 [Note] Plugin 'FEDERATED' is disabled.
2014-07-28 11:26:59 1638 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-07-28 11:26:59 9920 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-28 11:26:59 9920 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-28 11:26:59 9920 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-28 11:26:59 9920 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-28 11:26:59 9920 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-28 11:26:59 9920 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-28 11:26:59 9920 [Note] InnoDB: Completed initialization of buffer pool
2014-07-28 11:26:59 9920 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-28 11:26:59 9920 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-28 11:26:59 9920 [Note] InnoDB: Database was not shutdown normally!
2014-07-28 11:26:59 9920 [Note] InnoDB: Starting crash recovery.
2014-07-28 11:26:59 9920 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-28 11:26:59 9920 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-28 11:27:21 7696 [Note] Plugin 'FEDERATED' is disabled.
2014-07-28 11:27:21 1180 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-07-28 11:27:21 7696 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-28 11:27:21 7696 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-28 11:27:21 7696 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-28 11:27:21 7696 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-28 11:27:21 7696 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-28 11:27:21 7696 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-28 11:27:21 7696 [Note] InnoDB: Completed initialization of buffer pool
2014-07-28 11:27:21 7696 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-28 11:27:21 7696 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-28 11:27:21 7696 [Note] InnoDB: Database was not shutdown normally!
2014-07-28 11:27:21 7696 [Note] InnoDB: Starting crash recovery.
2014-07-28 11:27:21 7696 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-28 11:27:21 7696 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-28 11:35:22 4656 [Note] Plugin 'FEDERATED' is disabled.
2014-07-28 11:35:22 19ec 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-07-28 11:35:22 4656 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-28 11:35:22 4656 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-28 11:35:22 4656 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-28 11:35:22 4656 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-28 11:35:22 4656 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-28 11:35:22 4656 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-28 11:35:22 4656 [Note] InnoDB: Completed initialization of buffer pool
2014-07-28 11:35:22 4656 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-28 11:35:22 4656 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-28 11:35:22 4656 [Note] InnoDB: Database was not shutdown normally!
2014-07-28 11:35:22 4656 [Note] InnoDB: Starting crash recovery.
2014-07-28 11:35:22 4656 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-28 11:35:22 4656 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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-07-28 11:35:24 6568 [Note] Plugin 'FEDERATED' is disabled.
2014-07-28 11:35:24 2704 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-07-28 11:35:24 6568 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-28 11:35:24 6568 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-28 11:35:24 6568 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-28 11:35:24 6568 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-28 11:35:24 6568 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-28 11:35:24 6568 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-07-28 11:35:24 6568 [Note] InnoDB: Completed initialization of buffer pool
2014-07-28 11:35:24 6568 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-28 11:35:24 6568 [Note] InnoDB: The log sequence numbers 1626144 and 1626144 in ibdata files do not match the log sequence number 10359059 in the ib_logfiles!
2014-07-28 11:35:24 6568 [Note] InnoDB: Database was not shutdown normally!
2014-07-28 11:35:24 6568 [Note] InnoDB: Starting crash recovery.
2014-07-28 11:35:24 6568 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-28 11:35:24 6568 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace valleypaincarecom/wp_eg_navigation_skins uses space ID: 22 at filepath: .\valleypaincarecom\wp_eg_navigation_skins.ibd. Cannot open tablespace wordpress10/wp_usermeta which uses space ID: 22 at filepath: .\wordpress10\wp_usermeta.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress10\wp_usermeta.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.

Please let me know as I'm trying to finish a project for a clients website.
dreski
 
Posts: 1
Joined: 28. July 2014 17:51
Operating System: win7

Return to XAMPP for Windows

Who is online

Users browsing this forum: hthnightwolf and 69 guests