180913 16:41:31 [Note] Plugin ‘FEDERATED’ is disabled.
180913 16:41:31 InnoDB: The InnoDB memory heap is disabled
180913 16:41:31 InnoDB: Mutexes and rw_locks use Windows interlocked functions
180913 16:41:31 InnoDB: Compressed tables use zlib 1.2.3
180913 16:41:31 InnoDB: Initializing buffer pool, size = 47.0M
180913 16:41:31 InnoDB: Completed initialization of buffer pool
InnoDB: Error: space header page consists of zero bytes in data file .\ibdata1
180913 16:41:31 InnoDB: Could not open or create data files.
180913 16:41:31 InnoDB: If you tried to add new data files, and it failed here,
180913 16:41:31 InnoDB: you should now edit innodb_data_file_path in my.cnf back
180913 16:41:31 InnoDB: to what it was, and remove the new ibdata files InnoDB created
180913 16:41:31 InnoDB: in this failed attempt. InnoDB only wrote those files full of
180913 16:41:31 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
180913 16:41:31 InnoDB: remove old data files which contain your precious data!
180913 16:41:31 [ERROR] Plugin ‘InnoDB’ init function returned error.
180913 16:41:31 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
180913 16:41:31 [ERROR] Unknown/unsupported storage engine: INNODB
180913 16:41:31 [ERROR] Aborting然后,我们看到了为什么出启动不了服务:
The InnoDB memory heap is disabled
InnoDB: Error: space header page consists of zero bytes in data file .\ibdata1
Could not open or create data files.



# ———————————————————————-
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
# The TCP/IP Port the MySQL Server will listen on

#Path to installation directory. All paths are usually resolved relative to this.

#Path to the database root,数据库文件保存的路劲,日志也会保存在这里

# The default character set that will be used when a new schema or table is
# created and no character set is defined

# The default storage engine that will be used when create new tables when

# Set the SQL mode to strict

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.

# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# “Qcache_lowmem_prunes” status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.

# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable “open-files-limit” in
# section [mysqld_safe]

# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.

# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client’s threads are put in the cache if there aren’t
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn’t give a notable performance
# improvement if you have a good thread implementation.)

#*** MyISAM Specific options

# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.

# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you’re not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.

# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.

# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.

#*** INNODB Specific options ***
# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.

# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.

# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.

# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.

# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.

# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.

  • #* INNODB Specific options *****下加入这样的一条语句:
    innodb_data_file_path = ibdata1:1024M;ibdata2:512M:autoextend
  • 加入了这条语句后,将C:\xampp\mysql\data\下的文件全部删除,注意删除的是文件,不是文件夹,文件夹是数据库
  • 然后重启MySQL服务,发现还是报错了,这就是双系统MMP的地方了,我们还需要在my.ini配置文件中加一条语句
  • 然后,重新启动,解决了!

未经允许不得转载:专注は互联网 · 用户 · 产品 - 极简 · 生活 · 禅修 » MAC双系统Win10中安装XAMPP的MySQL无法启动的解决方法

赞 (0)


分享到:更多 ()

留言 0

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址