MySQL Server won't start on MAMP for Windows
0
MySQL Server is not starting on my Windows machine despite working when I last used it a few weeks ago.
There are no other mysql processes running as far as I can tell and I have tried using different ports and deleting ib_logfile1, ib_logfile101 and ibdata1 in MAMP/db/mysql and restarting to no success.
This is what appears in the mysql_error_log.err file:
2018-02-27 18:47:07 2128 [Note] Plugin 'FEDERATED' is disabled.
2018-02-27 18:47:07 2128 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-02-27 18:47:07 2128 [Note] InnoDB: The InnoDB memory heap is disabled
2018-02-27 18:47:07 2128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-02-27 18:47:07 2128 [Note] InnoDB: Memory barrier is not used
2018-02-27 18:47:07 2128 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-02-27 18:47:07 2128 [Note] InnoDB: Not using CPU crc32 instructions
2018-02-27 18:47:07 2128 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-02-27 18:47:07 2128 [Note] InnoDB: Completed initialization of buffer pool
2018-02-27 18:47:07 2128 [Note] InnoDB: Restoring page 0 of tablespace 0
2018-02-27 18:47:07 2128 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2018-02-27 18:47:07 2128 [ERROR] InnoDB: space header page consists of zero bytes in data file .ibdata1
2018-02-27 18:47:07 2128 [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!
2018-02-27 18:47:07 2128 [ERROR] Plugin 'InnoDB' init function returned error.
2018-02-27 18:47:07 2128 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-02-27 18:47:07 2128 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-02-27 18:47:07 2128 [ERROR] Aborting
2018-02-27 18:47:07 2128 [Note] Binlog end
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'partition'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_METRICS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMPMEM'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_LOCKS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_TRX'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'BLACKHOLE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'ARCHIVE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'MRG_MYISAM'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'MyISAM'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'MEMORY'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'CSV'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'sha256_password'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'mysql_old_password'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'mysql_native_password'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'binlog'
2018-02-27 18:47:07 2128 [Note] D:MAMP\binmysqlbinmysqld.exe: Shutdown complete
Any help would be greatly appreciated.
mysql mamp
asked Feb 27 '18 at 9:18
CalleCalle
11
|
show 2 more comments
0
MySQL Server is not starting on my Windows machine despite working when I last used it a few weeks ago.
There are no other mysql processes running as far as I can tell and I have tried using different ports and deleting ib_logfile1, ib_logfile101 and ibdata1 in MAMP/db/mysql and restarting to no success.
This is what appears in the mysql_error_log.err file:
2018-02-27 18:47:07 2128 [Note] Plugin 'FEDERATED' is disabled.
2018-02-27 18:47:07 2128 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-02-27 18:47:07 2128 [Note] InnoDB: The InnoDB memory heap is disabled
2018-02-27 18:47:07 2128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-02-27 18:47:07 2128 [Note] InnoDB: Memory barrier is not used
2018-02-27 18:47:07 2128 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-02-27 18:47:07 2128 [Note] InnoDB: Not using CPU crc32 instructions
2018-02-27 18:47:07 2128 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-02-27 18:47:07 2128 [Note] InnoDB: Completed initialization of buffer pool
2018-02-27 18:47:07 2128 [Note] InnoDB: Restoring page 0 of tablespace 0
2018-02-27 18:47:07 2128 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2018-02-27 18:47:07 2128 [ERROR] InnoDB: space header page consists of zero bytes in data file .ibdata1
2018-02-27 18:47:07 2128 [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!
2018-02-27 18:47:07 2128 [ERROR] Plugin 'InnoDB' init function returned error.
2018-02-27 18:47:07 2128 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-02-27 18:47:07 2128 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-02-27 18:47:07 2128 [ERROR] Aborting
2018-02-27 18:47:07 2128 [Note] Binlog end
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'partition'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_METRICS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMPMEM'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_LOCKS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_TRX'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'BLACKHOLE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'ARCHIVE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'MRG_MYISAM'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'MyISAM'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'MEMORY'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'CSV'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'sha256_password'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'mysql_old_password'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'mysql_native_password'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'binlog'
2018-02-27 18:47:07 2128 [Note] D:MAMP\binmysqlbinmysqld.exe: Shutdown complete
Any help would be greatly appreciated.
mysql mamp
asked Feb 27 '18 at 9:18
CalleCalle
11
What error message do you get when you try to run it?
– Darius
Feb 27 '18 at 9:35
@Darius There is no error message, the loading bar just disappears and the server never starts up.
– Calle
Feb 27 '18 at 9:42
In the directory where the MySQL data is stored look for a file with an extension of .err. The startup problem will likely be detailed in that file.
– Dave
Feb 27 '18 at 13:58
@Dave I have updated my question with the contents of the mysql_error_log.err file. Does it mean anything to you?
– Calle
Feb 27 '18 at 18:54
ibdata1 is the storage space for InnoDB since you erased it the InnoDB engine is not happy and can't start. If you have a copy of it someplace restore it and try to start the server again. If you don't the accepted answer dba.stackexchange.com/questions/57120/… explains how you can recreate it.
– Dave
Feb 27 '18 at 19:00
|
show 2 more comments
0
0
0
MySQL Server is not starting on my Windows machine despite working when I last used it a few weeks ago.
There are no other mysql processes running as far as I can tell and I have tried using different ports and deleting ib_logfile1, ib_logfile101 and ibdata1 in MAMP/db/mysql and restarting to no success.
This is what appears in the mysql_error_log.err file:
2018-02-27 18:47:07 2128 [Note] Plugin 'FEDERATED' is disabled.
2018-02-27 18:47:07 2128 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-02-27 18:47:07 2128 [Note] InnoDB: The InnoDB memory heap is disabled
2018-02-27 18:47:07 2128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-02-27 18:47:07 2128 [Note] InnoDB: Memory barrier is not used
2018-02-27 18:47:07 2128 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-02-27 18:47:07 2128 [Note] InnoDB: Not using CPU crc32 instructions
2018-02-27 18:47:07 2128 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-02-27 18:47:07 2128 [Note] InnoDB: Completed initialization of buffer pool
2018-02-27 18:47:07 2128 [Note] InnoDB: Restoring page 0 of tablespace 0
2018-02-27 18:47:07 2128 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2018-02-27 18:47:07 2128 [ERROR] InnoDB: space header page consists of zero bytes in data file .ibdata1
2018-02-27 18:47:07 2128 [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!
2018-02-27 18:47:07 2128 [ERROR] Plugin 'InnoDB' init function returned error.
2018-02-27 18:47:07 2128 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-02-27 18:47:07 2128 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-02-27 18:47:07 2128 [ERROR] Aborting
2018-02-27 18:47:07 2128 [Note] Binlog end
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'partition'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_METRICS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMPMEM'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_LOCKS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_TRX'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'BLACKHOLE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'ARCHIVE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'MRG_MYISAM'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'MyISAM'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'MEMORY'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'CSV'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'sha256_password'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'mysql_old_password'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'mysql_native_password'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'binlog'
2018-02-27 18:47:07 2128 [Note] D:MAMP\binmysqlbinmysqld.exe: Shutdown complete
Any help would be greatly appreciated.
mysql mamp
asked Feb 27 '18 at 9:18
CalleCalle
11
MySQL Server is not starting on my Windows machine despite working when I last used it a few weeks ago.
There are no other mysql processes running as far as I can tell and I have tried using different ports and deleting ib_logfile1, ib_logfile101 and ibdata1 in MAMP/db/mysql and restarting to no success.
This is what appears in the mysql_error_log.err file:
2018-02-27 18:47:07 2128 [Note] Plugin 'FEDERATED' is disabled.
2018-02-27 18:47:07 2128 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-02-27 18:47:07 2128 [Note] InnoDB: The InnoDB memory heap is disabled
2018-02-27 18:47:07 2128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-02-27 18:47:07 2128 [Note] InnoDB: Memory barrier is not used
2018-02-27 18:47:07 2128 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-02-27 18:47:07 2128 [Note] InnoDB: Not using CPU crc32 instructions
2018-02-27 18:47:07 2128 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-02-27 18:47:07 2128 [Note] InnoDB: Completed initialization of buffer pool
2018-02-27 18:47:07 2128 [Note] InnoDB: Restoring page 0 of tablespace 0
2018-02-27 18:47:07 2128 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2018-02-27 18:47:07 2128 [ERROR] InnoDB: space header page consists of zero bytes in data file .ibdata1
2018-02-27 18:47:07 2128 [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!
2018-02-27 18:47:07 2128 [ERROR] Plugin 'InnoDB' init function returned error.
2018-02-27 18:47:07 2128 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-02-27 18:47:07 2128 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-02-27 18:47:07 2128 [ERROR] Aborting
2018-02-27 18:47:07 2128 [Note] Binlog end
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'partition'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_METRICS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMPMEM'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_CMP'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_LOCKS'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'INNODB_TRX'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'BLACKHOLE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'ARCHIVE'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'MRG_MYISAM'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'MyISAM'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'MEMORY'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'CSV'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'sha256_password'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'mysql_old_password'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'mysql_native_password'
2018-02-27 18:47:07 2128 [Note] Shutting down plugin 'binlog'
2018-02-27 18:47:07 2128 [Note] D:MAMP\binmysqlbinmysqld.exe: Shutdown complete
Any help would be greatly appreciated.
mysql mamp
mysql mamp
asked Feb 27 '18 at 9:18
CalleCalle
11
asked Feb 27 '18 at 9:18
CalleCalle
11
edited Feb 27 '18 at 18:52
Calle
asked Feb 27 '18 at 9:18
CalleCalle
11
asked Feb 27 '18 at 9:18
CalleCalle
11
asked Feb 27 '18 at 9:18
CalleCalle
11
11
What error message do you get when you try to run it?
– Darius
Feb 27 '18 at 9:35
@Darius There is no error message, the loading bar just disappears and the server never starts up.
– Calle
Feb 27 '18 at 9:42
In the directory where the MySQL data is stored look for a file with an extension of .err. The startup problem will likely be detailed in that file.
– Dave
Feb 27 '18 at 13:58
@Dave I have updated my question with the contents of the mysql_error_log.err file. Does it mean anything to you?
– Calle
Feb 27 '18 at 18:54
ibdata1 is the storage space for InnoDB since you erased it the InnoDB engine is not happy and can't start. If you have a copy of it someplace restore it and try to start the server again. If you don't the accepted answer dba.stackexchange.com/questions/57120/… explains how you can recreate it.
– Dave
Feb 27 '18 at 19:00
|
show 2 more comments
What error message do you get when you try to run it?
– Darius
Feb 27 '18 at 9:35
@Darius There is no error message, the loading bar just disappears and the server never starts up.
– Calle
Feb 27 '18 at 9:42
In the directory where the MySQL data is stored look for a file with an extension of .err. The startup problem will likely be detailed in that file.
– Dave
Feb 27 '18 at 13:58
@Dave I have updated my question with the contents of the mysql_error_log.err file. Does it mean anything to you?
– Calle
Feb 27 '18 at 18:54
ibdata1 is the storage space for InnoDB since you erased it the InnoDB engine is not happy and can't start. If you have a copy of it someplace restore it and try to start the server again. If you don't the accepted answer dba.stackexchange.com/questions/57120/… explains how you can recreate it.
– Dave
Feb 27 '18 at 19:00
What error message do you get when you try to run it?
– Darius
Feb 27 '18 at 9:35
What error message do you get when you try to run it?
– Darius
Feb 27 '18 at 9:35
@Darius There is no error message, the loading bar just disappears and the server never starts up.
– Calle
Feb 27 '18 at 9:42
@Darius There is no error message, the loading bar just disappears and the server never starts up.
– Calle
Feb 27 '18 at 9:42
In the directory where the MySQL data is stored look for a file with an extension of .err. The startup problem will likely be detailed in that file.
– Dave
Feb 27 '18 at 13:58
In the directory where the MySQL data is stored look for a file with an extension of .err. The startup problem will likely be detailed in that file.
– Dave
Feb 27 '18 at 13:58
@Dave I have updated my question with the contents of the mysql_error_log.err file. Does it mean anything to you?
– Calle
Feb 27 '18 at 18:54
@Dave I have updated my question with the contents of the mysql_error_log.err file. Does it mean anything to you?
– Calle
Feb 27 '18 at 18:54
ibdata1 is the storage space for InnoDB since you erased it the InnoDB engine is not happy and can't start. If you have a copy of it someplace restore it and try to start the server again. If you don't the accepted answer dba.stackexchange.com/questions/57120/… explains how you can recreate it.
– Dave
Feb 27 '18 at 19:00
ibdata1 is the storage space for InnoDB since you erased it the InnoDB engine is not happy and can't start. If you have a copy of it someplace restore it and try to start the server again. If you don't the accepted answer dba.stackexchange.com/questions/57120/… explains how you can recreate it.
– Dave
Feb 27 '18 at 19:00
|
show 2 more comments
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1298762%2fmysql-server-wont-start-on-mamp-for-windows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1298762%2fmysql-server-wont-start-on-mamp-for-windows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What error message do you get when you try to run it?
– Darius
Feb 27 '18 at 9:35
@Darius There is no error message, the loading bar just disappears and the server never starts up.
– Calle
Feb 27 '18 at 9:42
In the directory where the MySQL data is stored look for a file with an extension of .err. The startup problem will likely be detailed in that file.
– Dave
Feb 27 '18 at 13:58
@Dave I have updated my question with the contents of the mysql_error_log.err file. Does it mean anything to you?
– Calle
Feb 27 '18 at 18:54
ibdata1 is the storage space for InnoDB since you erased it the InnoDB engine is not happy and can't start. If you have a copy of it someplace restore it and try to start the server again. If you don't the accepted answer dba.stackexchange.com/questions/57120/… explains how you can recreate it.
– Dave
Feb 27 '18 at 19:00