Question

我正在尝试在计算机上运行Wamp。 Wamp正在努力，直到我今天尝试使用它。我已经更改了MySQL的ini文件，但是当它停止工作时，我恢复了更改。它仍然无法正常工作。 Apache正在运行，因为我可以启动和停止该服务，并且图标会相应地更改颜色。这是我的意思的图像：

这是我的mysql .ini文件：

 # Example MySQL config file for medium systems.
 #
 # This is for a large system with memory of 1G-2G where the system runs mainly
# MySQL.
#
# MySQL programs look for option files in a set of
# locations which depend on the deployment platform.
# You can copy this option file to one of those
# locations. For information about these locations, see:
# http://dev.mysql.com/doc/mysql/en/option-files.html
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
#password = your_password
port = 3306
socket = /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[wampmysqld64]
#skip-grant-tables
port = 3306
socket = /tmp/mysql.sock
key_buffer_size = 64M
max_allowed_packet = 1M

#Added to reduce memory used (minimum is 400)
table_definition_cache = 600

sort_buffer_size = 2M
net_buffer_length = 8K
read_buffer_size = 2M
read_rnd_buffer_size = 2M
myisam_sort_buffer_size = 32M
#Path to mysql install directory
basedir="C:/wamp64/bin/mysql/mysql5.7.9"
log-error="C:/wamp64/logs/mysql.log"
#Verbosity Value  1 Errors only, 2  Errors and warnings , 3 Errors, warnings, and notes
log_error_verbosity=2
#Path to data directory
datadir="C:/wamp64/bin/mysql/mysql5.7.9/data"

#Path to the language
#See Documentation:
# http://dev.mysql.com/doc/refman/5.7/en/error-message-language.html
lc-messages-dir="C:/wamp64/bin/mysql/mysql5.7.9/share"
lc-messages=en_US

# The default storage engine that will be used when create new tables
default-storage-engine=InnoDB
# New for MySQL 5.6 default_tmp_storage_engine if skip-innodb enable
# default_tmp_storage_engine=InnoDB

#To avoid warning messages
secure_file_priv="C:/wamp64/tmp"
skip-ssl

explicit_defaults_for_timestamp=true

# Set the SQL mode to strict
#sql-mode=""
sql-mode="STRICT_ALL_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_ZERO_DATE,NO_ZERO_IN_DATE,NO_AUTO_CREATE_USER"

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking

# Disable Federated by default
skip-federated

# Replication Master Server (default)
# binary logging is required for replication
#log-bin=mysql-bin

# binary logging format - mixed recommended
#binlog_format=mixed

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1

# Replication Slave (comment out master section to use this)

# New for MySQL 5.6 if no slave
skip-slave-start

#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin

# Point the following paths to different dedicated disks
#tmpdir   = /tmp/
#log-update   = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using InnoDB tables
# Chemins de mes bases de donn�es qui sont d�plac�es
#innodb_data_home_dir = C:/mysql/data/
innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = C:/mysql/data/
#innodb_log_arch_dir = C:/mysql/data/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 16M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer_size = 2M
write_buffer_size = 2M

[myisamchk]
key_buffer_size = 20M
sort_buffer_size_size = 20M
read_buffer_size = 2M
write_buffer_size = 2M

[mysqlhotcopy]
interactive-timeout

[mysqld]
port = 3306

这是我的MySQL日志文件信息：

2016-05-31T14:32:28.277983Z 0 [Warning] InnoDB: Resizing redo log from 2*3072 to 2*320 pages, LSN=2472423
2016-05-31T14:32:28.480508Z 0 [Warning] InnoDB: Starting to delete and rewrite log files.
2016-05-31T14:32:28.984623Z 0 [Warning] InnoDB: New log files created, LSN=2472423
2016-06-14T19:25:07.247490Z 0 [Warning] wampmysqld64: Forcing close of thread 482  user: 'root'

2017-07-14T01:50:50.741198Z 0 [Warning] wampmysqld64: Forcing close of thread 30  user: 'root'

2017-07-14T01:50:50.761198Z 0 [Warning] wampmysqld64: Forcing close of thread 27  user: 'root'

2017-07-14T01:50:50.766200Z 0 [Warning] wampmysqld64: Forcing close of thread 26  user: 'root'

2017-07-14T01:50:50.772199Z 0 [Warning] wampmysqld64: Forcing close of thread 29  user: 'root'

2017-07-15T06:59:13.799344Z 0 [Warning] wampmysqld64: Forcing close of thread 11  user: 'root'

2017-07-15T06:59:13.846464Z 0 [Warning] wampmysqld64: Forcing close of thread 12  user: 'root'

2017-07-27T01:17:26.477513Z 0 [Warning] wampmysqld64: Forcing close of thread 688  user: 'root'

2017-07-27T01:17:26.517496Z 0 [Warning] wampmysqld64: Forcing close of thread 689  user: 'root'

2017-08-05T19:22:30.560951Z 0 [Warning] wampmysqld64: Forcing close of thread 305  user: 'root'

2017-08-05T19:22:30.631940Z 0 [Warning] wampmysqld64: Forcing close of thread 304  user: 'root'

2017-08-07T06:37:28.699452Z 0 [Warning] wampmysqld64: Forcing close of thread 12  user: 'root'

2017-08-07T06:37:28.701453Z 0 [Warning] wampmysqld64: Forcing close of thread 13  user: 'root'

2017-08-26T00:24:35.765816Z 0 [Warning] wampmysqld64: Forcing close of thread 24  user: 'root'

2017-08-26T00:24:35.802819Z 0 [Warning] wampmysqld64: Forcing close of thread 23  user: 'root'

以下是服务的状态：

State of services:

 The service 'wampapache64' is started

 The service 'wampmysqld64' is NOT started
 EXIT error code:0
 Help message for error code 0 is:
The operation completed successfully.



 The service 'dnscache' is started

WampServer (Apache, PHP and MySQL) will not function properly if any service
'wampapache64'
'wampmysqld64'
'dnscache'
 is not started.

感谢您的帮助！

更新

在服务中，mysqld.exe一直在运行，wampmysql64始终在启动..当我杀死mysqld.exe时，我可以选择启动MySQL服务。当我启动服务时，会发生同样的错误。

以下是我点击停止或重新启动服务时出现错误的照片：

Answer 1

你应该看一下这篇文章：Wampserver icon not going green fully, mysql services not starting up?

引用作者：

打开wampserver的mysql日志文件。这将包含有关服务投掷和错误的原因以及过早退出的信息。



在我的情况下，mysql服务无法启动，因为它无法读取某个表空间。特定的表空间在日志中显示。


无法读取此类文件可能是因为文件权限或文件被破坏。在这种情况下，mysql会停止执行，以避免损坏可能链接到您需要的数据库的表空间文件。通常，如果您有数据库的备份，那么只需删除这个有问题的文件并在您的mysql服务再次启动后恢复数据库是安全的。

如果您没有数据库备份，则可以通过在my.cnf / my.ini文件中启用该选项来强制mysql实例运行恢复。

innodb_force_recovery = 1

这会强制实例运行崩溃恢复。

注意：安装新的mysql实例并不一定意味着您的数据库应该被保留。如果您正在开展大型项目，我建议您对数据库进行夜间备份。

Answer 2

修复

我在新文件夹中下载了当前版本的wamp。然后我从bin中复制了MySQL文件夹。我添加了我的数据库并修改了my.ini和wampserver.conf文件，使它们指向正确的目录。这解决了我的问题。我希望这有助于其他人！

Wamp显示橙色图标 - Apache正在运行，MySQL无法启动

更新

2 个答案:

修复