SQL Unexpected shutdown (help Please)

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

SQL Unexpected shutdown (help Please)

Postby mroll13 » 17. September 2013 14:02

SQL keeps shutting down - I'm trying to develop a Joomla 3 site and this manifested itself after installing joomla using the bitnami install tool. Can anyone advise me what I need to chane and how I go about actually instigating the required change

Control Panel Notification

13:57:58 [mysql] Attempting to start MySQL app...
13:57:58 [mysql] Status change detected: running
13:57:59 [mysql] Status change detected: stopped
13:57:59 [mysql] Error: MySQL shutdown unexpectedly.
13:57:59 [mysql] This may be due to a blocked port, missing dependencies,
13:57:59 [mysql] improper privileges, a crash, or a shutdown by another method.
13:57:59 [mysql] Press the Logs button to view error logs and check
13:57:59 [mysql] the Windows Event Viewer for more clues
13:57:59 [mysql] If you need more help, copy and post this
13:57:59 [mysql] entire log window on the forums

Error Log
2013-09-17 12:44:28 4108 [Note] Plugin 'FEDERATED' is disabled.
2013-09-17 12:44:29 1010 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-09-17 12:44:29 4108 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-17 12:44:29 4108 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-17 12:44:29 4108 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-17 12:44:29 4108 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-17 12:44:29 4108 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-17 12:44:29 4108 [Note] InnoDB: Completed initialization of buffer pool
2013-09-17 12:44:29 4108 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2013-09-17 12:44:29 4108 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2013-09-17 12:44:29 4108 [Note] InnoDB: Database physically writes the file full: wait...
2013-09-17 12:44:29 4108 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2013-09-17 12:44:29 4108 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2013-09-17 12:44:30 4108 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2013-09-17 12:44:30 4108 [Warning] InnoDB: New log files created, LSN=45781
2013-09-17 12:44:30 4108 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-09-17 12:44:30 4108 [Note] InnoDB: Doublewrite buffer created
2013-09-17 12:44:31 4108 [Note] InnoDB: 128 rollback segment(s) are active.
2013-09-17 12:44:31 4108 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-09-17 12:44:32 4108 [Note] InnoDB: Foreign key constraint system tables created
2013-09-17 12:44:32 4108 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-09-17 12:44:32 4108 [Note] InnoDB: Tablespace and datafile system tables created.
2013-09-17 12:44:32 4108 [Note] InnoDB: Waiting for purge to start
2013-09-17 12:44:32 4108 [Note] InnoDB: 5.6.11 started; log sequence number 0
2013-09-17 12:44:32 4108 [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: 84d093e5-1f8e-11e3-90a2-002643ad2fe0.
2013-09-17 12:44:32 4108 [Note] Server hostname (bind-address): '*'; port: 3306
2013-09-17 12:44:32 4108 [Note] IPv6 is available.
2013-09-17 12:44:32 4108 [Note] - '::' resolves to '::';
2013-09-17 12:44:32 4108 [Note] Server socket created on IP: '::'.
2013-09-17 13:22:56 5496 [Note] Plugin 'FEDERATED' is disabled.
2013-09-17 13:22:56 10cc 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-09-17 13:22:56 5496 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-17 13:22:56 5496 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-17 13:22:56 5496 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-17 13:22:56 5496 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-17 13:22:56 5496 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-17 13:22:56 5496 [Note] InnoDB: Completed initialization of buffer pool
2013-09-17 13:22:56 5496 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-17 13:22:56 5496 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3000299 in the ib_logfiles!
2013-09-17 13:22:56 5496 [Note] InnoDB: Database was not shutdown normally!
2013-09-17 13:22:56 5496 [Note] InnoDB: Starting crash recovery.
2013-09-17 13:22:56 5496 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-17 13:22:56 5496 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_joomla/jos_associations uses space ID: 2 at filepath: .\bitnami_joomla\jos_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-09-17 13:25:39 5424 [Note] Plugin 'FEDERATED' is disabled.
2013-09-17 13:25:39 15b0 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-09-17 13:25:39 5424 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-17 13:25:39 5424 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-17 13:25:39 5424 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-17 13:25:39 5424 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-17 13:25:39 5424 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-17 13:25:39 5424 [Note] InnoDB: Completed initialization of buffer pool
2013-09-17 13:25:39 5424 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-17 13:25:39 5424 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3000299 in the ib_logfiles!
2013-09-17 13:25:39 5424 [Note] InnoDB: Database was not shutdown normally!
2013-09-17 13:25:39 5424 [Note] InnoDB: Starting crash recovery.
2013-09-17 13:25:39 5424 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-17 13:25:39 5424 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_joomla/jos_associations uses space ID: 2 at filepath: .\bitnami_joomla\jos_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-09-17 13:44:54 5324 [Note] Plugin 'FEDERATED' is disabled.
2013-09-17 13:44:54 89c 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-09-17 13:44:54 5324 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-17 13:44:54 5324 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-17 13:44:54 5324 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-17 13:44:54 5324 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-17 13:44:54 5324 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-17 13:44:54 5324 [Note] InnoDB: Completed initialization of buffer pool
2013-09-17 13:44:54 5324 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-17 13:44:54 5324 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3000299 in the ib_logfiles!
2013-09-17 13:44:54 5324 [Note] InnoDB: Database was not shutdown normally!
2013-09-17 13:44:54 5324 [Note] InnoDB: Starting crash recovery.
2013-09-17 13:44:54 5324 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-17 13:44:54 5324 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_joomla/jos_associations uses space ID: 2 at filepath: .\bitnami_joomla\jos_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-09-17 13:47:07 4752 [Note] Plugin 'FEDERATED' is disabled.
2013-09-17 13:47:07 1470 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-09-17 13:47:07 4752 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-17 13:47:07 4752 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-17 13:47:07 4752 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-17 13:47:07 4752 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-17 13:47:07 4752 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-17 13:47:07 4752 [Note] InnoDB: Completed initialization of buffer pool
2013-09-17 13:47:07 4752 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-17 13:47:07 4752 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3000299 in the ib_logfiles!
2013-09-17 13:47:07 4752 [Note] InnoDB: Database was not shutdown normally!
2013-09-17 13:47:07 4752 [Note] InnoDB: Starting crash recovery.
2013-09-17 13:47:07 4752 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-17 13:47:07 4752 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_joomla/jos_associations uses space ID: 2 at filepath: .\bitnami_joomla\jos_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-09-17 13:48:34 5864 [Note] Plugin 'FEDERATED' is disabled.
2013-09-17 13:48:34 16a8 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-09-17 13:48:34 5864 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-17 13:48:34 5864 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-17 13:48:34 5864 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-17 13:48:34 5864 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-17 13:48:34 5864 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-17 13:48:34 5864 [Note] InnoDB: Completed initialization of buffer pool
2013-09-17 13:48:34 5864 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-17 13:48:34 5864 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3000299 in the ib_logfiles!
2013-09-17 13:48:34 5864 [Note] InnoDB: Database was not shutdown normally!
2013-09-17 13:48:34 5864 [Note] InnoDB: Starting crash recovery.
2013-09-17 13:48:34 5864 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-17 13:48:34 5864 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_joomla/jos_associations uses space ID: 2 at filepath: .\bitnami_joomla\jos_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-09-17 13:48:38 2088 [Note] Plugin 'FEDERATED' is disabled.
2013-09-17 13:48:38 1630 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-09-17 13:48:38 2088 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-17 13:48:38 2088 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-17 13:48:38 2088 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-17 13:48:38 2088 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-17 13:48:38 2088 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-17 13:48:38 2088 [Note] InnoDB: Completed initialization of buffer pool
2013-09-17 13:48:38 2088 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-17 13:48:38 2088 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3000299 in the ib_logfiles!
2013-09-17 13:48:38 2088 [Note] InnoDB: Database was not shutdown normally!
2013-09-17 13:48:38 2088 [Note] InnoDB: Starting crash recovery.
2013-09-17 13:48:38 2088 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-17 13:48:38 2088 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_joomla/jos_associations uses space ID: 2 at filepath: .\bitnami_joomla\jos_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-09-17 13:48:48 2716 [Note] Plugin 'FEDERATED' is disabled.
2013-09-17 13:48:48 d64 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-09-17 13:48:48 2716 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-17 13:48:48 2716 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-17 13:48:48 2716 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-17 13:48:48 2716 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-17 13:48:48 2716 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-17 13:48:48 2716 [Note] InnoDB: Completed initialization of buffer pool
2013-09-17 13:48:48 2716 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-17 13:48:48 2716 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3000299 in the ib_logfiles!
2013-09-17 13:48:48 2716 [Note] InnoDB: Database was not shutdown normally!
2013-09-17 13:48:48 2716 [Note] InnoDB: Starting crash recovery.
2013-09-17 13:48:48 2716 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-17 13:48:48 2716 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_joomla/jos_associations uses space ID: 2 at filepath: .\bitnami_joomla\jos_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-09-17 13:48:50 3968 [Note] Plugin 'FEDERATED' is disabled.
2013-09-17 13:48:50 1270 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-09-17 13:48:50 3968 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-17 13:48:50 3968 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-17 13:48:50 3968 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-17 13:48:50 3968 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-17 13:48:50 3968 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-17 13:48:50 3968 [Note] InnoDB: Completed initialization of buffer pool
2013-09-17 13:48:50 3968 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-17 13:48:50 3968 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3000299 in the ib_logfiles!
2013-09-17 13:48:50 3968 [Note] InnoDB: Database was not shutdown normally!
2013-09-17 13:48:50 3968 [Note] InnoDB: Starting crash recovery.
2013-09-17 13:48:50 3968 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-17 13:48:50 3968 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_joomla/jos_associations uses space ID: 2 at filepath: .\bitnami_joomla\jos_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-09-17 13:54:06 4372 [Note] Plugin 'FEDERATED' is disabled.
2013-09-17 13:54:06 1350 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-09-17 13:54:06 4372 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-17 13:54:06 4372 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-17 13:54:06 4372 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-17 13:54:06 4372 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-17 13:54:06 4372 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-17 13:54:06 4372 [Note] InnoDB: Completed initialization of buffer pool
2013-09-17 13:54:07 4372 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-17 13:54:07 4372 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3000299 in the ib_logfiles!
2013-09-17 13:54:07 4372 [Note] InnoDB: Database was not shutdown normally!
2013-09-17 13:54:07 4372 [Note] InnoDB: Starting crash recovery.
2013-09-17 13:54:07 4372 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-17 13:54:07 4372 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_joomla/jos_associations uses space ID: 2 at filepath: .\bitnami_joomla\jos_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-09-17 13:54:19 3976 [Note] Plugin 'FEDERATED' is disabled.
2013-09-17 13:54:19 4a8 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-09-17 13:54:19 3976 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-17 13:54:19 3976 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-17 13:54:19 3976 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-17 13:54:19 3976 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-17 13:54:19 3976 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-17 13:54:19 3976 [Note] InnoDB: Completed initialization of buffer pool
2013-09-17 13:54:19 3976 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-17 13:54:19 3976 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3000299 in the ib_logfiles!
2013-09-17 13:54:19 3976 [Note] InnoDB: Database was not shutdown normally!
2013-09-17 13:54:19 3976 [Note] InnoDB: Starting crash recovery.
2013-09-17 13:54:19 3976 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-17 13:54:19 3976 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_joomla/jos_associations uses space ID: 2 at filepath: .\bitnami_joomla\jos_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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-09-17 13:57:58 1152 [Note] Plugin 'FEDERATED' is disabled.
2013-09-17 13:57:58 1320 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-09-17 13:57:58 1152 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-17 13:57:58 1152 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-17 13:57:58 1152 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-17 13:57:58 1152 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-17 13:57:58 1152 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-17 13:57:58 1152 [Note] InnoDB: Completed initialization of buffer pool
2013-09-17 13:57:58 1152 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-17 13:57:58 1152 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3000299 in the ib_logfiles!
2013-09-17 13:57:58 1152 [Note] InnoDB: Database was not shutdown normally!
2013-09-17 13:57:58 1152 [Note] InnoDB: Starting crash recovery.
2013-09-17 13:57:58 1152 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-17 13:57:58 1152 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_joomla/jos_associations uses space ID: 2 at filepath: .\bitnami_joomla\jos_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
mroll13
 
Posts: 5
Joined: 07. September 2013 15:36
Operating System: Win 8

Return to MariaDB - MySQL

Who is online

Users browsing this forum: No registered users and 3 guests