Power Fail Today Mysql error 2002
Posted by: trybefore (---.dip0.t-ipconnect.de)
Date: November 29, 2013 04:31PM

Running Win7-64bit, Wamp 2.2, Apache 2.2.22, Php 5.3.13, Msql 5.6.12

This installation has been running fine for months until I had a power fail today which appears to have corrupted something important. No apache or php errors in log files.
Mysql error log here:
2013-11-29 16:04:09 3400 [Note] Plugin 'FEDERATED' is disabled.
2013-11-29 16:04:09 3400 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-29 16:04:09 3400 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-29 16:04:09 3400 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-29 16:04:09 3400 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-29 16:04:09 3400 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-11-29 16:04:09 3400 [Note] InnoDB: Completed initialization of buffer pool
2013-11-29 16:04:09 3400 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-29 16:04:16 3400 [Note] InnoDB: 128 rollback segment(s) are active.
2013-11-29 16:04:16 3400 [Note] InnoDB: Waiting for purge to start
2013-11-29 16:04:16 3400 [Note] InnoDB: 5.6.12 started; log sequence number 631522173
2013-11-29 16:04:20 3400 [Note] Server hostname (bind-address): '*'; port: 3306
2013-11-29 16:04:20 3400 [Note] IPv6 is available.
2013-11-29 16:04:20 3400 [Note] - '::' resolves to '::';
2013-11-29 16:04:20 3400 [Note] Server socket created on IP: '::'.
2013-11-29 16:04:20 3400 [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 [dev.mysql.com] for how you can resolve the problem.
2013-11-29 16:04:20 3400 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2013-11-29 16:04:20 3400 [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 [dev.mysql.com] for how you can resolve the problem.
2013-11-29 16:04:20 3400 [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 [dev.mysql.com] for how you can resolve the problem.
2013-11-29 16:04:20 3400 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2013-11-29 16:04:20 3400 [ERROR] Column count of mysql.events_waits_current is wrong. Expected 19, found 16. Created with MySQL 50520, now running 50612. Please use mysql_upgrade to fix this error.
2013-11-29 16:04:20 3400 [ERROR] Column count of mysql.events_waits_history is wrong. Expected 19, found 16. Created with MySQL 50520, now running 50612. Please use mysql_upgrade to fix this error.
2013-11-29 16:04:20 3400 [ERROR] Column count of mysql.events_waits_history_long is wrong. Expected 19, found 16. Created with MySQL 50520, now running 50612. Please use mysql_upgrade to fix this error.
2013-11-29 16:04:20 3400 [ERROR] Incorrect definition of table performance_schema.events_waits_summary_by_thread_by_event_name: expected column 'THREAD_ID' at position 0 to have type bigint(20), found type int(11).
2013-11-29 16:04:20 3400 [ERROR] Column count of mysql.file_summary_by_event_name is wrong. Expected 23, found 5. Created with MySQL 50520, now running 50612. Please use mysql_upgrade to fix this error.
2013-11-29 16:04:20 3400 [ERROR] Column count of mysql.file_summary_by_instance is wrong. Expected 25, found 6. Created with MySQL 50520, now running 50612. Please use mysql_upgrade to fix this error.
2013-11-29 16:04:20 3400 [ERROR] Incorrect definition of table performance_schema.mutex_instances: expected column 'LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
2013-11-29 16:04:20 3400 [ERROR] Incorrect definition of table performance_schema.rwlock_instances: expected column 'WRITE_LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
2013-11-29 16:04:20 3400 [ERROR] Column count of mysql.threads is wrong. Expected 14, found 3. Created with MySQL 50520, now running 50612. Please use mysql_upgrade to fix this error.
2013-11-29 16:04:20 3400 [Note] Event Scheduler: Loaded 0 events
2013-11-29 16:04:20 3400 [Note] wampmysqld: ready for connections.
Version: '5.6.12-log' socket: '' port: 3306 MySQL Community Server (GPL)

Simple html sites are served ok. CMSs are naturally not starting.

Not sure where to start. Some handholding would be appreciated.

Options: ReplyQuote
Re: Power Fail Today Mysql error 2002
Posted by: RiggsFolly (---.as13285.net)
Date: December 01, 2013 04:22PM

Seems like the innodb databases got corrupted by the crash.

Checkout [dev.mysql.com] for how to get MySQL to recover from this kind of situation.

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>

Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Options: ReplyQuote


Sorry, only registered users may post in this forum.