我需要在xampp 3.2.1中对MySql提供一些帮助。 MySql服务无法启动,我找不到原因,因为错误日志文件报告它无法从“未知文件”读取并且仅返回错误0。 我不知道这意味着什么,因为它基本上说它在尝试读取未知文件时有0错误。 这是错误日志:
2015-01-20 10:36:12 760 [Note] Plugin 'FEDERATED' is disabled.
2015-01-20 10:36:12 574 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-01-20 10:36:12 760 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-01-20 10:36:12 760 [Note] InnoDB: The InnoDB memory heap is disabled
2015-01-20 10:36:12 760 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-01-20 10:36:12 760 [Note] InnoDB: Memory barrier is not used
2015-01-20 10:36:12 760 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-01-20 10:36:12 760 [Note] InnoDB: Not using CPU crc32 instructions
2015-01-20 10:36:12 760 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-01-20 10:36:12 760 [Note] InnoDB: Completed initialization of buffer pool
2015-01-20 10:36:12 760 [Note] InnoDB: Highest supported file format is Barracuda.
2015-01-20 10:36:12 760 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 131153885 in the ib_logfiles!
2015-01-20 10:36:12 760 [Note] InnoDB: Database was not shutdown normally!
2015-01-20 10:36:12 760 [Note] InnoDB: Starting crash recovery.
2015-01-20 10:36:12 760 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-01-20 10:36:12 760 [ERROR] InnoDB: File (unknown): 'read' returned OS error 0. Cannot continue operation
请帮助。
答案 0 :(得分:9)
这是针对不同的错误代码,但看看它是否有效。
通过“Config”打开MySQL配置文件 - > “的my.ini”。
插入
innodb_flush_method = normal
之间
innodb_lock_wait_timeout = 50
和## UTF 8 Settings
在xampp中再次启动MySQL。
https://community.apachefriends.org/f/viewtopic.php?f=16&t=72437
答案 1 :(得分:-1)
我遇到了完全相同的问题 - 运行相同版本的XAMPP,它刚刚开始与您的问题同时发生。
试试这个。打开XAMPP目录并转到XAMPP / mysql / Data
剪切所有文件(ibdata *,auto.cnf,mysql.pid)并将它们放在其他地方。
尝试启动Mysql - 如果效果很好,如果没有,你可能需要做的是,在你的日志中查找DB给你一个问题 - 并移动相应的文件夹。
幸运的是,这将解决你的问题 - 这对我有用!