xamppエラー：MySQLのシャットダウンが予期せず終了しました。シャットダウンする前に電源を忘れてしまいました。

Question

最近このエラーが発生しています。私はエラーが私がコンピュータをシャットダウンするときにmysqlのターンを忘れて原因であることに気付いた。私はデータフォルダ内のibdata1を削除しようとしていましたが、この状況では機能しません。以下は私のエラーログです。 configまたは他の方法の代わりに、再インストールXAMPPによってこの問題を解決する方法

2016-08-15 12:11:33 1b48 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. 
2016-08-15 12:11:33 6984 [Note] InnoDB: Using mutexes to ref count buffer pool pages 
2016-08-15 12:11:33 6984 [Note] InnoDB: The InnoDB memory heap is disabled 
2016-08-15 12:11:33 6984 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 
2016-08-15 12:11:33 6984 [Note] InnoDB: Memory barrier is not used 
2016-08-15 12:11:33 6984 [Note] InnoDB: Compressed tables use zlib 1.2.3 
2016-08-15 12:11:33 6984 [Note] InnoDB: Using generic crc32 instructions 
2016-08-15 12:11:33 6984 [Note] InnoDB: Initializing buffer pool, size = 16.0M 
2016-08-15 12:11:33 6984 [Note] InnoDB: Completed initialization of buffer pool 
2016-08-15 12:11:33 6984 [Note] InnoDB: Highest supported file format is Barracuda. 
2016-08-15 12:11:33 6984 [Note] InnoDB: The log sequence numbers 8656625 and 8656625 in ibdata files do not match the log sequence number 8656635 in the ib_logfiles! 
2016-08-15 12:11:33 6984 [Note] InnoDB: Database was not shutdown normally! 
2016-08-15 12:11:33 6984 [Note] InnoDB: Starting crash recovery. 
2016-08-15 12:11:33 6984 [Note] InnoDB: Reading tablespace information from the .ibd files... 
2016-08-15 12:11:36 6984 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace drupaltest/variable uses space ID: 31 at filepath: .\drupaltest\variable.ibd. Cannot open tablespace livestream/tbl_user which uses space ID: 31 at filepath: .\livestream\tbl_user.ibd 
InnoDB: Error: could not open single-table tablespace file .\livestream\tbl_user.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 

Answer 1

ねえ、私はちょうどこれをしなかったし、それが働いた：

があなたのCに行く

1. 終了XAMPPサーバー： \ xampp \ mysql \ dataディレクトリ
2. ibdata1ファイルを削除する
3. xamppサーバーを再起動する

それは