![无法启动服务 MySQL。错误:0 如何让 mysql 5.5 服务器运行?](https://linux22.com/image/566734/%E6%97%A0%E6%B3%95%E5%90%AF%E5%8A%A8%E6%9C%8D%E5%8A%A1%20MySQL%E3%80%82%E9%94%99%E8%AF%AF%EF%BC%9A0%20%E5%A6%82%E4%BD%95%E8%AE%A9%20mysql%205.5%20%E6%9C%8D%E5%8A%A1%E5%99%A8%E8%BF%90%E8%A1%8C%EF%BC%9F.png)
我尝试从 MySQL 5.1 升级到 MySQL 5.5。当我尝试运行实例配置向导时,出现以下错误:
Could not start the service MySQL. Error:0
现在我非常高兴能够全新安装 MySQL 5.5。之后我可以重新填充数据库。
我尝试过的事情:
- 重新启动机器并再次尝试实例配置
- 卸载所有 MySQL 软件,并确保没有服务并重新安装
- 搜索注册表以确保没有 MySQL 条目。
- 我尝试检查 .err 日志,但是没有发现任何内容。
- 在网上搜索是否有人遇到同样的问题。有几个人遇到了,但没有简单的解决办法。
- 已关注这指导一步一步,但仍然没有成功
我所掌握的信息:
操作系统:WINDOWS XP Service Pack 3
在cmd中运行后mysqld -nt --defaults-file="C:\Program Files\MySQL\MySQL Server 5.5\my.ini"
输出:
--standalone --console >>output.txt
111109 10:09:33 [Warning] option 'new': boolean value 't' wasn't recognized. Set
to OFF.
111109 10:09:33 [Note] Plugin 'FEDERATED' is disabled.
111109 10:09:33 InnoDB: The InnoDB memory heap is disabled
111109 10:09:33 InnoDB: Mutexes and rw_locks use Windows interlocked functions
111109 10:09:33 InnoDB: Compressed tables use zlib 1.2.3
111109 10:09:33 InnoDB: Initializing buffer pool, size = 47.0M
111109 10:09:33 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file .\ib_logfile0 is of different size 0 104857600 bytes
InnoDB: than specified in the .cnf file 0 25165824 bytes!
111109 10:09:33 [ERROR] Plugin 'InnoDB' init function returned error.
111109 10:09:33 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
111109 10:09:33 [ERROR] mysqld: unknown variable 'defaults-file=C:\Program Files
\MySQL\MySQL Server 5.5\my.ini'
111109 10:09:33 [ERROR] Aborting
111109 10:09:33 [Note] mysqld: Shutdown complete
my.ini 中的内容如下:
# MySQL Server Instance Configuration File
# ----------------------------------------------------------------------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ----------------------------------------------------------------------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory
# of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
# make sure the server reads the config file use the startup option
# "--defaults-file".
#
# To run run the server from the command line, execute this in a
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# To install the server as a Windows service manually, execute this in a
# command line shell, e.g.
# mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# And then execute this in a command line shell to start the server, e.g.
# net start MySQLXY
#
#
# Guildlines for editing this file
# ----------------------------------------------------------------------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
#
# CLIENT SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]
port=3306
[mysql]
default-character-set=latin1
# SERVER SECTION
# ----------------------------------------------------------------------
#
# 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.
#
[mysqld]
# The TCP/IP Port the MySQL Server will listen on
port=3306
#Path to installation directory. All paths are usually resolved relative to this.
basedir="C:/Program Files/MySQL/MySQL Server 5.5/"
#Path to the database root
datadir="C:/Documents and Settings/All Users/Application Data/MySQL/MySQL Server 5.5/Data/"
# The default character set that will be used when a new schema or table is
# created and no character set is defined
character-set-server=latin1
# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB
# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
# 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.
max_connections=100
# 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.
query_cache_size=0
# 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]
table_cache=256
# 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.
tmp_table_size=17M
# 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.)
thread_cache_size=8
#*** 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).
myisam_max_sort_file_size=100G
# 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.
myisam_sort_buffer_size=34M
# 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.
key_buffer_size=25M
# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K
# 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.
sort_buffer_size=256K
#*** 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.
#skip-innodb
# 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.
innodb_additional_mem_pool_size=2M
# 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.
innodb_flush_log_at_trx_commit=1
# 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_log_buffer_size=1M
# 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.
innodb_buffer_pool_size=47M
# 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.
innodb_log_file_size=24M
# 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_thread_concurrency=8
自发布以来我尝试过的事情:
- 尝试删除 ib_logfile0 和 ib_logfile1,但它们不存在
- 运行了“mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server 5.5\my.ini" --nt”,但
mysqld -nt --defaults-file="C:\Program Files\MySQL\MySQL Server 5.5\my.ini
屏幕上没有输出任何内容,我仍然无法运行服务
答案1
我在现实生活中帮助理查德解决了这个问题——问题原来出在应用程序数据下的 MySQL 目录。
在这种情况下:C:\Documents and Settings\All Users\Application Data\MySQL(对于那些不确定我在说什么的人来说,在 Vista/7 下等效路径会有所不同)
解决方案是删除实例,卸载 MySQL,删除应用程序数据下的 MySQL 目录,然后重新安装,如 Eric Eskildsen 和 Matthew Sadowski 在此线程底部所述。
http://bugs.mysql.com/bug.php?id=48871
值得注意的是,有一个MySQL 服务器 5.1MySQL 文件夹下的目录,无论是读取那目录而不是 5.5,或者 5.5 目录中的文件是否已损坏...我不知道,但在这种情况下,它们中的一个或两个都是罪魁祸首。
毫无疑问,这是我安装 MySQL 时遇到的最奇怪的问题之一 :-S
答案2
尝试运行:
mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server 5.5\my.ini" --nt
它会起作用。问题是默认文件参数应该是第一个。正如这里提到的: http://dev.mysql.com/doc/refman/5.0/en/mysqld-safe.html
编辑: 命令中也缺少引号。