showing error

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

showing error

Postby vijayrocky » 05. October 2013 04:41

this is log file..plz heip me out.. :cry:
================================================================

2013-10-03 17:40:37 3996 [Note] Plugin 'FEDERATED' is disabled.
2013-10-03 17:40:37 4c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-10-03 17:40:37 3996 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-03 17:40:37 3996 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-03 17:40:37 3996 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-03 17:40:37 3996 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-03 17:40:37 3996 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-03 17:40:37 3996 [Note] InnoDB: Completed initialization of buffer pool
2013-10-03 17:40:37 3996 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-10-03 17:40:37 3996 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2013-10-03 17:40:37 3996 [Note] InnoDB: Database physically writes the file full: wait...
2013-10-03 17:40:38 3996 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-10-03 17:40:38 3996 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-10-03 17:40:38 3996 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-10-03 17:40:38 3996 [Warning] InnoDB: New log files created, LSN=45781
2013-10-03 17:40:38 3996 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-10-03 17:40:38 3996 [Note] InnoDB: Doublewrite buffer created
2013-10-03 17:40:40 3996 [Note] InnoDB: 128 rollback segment(s) are active.
2013-10-03 17:40:40 3996 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-10-03 17:40:40 3996 [Note] InnoDB: Foreign key constraint system tables created
2013-10-03 17:40:40 3996 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-10-03 17:40:40 3996 [Note] InnoDB: Tablespace and datafile system tables created.
2013-10-03 17:40:40 3996 [Note] InnoDB: Waiting for purge to start
2013-10-03 17:40:40 3996 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-10-03 17:40:40 3996 [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: d1cb8e6c-2c24-11e3-a2b6-e06995999620.
2013-10-03 17:40:40 3996 [Note] Server hostname (bind-address): '*'; port: 3306
2013-10-03 17:40:40 3996 [Note] IPv6 is available.
2013-10-03 17:40:40 3996 [Note] - '::' resolves to '::';
2013-10-03 17:40:40 3996 [Note] Server socket created on IP: '::'.
2013-10-04 09:14:12 960 [Note] Plugin 'FEDERATED' is disabled.
2013-10-04 09:14:12 690 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-10-04 09:14:12 960 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-04 09:14:12 960 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-04 09:14:12 960 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-04 09:14:12 960 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-04 09:14:12 960 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-04 09:14:12 960 [Note] InnoDB: Completed initialization of buffer pool
2013-10-04 09:14:12 960 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-04 09:14:12 960 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4036229 in the ib_logfiles!
2013-10-04 09:14:12 960 [Note] InnoDB: Database was not shutdown normally!
2013-10-04 09:14:12 960 [Note] InnoDB: Starting crash recovery.
2013-10-04 09:14:12 960 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-04 09:14:13 960 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2013-10-04 09:14:20 4016 [Note] Plugin 'FEDERATED' is disabled.
2013-10-04 09:14:20 fbc InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-10-04 09:14:20 4016 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-04 09:14:20 4016 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-04 09:14:20 4016 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-04 09:14:20 4016 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-04 09:14:20 4016 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-04 09:14:20 4016 [Note] InnoDB: Completed initialization of buffer pool
2013-10-04 09:14:20 4016 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-04 09:14:20 4016 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4036229 in the ib_logfiles!
2013-10-04 09:14:20 4016 [Note] InnoDB: Database was not shutdown normally!
2013-10-04 09:14:20 4016 [Note] InnoDB: Starting crash recovery.
2013-10-04 09:14:20 4016 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-04 09:14:20 4016 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2013-10-04 21:55:30 348 [Note] Plugin 'FEDERATED' is disabled.
2013-10-04 21:55:30 de0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-10-04 21:55:30 348 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-04 21:55:30 348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-04 21:55:30 348 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-04 21:55:30 348 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-04 21:55:30 348 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-04 21:55:30 348 [Note] InnoDB: Completed initialization of buffer pool
2013-10-04 21:55:30 348 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-04 21:55:30 348 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4036229 in the ib_logfiles!
2013-10-04 21:55:30 348 [Note] InnoDB: Database was not shutdown normally!
2013-10-04 21:55:30 348 [Note] InnoDB: Starting crash recovery.
2013-10-04 21:55:30 348 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-04 21:55:30 348 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2013-10-05 09:03:07 1900 [Note] Plugin 'FEDERATED' is disabled.
2013-10-05 09:03:07 e24 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-10-05 09:03:07 1900 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-05 09:03:07 1900 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-05 09:03:07 1900 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-05 09:03:07 1900 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-05 09:03:07 1900 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-05 09:03:07 1900 [Note] InnoDB: Completed initialization of buffer pool
2013-10-05 09:03:07 1900 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-05 09:03:07 1900 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 4036229 in the ib_logfiles!
2013-10-05 09:03:07 1900 [Note] InnoDB: Database was not shutdown normally!
2013-10-05 09:03:07 1900 [Note] InnoDB: Starting crash recovery.
2013-10-05 09:03:07 1900 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-05 09:03:08 1900 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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.
vijayrocky
 
Posts: 1
Joined: 05. October 2013 04:37
XAMPP Version: 5.5.19
Operating System: windows 8

Re: showing error

Postby Altrea » 05. October 2013 09:28

We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 6829
Joined: 17. August 2009 13:05
XAMPP Version: 5.5.19
Operating System: W7Ux64


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 25 guests