MySql

MySql

clueless	# July 9, 2014, 1:49 pm \| Post: 2
Group: Member Post Group: Newbie Posts: 11 Status:	I just restarted my Mac and AMPPS. According to the Control Panel, both Apache and MySql started successfully. Here is the error message displayed when I attempt to launch my Joomla page:Error displaying the error page: Application Instantiation Error: Could not connect to MySQL. Here is the error log:2014-07-09 06:34:38 937 [Warning] You need to use --log-bin to make --binlog-format work. 2014-07-09 06:34:38 937 [Note] Plugin 'FEDERATED' is disabled. 2014-07-09 06:34:38 937 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-07-09 06:34:38 937 [Note] InnoDB: The InnoDB memory heap is disabled 2014-07-09 06:34:38 937 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-07-09 06:34:38 937 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-07-09 06:34:38 937 [Note] InnoDB: Not using CPU crc32 instructions 2014-07-09 06:34:38 937 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2014-07-09 06:34:38 937 [Note] InnoDB: Completed initialization of buffer pool 2014-07-09 06:34:38 937 [Note] InnoDB: Highest supported file format is Barracuda. 2014-07-09 06:34:38 937 [Note] InnoDB: The log sequence numbers 4202342 and 4202342 in ibdata files do not match the log sequence number 7030899 in the ib_logfiles! 2014-07-09 06:34:38 937 [Note] InnoDB: Database was not shutdown normally! 2014-07-09 06:34:38 937 [Note] InnoDB: Starting crash recovery. 2014-07-09 06:34:38 937 [Note] InnoDB: Reading tablespace information from the .ibd files... 2014-07-09 06:34:41 937 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace dhl/jos_associations uses space ID: 2 at filepath: ./dhl/jos_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: ./mysql/innodb_index_stats.ibd 2014-07-09 06:34:41 a16531a8 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. 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. 2014-07-09 06:45:19 337 [Warning] You need to use --log-bin to make --binlog-format work. 2014-07-09 06:45:19 337 [Note] Plugin 'FEDERATED' is disabled. 2014-07-09 06:45:19 337 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-07-09 06:45:19 337 [Note] InnoDB: The InnoDB memory heap is disabled 2014-07-09 06:45:19 337 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-07-09 06:45:19 337 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-07-09 06:45:19 337 [Note] InnoDB: Not using CPU crc32 instructions 2014-07-09 06:45:19 337 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2014-07-09 06:45:19 337 [Note] InnoDB: Completed initialization of buffer pool 2014-07-09 06:45:19 337 [Note] InnoDB: Highest supported file format is Barracuda. 2014-07-09 06:45:19 337 [Note] InnoDB: The log sequence numbers 4202342 and 4202342 in ibdata files do not match the log sequence number 7030899 in the ib_logfiles! 2014-07-09 06:45:19 337 [Note] InnoDB: Database was not shutdown normally! 2014-07-09 06:45:19 337 [Note] InnoDB: Starting crash recovery. 2014-07-09 06:45:19 337 [Note] InnoDB: Reading tablespace information from the .ibd files... 2014-07-09 06:45:21 337 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace dhl/jos_associations uses space ID: 2 at filepath: ./dhl/jos_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: ./mysql/innodb_index_stats.ibd 2014-07-09 06:45:21 a16531a8 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. 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.
IP: --

Users viewing this topic
	1 guests, 0 users.