phpmyadmin/nginx:502 Bad Gateway settlement record

Today the boot run Nginx ready to do local testing, browser opened phpMyAdmin after the nginx process crashes. Open nginx error log "Error.log" does not have any valid information. Then open the phpmyadmin error log "***-pc.err", extract the valid information as follows:

140920 19:34:27 [Note] innodb:using mutexes to ref count buffer pool pages

140920 19:34:27 [Note] innodb:the InnoDB memory heap is disabled

140920 19:34:27 [Note] innodb:mutexes and rw_locks use Windows interlocked functions

140920 19:34:27 [Note] innodb:compressed tables use zlib 1.2.3

140920 19:34:27 [Note] innodb:not using CPU CRC32 instructions

140920 19:34:27 [Note] innodb:initializing buffer pool, size = 128.0M

140920 19:34:27 [Note] innodb:completed initialization of buffer pool

140920 19:34:27 [Note] innodb:highest supported file format is Barracuda.

140920 19:34:27 [Note] innodb:the log sequence numbers 5900060 and 5900060 in Ibdata files does not match the log sequence Number 6080247 in the ib_logfiles!

140920 19:34:27 [Note] innodb:database is not shutdown normally!

140920 19:34:27 [Note] innodb:starting crash recovery.

140920 19:34:27 [Note] innodb:reading tablespace information from the. ibd files ...

2014-09-20 19:34:27 EC4 innodb:operating system error number 2 in a file operation.

Innodb:some Operating system error numbers is described at

Innodb:http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html

InnoDB:Error:could not open single-table tablespace file. \dota2\data_abilities-

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 can be restore it from a backup,

Innodb:then you can remove the. ibd file, and InnoDB would 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, can set innodb_force_recovery > 0 in MY.CNF

Innodb:and force InnoDB to continue crash recovery here.

You can see the error code is 2, check the MySQL official website error code description is "No such file or directory". Back to the error log, the previous sentence of the error code is "Reading tablespace information from the. ibd files ...", the next sentence is "Error:could not open single-table Tablespa CE file. \dota2\data_abilities-". You can see that the error is related to the *. ibd file in the database. \dota2\ directory. Open the directory, and sure enough there is a file data_abilities-copy that was previously backed up manually. ibd. Delete it, restart Nginx and MySQL, open phpMyAdmin again , return to normal.

phpmyadmin/nginx:502 Bad Gateway settlement record