Please / Error: MySQL shutdown unexpectedly

Alles, was MariaDB und MySQL betrifft, kann hier besprochen werden.

Please / Error: MySQL shutdown unexpectedly

Postby weeshi » 02. March 2015 12:45

i need Help Please (Mysql Not Running) .. the XAMPP was running great till i Upgraded it to Version: 5.6.3 :cry: MYSQL Stopped Running

================ ERORR LOG=================
12:58:13 م [main] Initializing Control Panel
12:58:13 م [main] Windows Version: Windows 7 Ultimate 32-bit
12:58:13 م [main] XAMPP Version: 5.6.3
12:58:13 م [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ]
12:58:13 م [main] Running with Administrator rights - good!
12:58:13 م [main] XAMPP Installation Directory: "c:\xampp\"
12:58:13 م [main] Checking for prerequisites
12:58:19 م [main] All prerequisites found
12:58:19 م [main] Initializing Modules
12:58:20 م [main] Starting Check-Timer
12:58:20 م [main] Control Panel Ready
12:58:41 م [Apache] Attempting to start Apache app...
12:58:41 م [Apache] Status change detected: running
12:58:44 م [mysql] Attempting to start MySQL app...
12:58:44 م [mysql] Status change detected: running
12:58:56 م [mysql] Status change detected: stopped
12:58:56 م [mysql] Error: MySQL shutdown unexpectedly.
12:58:56 م [mysql] This may be due to a blocked port, missing dependencies,
12:58:56 م [mysql] improper privileges, a crash, or a shutdown by another method.
12:58:56 م [mysql] Press the Logs button to view error logs and check
12:58:56 م [mysql] the Windows Event Viewer for more clues
12:58:56 م [mysql] If you need more help, copy and post this
12:58:56 م [mysql] entire log window on the forums

