Hier die mysql_error:
- Code: Select all
2013-10-11 01:11:47 6028 [Note] Plugin 'FEDERATED' is disabled.
2013-10-11 01:11:47 2698 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-11 01:11:47 6028 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-11 01:11:47 6028 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-11 01:11:47 6028 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-11 01:11:47 6028 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-11 01:11:47 6028 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-11 01:11:47 6028 [Note] InnoDB: Completed initialization of buffer pool
2013-10-11 01:11:47 6028 [Note] InnoDB: The first specified data file \xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-10-11 01:11:47 6028 [Note] InnoDB: Setting file \xampp\mysql\data\ibdata1 size to 10 MB
2013-10-11 01:11:47 6028 [Note] InnoDB: Database physically writes the file full: wait...
2013-10-11 01:11:47 6028 [Note] InnoDB: Setting log file \xampp\mysql\data\ib_logfile101 size to 5 MB
2013-10-11 01:11:47 6028 [Note] InnoDB: Setting log file \xampp\mysql\data\ib_logfile1 size to 5 MB
2013-10-11 01:11:48 6028 [Note] InnoDB: Renaming log file \xampp\mysql\data\ib_logfile101 to \xampp\mysql\data\ib_logfile0
2013-10-11 01:11:48 6028 [Warning] InnoDB: New log files created, LSN=45781
2013-10-11 01:11:48 6028 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-10-11 01:11:49 6028 [Note] InnoDB: Doublewrite buffer created
2013-10-11 01:11:55 6028 [Note] InnoDB: 128 rollback segment(s) are active.
2013-10-11 01:11:55 6028 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-10-11 01:11:56 6028 [Note] InnoDB: Foreign key constraint system tables created
2013-10-11 01:11:56 6028 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-10-11 01:11:56 6028 [Note] InnoDB: Tablespace and datafile system tables created.
2013-10-11 01:11:56 6028 [Note] InnoDB: Waiting for purge to start
2013-10-11 01:11:56 6028 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-10-11 01:11:56 6028 [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: 5bb501db-3201-11e3-88ef-001a9252d87c.
2013-10-11 01:11:56 6028 [Note] Server hostname (bind-address): '*'; port: 3306
2013-10-11 01:11:56 6028 [Note] IPv6 is available.
2013-10-11 01:11:56 6028 [Note] - '::' resolves to '::';
2013-10-11 01:11:56 6028 [Note] Server socket created on IP: '::'.
2013-10-11 01:11:58 6028 [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-10-11 01:11:58 6028 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-10-11 01:11:58 6028 [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-10-11 01:11:58 6028 [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-10-11 01:11:58 6028 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-10-11 01:11:59 6028 [Note] Event Scheduler: Loaded 0 events
2013-10-11 01:11:59 6028 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
2013-10-11 01:32:20 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:20 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:20 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:20 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:21 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:21 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:21 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:21 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:21 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:22 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:22 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:22 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:22 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."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-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."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-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."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-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."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-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."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-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."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-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."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-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."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-10-11 01:32:26 ad8 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:26 ad8 InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."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-10-11 01:32:36 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:36 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:32:47 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:47 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:32:49 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:49 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_usermeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:32:57 1c6c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:57 1c6c InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."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-10-11 01:32:59 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:32:59 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_options" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:33:17 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:33:17 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:33:17 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:33:17 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:33:37 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:33:37 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_postmeta" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:33:37 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:33:37 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 01:33:48 1a8c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 01:33:48 1a8c InnoDB: Recalculation of persistent statistics requested for table "yesautohandel"."wp_posts" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2013-10-11 02:04:28 1c6c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2013-10-11 02:04:28 1c6c InnoDB: Error: Fetch of persistent statistics requested for table "yesautohandel"."wp_links" 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-10-11 15:25:33 3740 [Note] Plugin 'FEDERATED' is disabled.
2013-10-11 15:25:33 ea8 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-11 15:25:33 3740 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-11 15:25:33 3740 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-11 15:25:33 3740 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-11 15:25:33 3740 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-11 15:25:34 3740 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-11 15:25:34 3740 [Note] InnoDB: Completed initialization of buffer pool
2013-10-11 15:25:34 3740 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-11 15:25:34 3740 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2524657 in the ib_logfiles!
2013-10-11 15:25:34 3740 [Note] InnoDB: Database was not shutdown normally!
2013-10-11 15:25:34 3740 [Note] InnoDB: Starting crash recovery.
2013-10-11 15:25:34 3740 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-11 15:25:34 3740 [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 yesautohandel/wp_terms which uses space ID: 3 at filepath: .\yesautohandel\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\yesautohandel\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-11 15:25:40 2664 [Note] Plugin 'FEDERATED' is disabled.
2013-10-11 15:25:40 408 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-11 15:25:40 2664 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-11 15:25:40 2664 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-11 15:25:40 2664 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-11 15:25:40 2664 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-11 15:25:40 2664 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-11 15:25:40 2664 [Note] InnoDB: Completed initialization of buffer pool
2013-10-11 15:25:40 2664 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-11 15:25:41 2664 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2524657 in the ib_logfiles!
2013-10-11 15:25:41 2664 [Note] InnoDB: Database was not shutdown normally!
2013-10-11 15:25:41 2664 [Note] InnoDB: Starting crash recovery.
2013-10-11 15:25:41 2664 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-11 15:25:41 2664 [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 yesautohandel/wp_terms which uses space ID: 3 at filepath: .\yesautohandel\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\yesautohandel\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-11 15:28:14 4212 [Note] Plugin 'FEDERATED' is disabled.
2013-10-11 15:28:14 1078 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-11 15:28:14 4212 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-11 15:28:14 4212 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-11 15:28:14 4212 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-11 15:28:14 4212 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-11 15:28:14 4212 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-11 15:28:14 4212 [Note] InnoDB: Completed initialization of buffer pool
2013-10-11 15:28:14 4212 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-11 15:28:14 4212 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2524657 in the ib_logfiles!
2013-10-11 15:28:14 4212 [Note] InnoDB: Database was not shutdown normally!
2013-10-11 15:28:14 4212 [Note] InnoDB: Starting crash recovery.
2013-10-11 15:28:14 4212 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-11 15:28:14 4212 [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 yesautohandel/wp_terms which uses space ID: 3 at filepath: .\yesautohandel\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\yesautohandel\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-11 15:28:21 4368 [Note] Plugin 'FEDERATED' is disabled.
2013-10-11 15:28:21 1114 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-11 15:28:21 4368 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-11 15:28:21 4368 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-11 15:28:21 4368 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-11 15:28:21 4368 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-11 15:28:21 4368 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-11 15:28:21 4368 [Note] InnoDB: Completed initialization of buffer pool
2013-10-11 15:28:21 4368 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-11 15:28:21 4368 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2524657 in the ib_logfiles!
2013-10-11 15:28:21 4368 [Note] InnoDB: Database was not shutdown normally!
2013-10-11 15:28:21 4368 [Note] InnoDB: Starting crash recovery.
2013-10-11 15:28:21 4368 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-11 15:28:21 4368 [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 yesautohandel/wp_terms which uses space ID: 3 at filepath: .\yesautohandel\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\yesautohandel\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.