Group: Member Post Group: Newbie
Posts: 3
Status:  |
Please help. New install of AMPPS and MySQL will not start. Error in error log below. Not sure how to proceed. Any help would be appreciated. Thanks.
2014-03-08 16:40:07 7260 [Warning] You need to use --log-bin to make --binlog-format work.
2014-03-08 16:40:07 7260 [Note] Plugin 'FEDERATED' is disabled.
2014-03-08 16:40:07 7260 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-03-08 16:40:07 7260 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-08 16:40:07 7260 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-08 16:40:07 7260 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-08 16:40:07 7260 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-08 16:40:07 7260 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-03-08 16:40:07 7260 [Note] InnoDB: Completed initialization of buffer pool
2014-03-08 16:40:07 7260 [Note] InnoDB: The first specified data file .\ibdata1 did not exist: a new database to be created!
2014-03-08 16:40:07 7260 [Note] InnoDB: Setting file .\ibdata1 size to 12 MB
2014-03-08 16:40:07 7260 [Note] InnoDB: Database physically writes the file full: wait...
2014-03-08 16:40:08 7260 [Note] InnoDB: Setting log file .\ib_logfile101 size to 48 MB
2014-03-08 16:40:11 7260 [Note] InnoDB: Setting log file .\ib_logfile1 size to 48 MB
2014-03-08 16:40:13 1c60 InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: ht*p://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2014-03-08 16:40:13 7260 [ERROR] InnoDB: File .\ib_logfile101: 'aio write' returned OS error 187. Cannot continue operation
2014-03-08 19:01:15 3732 [Warning] You need to use --log-bin to make --binlog-format work.
2014-03-08 19:01:15 3732 [Note] Plugin 'FEDERATED' is disabled.
2014-03-08 19:01:15 3732 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-03-08 19:01:15 3732 [Note] InnoDB: The InnoDB memory heap is disabled
2014-03-08 19:01:15 3732 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-03-08 19:01:15 3732 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-03-08 19:01:15 3732 [Note] InnoDB: Not using CPU crc32 instructions
2014-03-08 19:01:15 3732 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-03-08 19:01:15 3732 [Note] InnoDB: Completed initialization of buffer pool
2014-03-08 19:01:15 3732 [ERROR] InnoDB: space header page consists of zero bytes in data file .\ibdata1
2014-03-08 19:01:15 3732 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2014-03-08 19:01:15 3732 [ERROR] Plugin 'InnoDB' init function returned error.
2014-03-08 19:01:15 3732 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2014-03-08 19:01:15 3732 [ERROR] Unknown/unsupported storage engine: InnoDB
2014-03-08 19:01:15 3732 [ERROR] Aborting2014-03-08 19:01:15 3732 [Note] Binlog end
|
Powered By AEF 1.0.8 © 2007-2008 Electron Inc.
March 9, 2014, 1:36 am
