apmserv 5.2.6 MySQL5.1启动失败，启动

目前苹果并没有给出相关的解释和相应对策，根据twitter和reddit的上大神讨论消息，iphone用户出现此类情况的原因可能与近期ios的版本更新有关，ios11.1.2中出现日期相关的错误，iphone在12月2日上午12点15分之后收到基于时间的本地通知时apmserv启动失败，就会触发崩溃，出现黑屏死机情况。只有下载时apmserv启动失败，才会触发peer.exe、peerconf.exe和peeradapter.exe这3个进程.通常在下载的时候,这3个程序都会一起运行.如果手动终止,将会导致下载错误.重新打开下载程序即可解决.version3.0以上版本，启动peer.exe进程，在启动项中去掉即可。只有下载时，才会触发peer.exe、peerconf.exe和peeradapter.exe这3个进程.通常在下载的时候,这3个程序都会一起运行.如果手动终止,将会导致下载错误.重新打开下载程序即可解决.version 3.0以上版本，启动peer.exe进程，在启动项中去掉即可。

下面是错误日志：

InnoDB: The first specified data file .\ibdata1 did not exist:

InnoDB: a new database to be created!

120727 16:08:17 InnoDB: Setting file .\ibdata1 size to 10 MB

InnoDB: Database physically writes the file full: wait...

120727 16:08:17 InnoDB: Log file .\ib_logfile0 did not exist: new to be created

innodb: setting log file c:\iblogs\ib_logfile2 size to 31457280。innodb: setting log file c:\iblogs\ib_logfile1 size to 31457280。innodb: setting file c:\ibdata\ibdata1 size to 209715200。

InnoDB: Database physically writes the file full: wait...

120727 16:08:17 InnoDB: Log file .\ib_logfile1 did not exist: new to be created

InnoDB: Setting log file .\ib_logfile1 size to 5 MB

a full database backup backs up the whole database. this includes part of the transaction log so that the full database can be recovered after a full database backup is restored. full database backups represent the database at the time the backup finished.。which is full circle, because in "wait/weight," morris writes about some of the frustrations he faced as a kid in those schools.。one key difference between the input parameters for the gui setup and the windows powershell command is the db file path. the gui expects the path to the folder where db files will be stored whereas the windows powershell command expects the full path to the database file (.mdf file), even though the file might not exist during setup and will be created by sql during the database creation.。

InnoDB: Doublewrite buffer not found: creating new

InnoDB: Doublewrite buffer created

InnoDB: Creating foreign key constraint system tables

InnoDB: Foreign key constraint system tables created

120727 16:08:18 InnoDB: Started; log sequence number 0 0

fatal error: can't open and lock privilege tables: table 'mysql.host' doesn't exist。4.当报：[error] fatal error: can't open and lock privilege tables: can't find file: './mysql/user.frm' (errno: 13 - permission denied)。this occurs when the thread creates a table (including internal temporary tables), at the end of the function that creates the table. this state is used even if the table could not be created due to some error.。

本文来自电脑杂谈，转载请注明本文网址：
http://www.pc-fly.com/a/ruanjian/article-109413-1.html