启动并停止本地计算机上的MySQL57服务 [英] MySQL57 service on Local Computer started and then stopped
问题描述
我的mySql有问题.它停止了,当我尝试启动它时,得到以下信息:本地计算机上的MySQL57服务已启动,然后停止了."如您在下图中所看到的: 我的服务器日志如下:
I'm having a problem with mySql. It is stopped and when I try to start it, I get the following: "MySQL57 service on Local Computer started and then stopped." as you can see in the following image: My server log is the following:
2017-04-05T10:04:58.085384Z 0 [警告]不建议使用具有隐式DEFAULT值的TIMESTAMP.请使用--explicit_defaults_for_timestamp
服务器选项(有关更多详细信息,请参阅文档).
2017-04-05T10:04:58.085384Z 0 [警告]'NO_ZERO_DATE','NO_ZERO_IN_DATE'和'ERROR_FOR_DIVISION_BY_ZERO'sql模式应与严格模式一起使用.在将来的版本中,它们将与严格模式合并.
2017-04-05T10:04:58.087363Z 0 [注意] C:\ Program Files \ MySQL \ MySQL Server 5.7 \ bin \ mysqld.exe(mysqld 5.7.9-log)作为进程7852启动...
2017-04-05T10:04:58.108397Z 0 [注意] InnoDB:互斥锁和rw_locks使用Windows互锁函数
2017-04-05T10:04:58.109398Z 0 [Note] InnoDB:使用事件互斥量
2017-04-05T10:04:58.109398Z 0 [注意] InnoDB:_mm_lfence()和_mm_sfence()用于内存屏障
2017-04-05T10:04:58.110399Z 0 [Note] InnoDB:压缩表使用zlib 1.2.3
2017-04-05T10:04:58.110399Z 0 [Note] InnoDB:由于innodb_buffer_pool_size小于1024 MiB,因此将innodb_buffer_pool_instances从8调整为1
2017-04-05T10:04:58.116403Z 0 [Note] InnoDB:池数:1
2017-04-05T10:04:58.116403Z 0 [Note] InnoDB:不使用CPU crc32指令
2017-04-05T10:04:58.156434Z 0 [注意] InnoDB:正在初始化缓冲池,总大小= 8M,实例= 1,块大小= 8M
2017-04-05T10:04:58.158435Z 0 [注意] InnoDB:缓冲池的完成初始化
2017-04-05T10:04:58.200443Z 0 [注意] InnoDB:支持的最高文件格式是梭子鱼.
2017-04-05T10:04:58.207479Z 0 [注意] InnoDB:日志扫描已通过检查点lsn 43061044961
2017-04-05T10:04:58.208477Z 0 [注意] InnoDB:正在执行恢复:扫描到日志序列号43061045173
2017-04-05T10:04:58.209476Z 0 [错误] InnoDB:由于在检查点43061044961和末端43061045173之间缺少MLOG_CHECKPOINT而忽略重做日志.
2017-04-05T10:04:58.210477Z 0 [错误] InnoDB:插件初始化因错误而中止通用错误
2017-04-05T10:04:58.514809Z 0 [错误]插件'InnoDB'初始化函数返回错误.
2017-04-05T10:04:58.515786Z 0 [错误]插件'InnoDB'注册为存储引擎失败.
2017-04-05T10:04:58.515786Z 0 [错误]无法初始化插件.
2017-04-05T10:04:58.516785Z 0 [错误]正在中止
2017-04-05T10:04:58.085384Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp
server option (see documentation for more details).
2017-04-05T10:04:58.085384Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2017-04-05T10:04:58.087363Z 0 [Note] C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe (mysqld 5.7.9-log) starting as process 7852 ...
2017-04-05T10:04:58.108397Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-04-05T10:04:58.109398Z 0 [Note] InnoDB: Uses event mutexes
2017-04-05T10:04:58.109398Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-04-05T10:04:58.110399Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-04-05T10:04:58.110399Z 0 [Note] InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB
2017-04-05T10:04:58.116403Z 0 [Note] InnoDB: Number of pools: 1
2017-04-05T10:04:58.116403Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2017-04-05T10:04:58.156434Z 0 [Note] InnoDB: Initializing buffer pool, total size = 8M, instances = 1, chunk size = 8M
2017-04-05T10:04:58.158435Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-04-05T10:04:58.200443Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-04-05T10:04:58.207479Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 43061044961
2017-04-05T10:04:58.208477Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43061045173
2017-04-05T10:04:58.209476Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 43061044961 and the end 43061045173.
2017-04-05T10:04:58.210477Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2017-04-05T10:04:58.514809Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-04-05T10:04:58.515786Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-04-05T10:04:58.515786Z 0 [ERROR] Failed to initialize plugins.
2017-04-05T10:04:58.516785Z 0 [ERROR] Aborting
2017-04-05T10:04:58.517786Z 0 [注意] Binlog结束 2017-04-05T10:04:58.517786Z 0 [注意]正在关闭插件"CSV" 2017-04-05T10:04:58.519788Z 0 [Note] C:\ Program Files \ MySQL \ MySQL Server 5.7 \ bin \ mysqld.exe:关闭完成
2017-04-05T10:04:58.517786Z 0 [Note] Binlog end 2017-04-05T10:04:58.517786Z 0 [Note] Shutting down plugin 'CSV' 2017-04-05T10:04:58.519788Z 0 [Note] C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe: Shutdown complete
我已经尝试过,某些选项如通过命令行关闭innodb_log_checksums或设置innodb_log_checksums =配置文件中为0.然后重新启动,或 stackoverflow ,但仍处于停止状态. 我能做些什么?有人可以帮我吗?
I have tried, some options like turn off innodb_log_checksums via command line or set innodb_log_checksums = 0 in configure file. and then restart, or this one in stackoverflow but It is still stopped. What can I do? Can some one help me?
谢谢
推荐答案
从命令提示符处运行命令;这是查看服务返回的错误消息的唯一有效方法,使用内置Windows Services程序将看不到该消息.
Run the command from the command prompt; it's the only effective way to see the error message that services return that you will not see using the built-in Windows Services program.
- 双击服务或右键单击以单击属性.
- 点击可执行文件路径.
- 按Home键,然后在按住End键的同时按住Shift键以突出显示整个命令.
- 按住Control键,然后按C键进行复制.
- 运行命令提示符(通常是开始"->运行"->"cmd"->好")或创建新的快捷方式,然后键入
cmd
作为命令. - 在命令提示符中单击鼠标右键.
- 左键单击粘贴.
- 按Enter键运行命令.
- 使用您首选的搜索引擎研究问题,如果有太多不相关的结果,请在错误消息周围使用引号运算符"来限制结果.
- Either double-click the service or right-click to click on Properties.
- Click on the Path to executable.
- Press the Home key and then hold Shift while pressing the End key to highlight the entire command.
- Hold the Control key and then press C to copy.
- Run the command prompt (usually Start -> Run -> cmd -> Okay) or make a new shortcut and just type
cmd
for the command. - In the commend prompt right-click.
- Left-click on paste.
- Press Enter to run the command.
- Research the problem with your preferred search engine, use "quote operators" around the error message to limit results if there are too many unrelated results.
这篇关于启动并停止本地计算机上的MySQL57服务的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!