BUG Xampp 1.8.3 MySQL Start

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

BUG Xampp 1.8.3 MySQL Start

Postby ptcebula » 27. August 2013 14:39

I have problems connecting to MySQL. The first time after installing 1.8.3 everything worked fine but the second time I keep getting an error. Here's the log:

2013-08-26 10:35:31 5404 [Note] Plugin 'FEDERATED' is disabled.
2013-08-26 10:35:31 1520 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-08-26 10:35:31 5404 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-26 10:35:31 5404 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-26 10:35:31 5404 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-26 10:35:31 5404 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-26 10:35:31 5404 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-26 10:35:31 5404 [Note] InnoDB: Completed initialization of buffer pool
2013-08-26 10:35:31 5404 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-08-26 10:35:31 5404 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2013-08-26 10:35:31 5404 [Note] InnoDB: Database physically writes the file full: wait...
2013-08-26 10:35:31 5404 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-08-26 10:35:31 5404 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-08-26 10:35:32 5404 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-08-26 10:35:32 5404 [Warning] InnoDB: New log files created, LSN=45781
2013-08-26 10:35:32 5404 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-08-26 10:35:32 5404 [Note] InnoDB: Doublewrite buffer created
2013-08-26 10:35:32 5404 [Note] InnoDB: 128 rollback segment(s) are active.
2013-08-26 10:35:32 5404 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-08-26 10:35:32 5404 [Note] InnoDB: Foreign key constraint system tables created
2013-08-26 10:35:32 5404 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-08-26 10:35:32 5404 [Note] InnoDB: Tablespace and datafile system tables created.
2013-08-26 10:35:32 5404 [Note] InnoDB: Waiting for purge to start
2013-08-26 10:35:32 5404 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-08-26 10:35:32 5404 [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: 788327bf-0e2a-11e3-9f3b-f0def1a2f348.
2013-08-26 10:35:32 5404 [Note] Server hostname (bind-address): '*'; port: 3306
2013-08-26 10:35:32 5404 [Note] IPv6 is available.
2013-08-26 10:35:32 5404 [Note] - '::' resolves to '::';
2013-08-26 10:35:32 5404 [Note] Server socket created on IP: '::'.
2013-08-26 10:35:32 5404 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-08-26 10:35:32 5404 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-08-26 10:35:32 5404 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-08-26 10:35:32 5404 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2013-08-26 10:35:32 5404 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-08-26 10:35:32 5404 [Note] Event Scheduler: Loaded 0 events
2013-08-26 10:35:32 5404 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2013-08-26 10:59:35 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:35 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:35 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:35 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:35 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:35 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:35 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:35 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:35 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:35 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:35 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:35 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:35 174c InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_options" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-08-26 10:59:36 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:36 174c InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_users" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-08-26 10:59:36 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:36 174c InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_usermeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-08-26 10:59:36 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:36 174c InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_terms" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-08-26 10:59:36 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:36 174c InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_term_taxonomy" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-08-26 10:59:36 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:36 174c InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_posts" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-08-26 10:59:36 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:36 174c InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_term_relationships" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-08-26 10:59:36 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:36 174c InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_comments" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-08-26 10:59:36 174c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:36 174c InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_postmeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-08-26 10:59:46 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:46 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 10:59:56 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 10:59:56 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 11:00:06 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 11:00:06 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_usermeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 11:00:37 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 11:00:37 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 11:00:39 1630 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 11:00:39 1630 InnoDB: Error: Fetch of persistent statistics requested for table "wordpress"."wp_commentmeta" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2013-08-26 11:00:50 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 11:00:50 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 14:03:25 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 14:03:25 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 14:03:25 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 14:03:25 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 14:03:50 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 14:03:50 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 14:04:29 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 14:04:29 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 14:04:29 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 14:04:29 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 14:04:34 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 14:04:34 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_usermeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:06:50 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:06:50 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:09:01 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:09:01 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_terms" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:09:11 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:09:11 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_term_taxonomy" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:10:09 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:10:09 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:10:09 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:10:09 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:10:22 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:10:22 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:10:32 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:10:32 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_term_relationships" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:10:37 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:10:37 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:10:43 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:10:43 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:10:43 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:10:43 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_terms" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:10:53 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:10:53 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_term_taxonomy" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:17:52 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:17:52 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:17:52 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:17:52 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:18:20 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:18:20 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:18:20 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:18:20 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:22:35 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:22:35 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:22:47 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:22:47 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:23:32 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:23:32 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:24:11 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:24:11 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:24:11 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:24:11 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:25:53 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:25:53 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:26:11 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:26:11 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:27:53 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:27:53 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:30:42 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:30:42 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:35:11 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:35:11 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:35:17 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:35:17 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:36:29 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:36:29 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 16:56:30 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 16:56:30 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 17:04:22 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 17:04:22 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 17:11:53 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 17:11:53 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-26 23:07:30 1580 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-08-26 23:07:30 1580 InnoDB: Recalculation of persistent statistics requested for table "wordpress"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-08-27 09:45:37 3772 [Note] Plugin 'FEDERATED' is disabled.
2013-08-27 09:45:37 46c 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-08-27 09:45:37 3772 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-27 09:45:37 3772 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-27 09:45:37 3772 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-27 09:45:37 3772 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-27 09:45:37 3772 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-27 09:45:37 3772 [Note] InnoDB: Completed initialization of buffer pool
2013-08-27 09:45:37 3772 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-27 09:45:37 3772 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2915516 in the ib_logfiles!
2013-08-27 09:45:37 3772 [Note] InnoDB: Database was not shutdown normally!
2013-08-27 09:45:37 3772 [Note] InnoDB: Starting crash recovery.
2013-08-27 09:45:37 3772 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-27 09:45:37 3772 [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-08-27 09:45:47 4540 [Note] Plugin 'FEDERATED' is disabled.
2013-08-27 09:45:47 1118 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-08-27 09:45:47 4540 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-27 09:45:47 4540 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-27 09:45:47 4540 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-27 09:45:47 4540 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-27 09:45:47 4540 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-27 09:45:47 4540 [Note] InnoDB: Completed initialization of buffer pool
2013-08-27 09:45:47 4540 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-27 09:45:47 4540 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2915516 in the ib_logfiles!
2013-08-27 09:45:47 4540 [Note] InnoDB: Database was not shutdown normally!
2013-08-27 09:45:47 4540 [Note] InnoDB: Starting crash recovery.
2013-08-27 09:45:47 4540 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-27 09:45:47 4540 [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-08-27 09:46:11 4436 [Note] Plugin 'FEDERATED' is disabled.
2013-08-27 09:46:11 ef4 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-08-27 09:46:11 4436 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-27 09:46:11 4436 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-27 09:46:11 4436 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-27 09:46:11 4436 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-27 09:46:11 4436 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-27 09:46:11 4436 [Note] InnoDB: Completed initialization of buffer pool
2013-08-27 09:46:11 4436 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-27 09:46:11 4436 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2915516 in the ib_logfiles!
2013-08-27 09:46:11 4436 [Note] InnoDB: Database was not shutdown normally!
2013-08-27 09:46:11 4436 [Note] InnoDB: Starting crash recovery.
2013-08-27 09:46:11 4436 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-27 09:46:11 4436 [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-08-27 09:46:42 4180 [Note] Plugin 'FEDERATED' is disabled.
2013-08-27 09:46:42 bb0 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-08-27 09:46:42 4180 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-27 09:46:42 4180 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-27 09:46:42 4180 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-27 09:46:42 4180 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-27 09:46:42 4180 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-27 09:46:42 4180 [Note] InnoDB: Completed initialization of buffer pool
2013-08-27 09:46:42 4180 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-27 09:46:42 4180 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2915516 in the ib_logfiles!
2013-08-27 09:46:42 4180 [Note] InnoDB: Database was not shutdown normally!
2013-08-27 09:46:42 4180 [Note] InnoDB: Starting crash recovery.
2013-08-27 09:46:42 4180 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-27 09:46:42 4180 [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-08-27 09:55:50 4756 [Note] Plugin 'FEDERATED' is disabled.
2013-08-27 09:55:50 129c 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-08-27 09:55:50 4756 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-27 09:55:50 4756 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-27 09:55:50 4756 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-27 09:55:50 4756 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-27 09:55:50 4756 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-27 09:55:50 4756 [Note] InnoDB: Completed initialization of buffer pool
2013-08-27 09:55:50 4756 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-27 09:55:50 4756 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2915516 in the ib_logfiles!
2013-08-27 09:55:50 4756 [Note] InnoDB: Database was not shutdown normally!
2013-08-27 09:55:50 4756 [Note] InnoDB: Starting crash recovery.
2013-08-27 09:55:50 4756 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-27 09:55:50 4756 [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-08-27 12:01:07 5184 [Note] Plugin 'FEDERATED' is disabled.
2013-08-27 12:01:07 1124 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-08-27 12:01:07 5184 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-27 12:01:07 5184 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-27 12:01:07 5184 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-27 12:01:07 5184 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-27 12:01:07 5184 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-27 12:01:07 5184 [Note] InnoDB: Completed initialization of buffer pool
2013-08-27 12:01:07 5184 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-27 12:01:07 5184 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2915516 in the ib_logfiles!
2013-08-27 12:01:07 5184 [Note] InnoDB: Database was not shutdown normally!
2013-08-27 12:01:07 5184 [Note] InnoDB: Starting crash recovery.
2013-08-27 12:01:07 5184 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-27 12:01:07 5184 [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-08-27 12:01:14 4764 [Note] Plugin 'FEDERATED' is disabled.
2013-08-27 12:01:14 16f4 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-08-27 12:01:14 4764 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-27 12:01:14 4764 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-27 12:01:14 4764 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-27 12:01:14 4764 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-27 12:01:14 4764 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-27 12:01:14 4764 [Note] InnoDB: Completed initialization of buffer pool
2013-08-27 12:01:14 4764 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-27 12:01:14 4764 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2915516 in the ib_logfiles!
2013-08-27 12:01:14 4764 [Note] InnoDB: Database was not shutdown normally!
2013-08-27 12:01:14 4764 [Note] InnoDB: Starting crash recovery.
2013-08-27 12:01:14 4764 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-27 12:01:14 4764 [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-08-27 15:36:02 5276 [Note] Plugin 'FEDERATED' is disabled.
2013-08-27 15:36:02 1714 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-08-27 15:36:02 5276 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-27 15:36:02 5276 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-27 15:36:02 5276 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-27 15:36:02 5276 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-27 15:36:02 5276 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-27 15:36:02 5276 [Note] InnoDB: Completed initialization of buffer pool
2013-08-27 15:36:02 5276 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-27 15:36:02 5276 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2915516 in the ib_logfiles!
2013-08-27 15:36:02 5276 [Note] InnoDB: Database was not shutdown normally!
2013-08-27 15:36:02 5276 [Note] InnoDB: Starting crash recovery.
2013-08-27 15:36:02 5276 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-27 15:36:02 5276 [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.
ptcebula
 
Posts: 2
Joined: 27. August 2013 14:37
XAMPP Version: 5.6.3
Operating System: Windows 7

Re: BUG Xampp 1.8.3 MySQL Start

Postby Altrea » 27. August 2013 15:31

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: 6697
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 48 guests