Error: MySQL shutdown unexpectedly.

[skeeterz71]

Hi,

MySQL worked fine yesterday. I don't know what happened. I do know I have my customer management and severl dev sites in the database! I need help. Any help will be appreciated. Thanks

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

/*****Error Log*****/

2015-04-19 13:10:03 5424 [Note] Plugin 'FEDERATED' is disabled.
2015-04-19 13:10:03 f74 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-04-19 13:10:03 5424 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-04-19 13:10:03 5424 [Note] InnoDB: The InnoDB memory heap is disabled
2015-04-19 13:10:03 5424 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-04-19 13:10:03 5424 [Note] InnoDB: Memory barrier is not used
2015-04-19 13:10:03 5424 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-04-19 13:10:03 5424 [Note] InnoDB: Not using CPU crc32 instructions
2015-04-19 13:10:03 5424 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-04-19 13:10:03 5424 [Note] InnoDB: Completed initialization of buffer pool
2015-04-19 13:10:04 5424 [Note] InnoDB: Highest supported file format is Barracuda.
2015-04-19 13:10:04 5424 [Note] InnoDB: The log sequence numbers 21777452 and 21777452 in ibdata files do not match the log sequence number 22259861 in the ib_logfiles!
2015-04-19 13:10:04 5424 [Note] InnoDB: Database was not shutdown normally!
2015-04-19 13:10:04 5424 [Note] InnoDB: Starting crash recovery.
2015-04-19 13:10:04 5424 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-04-19 13:10:04 5424 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats-Todd-PC uses space ID: 2 at filepath: .\mysql\innodb_index_stats-todd-pc.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.

[skeeterz71]

On another not, I can no longer login to phpMyAdmin MySQL. Connection for controluser as defined in your configuration failed.

[mark.mcdonald]

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.

Did you try going to phpmyadmin after your mysql shutdown? Does your mysql work again or was this an issue before the unexpected shutdown?

[skeeterz71]

No issues before the shutdown. I tried to go to phpmyadmin and could no longer login.

[mark.mcdonald]

So from my understanding you have successfully gotten mysql to run since without error (besides your login credentials not working).
Check your log files again and make sure there are no "2015-04-19 13:10:04 5424 [ERROR]" since this one. Because of the crash I suspect your ibd file is still an issue preventing you from using your login credentials.
I would suggest either making a backup and try replacing the file with a freshly downloaded one or forcing a full recovery by setting innodb_force_recovery > 0 in my.cnf

[Altrea]

I just reference to an old Bug report because the workaround should still work:
viewtopic.php?f=16&t=66746&p=230644#p230644