=================== mysql_error.log ===========================
2015-02-15 01:53:31 7864 [Note] Plugin 'FEDERATED' is disabled.
2015-02-15 01:53:31 19b4 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-15 01:53:31 7864 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-15 01:53:31 7864 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-15 01:53:31 7864 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-15 01:53:31 7864 [Note] InnoDB: Memory barrier is not used
2015-02-15 01:53:31 7864 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-15 01:53:31 7864 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-15 01:53:31 7864 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-15 01:53:31 7864 [Note] InnoDB: Completed initialization of buffer pool
2015-02-15 01:53:31 7864 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-15 01:53:32 7864 [Note] InnoDB: 128 rollback segment(s) are active.
2015-02-15 01:53:32 7864 [Note] InnoDB: Waiting for purge to start
2015-02-15 01:53:32 7864 [Note] InnoDB: 5.6.21 started; log sequence number 1665234
2015-02-15 01:53:32 7864 [Note] Server hostname (bind-address): '*'; port: 3306
2015-02-15 01:53:32 7864 [Note] IPv6 is available.
2015-02-15 01:53:32 7864 [Note] - '::' resolves to '::';
2015-02-15 01:53:32 7864 [Note] Server socket created on IP: '::'.
2015-02-15 01:53:34 7864 [Note] Event Scheduler: Loaded 0 events
2015-02-15 01:53:34 7864 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.21' socket: '' port: 3306 MySQL Community Server (GPL)
2015-02-15 01:59:37 6936 [Note] Plugin 'FEDERATED' is disabled.
2015-02-15 01:59:37 1578 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-15 01:59:37 6936 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-15 01:59:37 6936 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-15 01:59:37 6936 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-15 01:59:37 6936 [Note] InnoDB: Memory barrier is not used
2015-02-15 01:59:37 6936 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-15 01:59:37 6936 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-15 01:59:38 6936 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-15 01:59:38 6936 [Note] InnoDB: Completed initialization of buffer pool
2015-02-15 01:59:38 6936 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-15 01:59:38 6936 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665244 in the ib_logfiles!
2015-02-15 01:59:38 6936 [Note] InnoDB: Database was not shutdown normally!
2015-02-15 01:59:38 6936 [Note] InnoDB: Starting crash recovery.
2015-02-15 01:59:38 6936 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-15 01:59:38 6936 [Note] InnoDB: Restoring possible half-written data pages
2015-02-15 01:59:38 6936 [Note] InnoDB: from the doublewrite buffer...
2015-02-15 01:59:39 6936 [Note] InnoDB: 128 rollback segment(s) are active.
2015-02-15 01:59:39 6936 [Note] InnoDB: Waiting for purge to start
2015-02-15 01:59:39 6936 [Note] InnoDB: 5.6.21 started; log sequence number 1665244
2015-02-15 01:59:39 6936 [Note] Server hostname (bind-address): '*'; port: 3306
2015-02-15 01:59:39 6936 [Note] IPv6 is available.
2015-02-15 01:59:39 6936 [Note] - '::' resolves to '::';
2015-02-15 01:59:39 6936 [Note] Server socket created on IP: '::'.
2015-02-15 01:59:39 6936 [Note] Event Scheduler: Loaded 0 events
2015-02-15 01:59:39 6936 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.21' socket: '' port: 3306 MySQL Community Server (GPL)
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_assets 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_associations 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_banner_clients 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_banner_tracks 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_banners 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_categories 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_contact_details 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_content 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_content_frontpage 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_content_rating 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_content_types 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_contentitem_tag_map 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_core_log_searches 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_extensions 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_finder_filters 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_finder_links 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_finder_links_terms0 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_finder_links_terms1 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_finder_links_terms2 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/o065q_finder_links_terms3 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_ak_profiles 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_ak_stats 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_ak_storage 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_contentitem_tag_map 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_jcklanguages 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.
2015-02-15 05:13:59 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_jckplugins 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_jcktoolbarplugins 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_jcktoolbars 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_postinstall_messages 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_rokgallery_file_loves 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_rokgallery_file_tags 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_rokgallery_file_views 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_rokgallery_files 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_rokgallery_files_index 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_rokgallery_filters 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_rokgallery_galleries 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_rokgallery_jobs 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_rokgallery_profiles 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_rokgallery_schema_version 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_rokgallery_slice_tags 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_rokgallery_slices 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_rokgallery_slices_index 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_tags 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_ucm_content 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_ucm_history 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_update_sites_extensions 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.
2015-02-15 05:14:00 6936 [Warning] InnoDB: Cannot open table allawag/yu3lk_user_keys 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.
2015-02-15 05:42:40 9472 [Note] Plugin 'FEDERATED' is disabled.
2015-02-15 05:42:40 1d2c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-15 05:42:40 9472 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-15 05:42:40 9472 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-15 05:42:40 9472 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-15 05:42:40 9472 [Note] InnoDB: Memory barrier is not used
2015-02-15 05:42:40 9472 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-15 05:42:40 9472 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-15 05:42:40 9472 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-15 05:42:40 9472 [Note] InnoDB: Completed initialization of buffer pool
2015-02-15 05:42:40 9472 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-15 05:42:41 9472 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-02-15 05:42:41 9472 [Note] InnoDB: Database was not shutdown normally!
2015-02-15 05:42:41 9472 [Note] InnoDB: Starting crash recovery.
2015-02-15 05:42:41 9472 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-15 05:42:41 9472 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-02-15 05:44:21 5624 [Note] Plugin 'FEDERATED' is disabled.
2015-02-15 05:44:21 1990 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-15 05:44:21 5624 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-15 05:44:21 5624 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-15 05:44:21 5624 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-15 05:44:21 5624 [Note] InnoDB: Memory barrier is not used
2015-02-15 05:44:21 5624 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-15 05:44:21 5624 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-15 05:44:21 5624 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-15 05:44:21 5624 [Note] InnoDB: Completed initialization of buffer pool
2015-02-15 05:44:21 5624 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-15 05:44:21 5624 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-02-15 05:44:21 5624 [Note] InnoDB: Database was not shutdown normally!
2015-02-15 05:44:21 5624 [Note] InnoDB: Starting crash recovery.
2015-02-15 05:44:21 5624 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-15 05:44:21 5624 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-02-15 05:49:42 7056 [Note] Plugin 'FEDERATED' is disabled.
2015-02-15 05:49:42 1dc8 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-15 05:49:42 7056 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-15 05:49:42 7056 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-15 05:49:42 7056 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-15 05:49:42 7056 [Note] InnoDB: Memory barrier is not used
2015-02-15 05:49:42 7056 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-15 05:49:42 7056 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-15 05:49:42 7056 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-15 05:49:42 7056 [Note] InnoDB: Completed initialization of buffer pool
2015-02-15 05:49:42 7056 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-15 05:49:42 7056 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-02-15 05:49:42 7056 [Note] InnoDB: Database was not shutdown normally!
2015-02-15 05:49:42 7056 [Note] InnoDB: Starting crash recovery.
2015-02-15 05:49:42 7056 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-15 05:49:42 7056 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-02-19 07:58:41 7632 [Note] Plugin 'FEDERATED' is disabled.
2015-02-19 07:58:42 1dcc InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-19 07:58:42 7632 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-19 07:58:42 7632 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-19 07:58:42 7632 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-19 07:58:42 7632 [Note] InnoDB: Memory barrier is not used
2015-02-19 07:58:42 7632 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-19 07:58:42 7632 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-19 07:58:42 7632 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-19 07:58:42 7632 [Note] InnoDB: Completed initialization of buffer pool
2015-02-19 07:58:43 7632 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-19 07:58:43 7632 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-02-19 07:58:43 7632 [Note] InnoDB: Database was not shutdown normally!
2015-02-19 07:58:43 7632 [Note] InnoDB: Starting crash recovery.
2015-02-19 07:58:43 7632 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-19 07:58:44 7632 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-02-19 08:11:37 6568 [Note] Plugin 'FEDERATED' is disabled.
2015-02-19 08:11:37 1ad0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-19 08:11:37 6568 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-19 08:11:37 6568 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-19 08:11:37 6568 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-19 08:11:37 6568 [Note] InnoDB: Memory barrier is not used
2015-02-19 08:11:37 6568 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-19 08:11:37 6568 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-19 08:11:37 6568 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-19 08:11:37 6568 [Note] InnoDB: Completed initialization of buffer pool
2015-02-19 08:11:37 6568 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-19 08:11:37 6568 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-02-19 08:11:37 6568 [Note] InnoDB: Database was not shutdown normally!
2015-02-19 08:11:37 6568 [Note] InnoDB: Starting crash recovery.
2015-02-19 08:11:37 6568 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-19 08:11:37 6568 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-02-19 08:12:51 7232 [Note] Plugin 'FEDERATED' is disabled.
2015-02-19 08:12:51 d9c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-19 08:12:51 7232 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-19 08:12:51 7232 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-19 08:12:51 7232 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-19 08:12:51 7232 [Note] InnoDB: Memory barrier is not used
2015-02-19 08:12:51 7232 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-19 08:12:51 7232 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-19 08:12:51 7232 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-19 08:12:51 7232 [Note] InnoDB: Completed initialization of buffer pool
2015-02-19 08:12:51 7232 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-19 08:12:51 7232 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-02-19 08:12:51 7232 [Note] InnoDB: Database was not shutdown normally!
2015-02-19 08:12:51 7232 [Note] InnoDB: Starting crash recovery.
2015-02-19 08:12:51 7232 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-19 08:12:51 7232 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-02-19 08:15:54 6096 [Note] Plugin 'FEDERATED' is disabled.
2015-02-19 08:15:54 1130 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-19 08:15:54 6096 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-19 08:15:54 6096 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-19 08:15:54 6096 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-19 08:15:54 6096 [Note] InnoDB: Memory barrier is not used
2015-02-19 08:15:54 6096 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-19 08:15:54 6096 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-19 08:15:54 6096 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-19 08:15:54 6096 [Note] InnoDB: Completed initialization of buffer pool
2015-02-19 08:15:54 6096 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-19 08:15:54 6096 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-02-19 08:15:54 6096 [Note] InnoDB: Database was not shutdown normally!
2015-02-19 08:15:54 6096 [Note] InnoDB: Starting crash recovery.
2015-02-19 08:15:54 6096 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-19 08:15:54 6096 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-02-19 08:20:34 5252 [Note] Plugin 'FEDERATED' is disabled.
2015-02-19 08:20:34 1c54 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-19 08:20:34 5252 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-19 08:20:34 5252 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-19 08:20:34 5252 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-19 08:20:34 5252 [Note] InnoDB: Memory barrier is not used
2015-02-19 08:20:34 5252 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-19 08:20:34 5252 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-19 08:20:34 5252 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-19 08:20:34 5252 [Note] InnoDB: Completed initialization of buffer pool
2015-02-19 08:20:34 5252 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-19 08:20:34 5252 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-02-19 08:20:34 5252 [Note] InnoDB: Database was not shutdown normally!
2015-02-19 08:20:34 5252 [Note] InnoDB: Starting crash recovery.
2015-02-19 08:20:34 5252 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-19 08:20:34 5252 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-02-19 08:22:51 2192 [Note] Plugin 'FEDERATED' is disabled.
2015-02-19 08:22:51 1334 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-19 08:22:51 2192 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-19 08:22:51 2192 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-19 08:22:51 2192 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-19 08:22:51 2192 [Note] InnoDB: Memory barrier is not used
2015-02-19 08:22:51 2192 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-19 08:22:51 2192 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-19 08:22:51 2192 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-19 08:22:51 2192 [Note] InnoDB: Completed initialization of buffer pool
2015-02-19 08:22:51 2192 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-19 08:22:51 2192 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-02-19 08:22:51 2192 [Note] InnoDB: Database was not shutdown normally!
2015-02-19 08:22:51 2192 [Note] InnoDB: Starting crash recovery.
2015-02-19 08:22:51 2192 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-19 08:22:51 2192 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-02-19 08:56:00 6952 [Note] Plugin 'FEDERATED' is disabled.
2015-02-19 08:56:00 151c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-19 08:56:00 6952 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-19 08:56:00 6952 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-19 08:56:00 6952 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-19 08:56:00 6952 [Note] InnoDB: Memory barrier is not used
2015-02-19 08:56:00 6952 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-19 08:56:00 6952 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-19 08:56:01 6952 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-19 08:56:01 6952 [Note] InnoDB: Completed initialization of buffer pool
2015-02-19 08:56:01 6952 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-19 08:56:01 6952 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-02-19 08:56:01 6952 [Note] InnoDB: Database was not shutdown normally!
2015-02-19 08:56:01 6952 [Note] InnoDB: Starting crash recovery.
2015-02-19 08:56:01 6952 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-19 08:56:01 6952 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-02-19 08:56:14 1452 [Note] Plugin 'FEDERATED' is disabled.
2015-02-19 08:56:14 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.
2015-02-19 08:56:14 1452 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-19 08:56:14 1452 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-19 08:56:14 1452 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-19 08:56:14 1452 [Note] InnoDB: Memory barrier is not used
2015-02-19 08:56:14 1452 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-19 08:56:14 1452 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-19 08:56:14 1452 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-19 08:56:14 1452 [Note] InnoDB: Completed initialization of buffer pool
2015-02-19 08:56:14 1452 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-19 08:56:14 1452 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-02-19 08:56:14 1452 [Note] InnoDB: Database was not shutdown normally!
2015-02-19 08:56:14 1452 [Note] InnoDB: Starting crash recovery.
2015-02-19 08:56:14 1452 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-19 08:56:14 1452 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-02-19 08:56:16 6960 [Note] Plugin 'FEDERATED' is disabled.
2015-02-19 08:56:16 1404 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-19 08:56:16 6960 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-19 08:56:16 6960 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-19 08:56:16 6960 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-19 08:56:16 6960 [Note] InnoDB: Memory barrier is not used
2015-02-19 08:56:16 6960 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-19 08:56:16 6960 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-19 08:56:16 6960 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-19 08:56:16 6960 [Note] InnoDB: Completed initialization of buffer pool
2015-02-19 08:56:16 6960 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-19 08:56:17 6960 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-02-19 08:56:17 6960 [Note] InnoDB: Database was not shutdown normally!
2015-02-19 08:56:17 6960 [Note] InnoDB: Starting crash recovery.
2015-02-19 08:56:17 6960 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-19 08:56:17 6960 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-02-19 09:03:06 5712 [Note] Plugin 'FEDERATED' is disabled.
2015-02-19 09:03:06 1b68 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-19 09:03:06 5712 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-19 09:03:06 5712 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-19 09:03:06 5712 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-19 09:03:06 5712 [Note] InnoDB: Memory barrier is not used
2015-02-19 09:03:06 5712 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-19 09:03:06 5712 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-19 09:03:06 5712 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-02-19 09:03:06 5712 [Note] InnoDB: Completed initialization of buffer pool
2015-02-19 09:03:06 5712 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-19 09:03:06 5712 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-02-19 09:03:06 5712 [Note] InnoDB: Database was not shutdown normally!
2015-02-19 09:03:06 5712 [Note] InnoDB: Starting crash recovery.
2015-02-19 09:03:06 5712 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-19 09:03:06 5712 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-03-02 12:58:49 11572 [Note] Plugin 'FEDERATED' is disabled.
2015-03-02 12:58:51 169c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-03-02 12:58:51 11572 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-03-02 12:58:51 11572 [Note] InnoDB: The InnoDB memory heap is disabled
2015-03-02 12:58:51 11572 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-03-02 12:58:51 11572 [Note] InnoDB: Memory barrier is not used
2015-03-02 12:58:51 11572 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-03-02 12:58:51 11572 [Note] InnoDB: Not using CPU crc32 instructions
2015-03-02 12:58:52 11572 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-03-02 12:58:52 11572 [Note] InnoDB: Completed initialization of buffer pool
2015-03-02 12:58:53 11572 [Note] InnoDB: Highest supported file format is Barracuda.
2015-03-02 12:58:53 11572 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665254 in the ib_logfiles!
2015-03-02 12:58:53 11572 [Note] InnoDB: Database was not shutdown normally!
2015-03-02 12:58:53 11572 [Note] InnoDB: Starting crash recovery.
2015-03-02 12:58:53 11572 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-03-02 12:58:55 11572 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace allawag/o065q_content_types uses space ID: 240 at filepath: .\allawag\o065q_content_types.ibd. Cannot open tablespace allawag/yu3lk_content_types which uses space ID: 240 at filepath: .\allawag\yu3lk_content_types.ibd
InnoDB: Error: could not open single-table tablespace file .\allawag\yu3lk_content_types.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.
weeshi
 
Posts: 1
Joined: 02. March 2015 12:34
Operating System: Windows 7 Ultimate 32-bit

Re: Please / Error: MySQL shutdown unexpectedly

Postby Nobbie » 02. March 2015 20:48

weeshi wrote:i need Help Please (Mysql Not Running) .. the XAMPP was running great till i Upgraded it to Version: 5.6.3 :cry:


Why did you "upgrade"? What did not work correctly?

There is no upgrade procedure for Xampp anyway. Seems, you have destroyed your working installation. For which reason?
Nobbie
 
Posts: 8779
Joined: 09. March 2008 13:04


Return to MariaDB - MySQL

Who is online

Users browsing this forum: No registered users and 2 guests