Phpmyadmin 无法在xampp中启动mysql
Xampp mysql phpmyadmin几天前运行得很好。现在我遇到了这个问题 我尝试更改端口号，但仍然遇到此问题 windows错误提示告诉我： mysqld.exe已停止处理以下问题详细信息：Phpmyadmin 无法在xampp中启动mysql,phpmyadmin,xampp,mysql,Phpmyadmin,Xampp,Mysql,Xampp mysql phpmyadmin几天前运行得很好。现在我遇到了这个问题 我尝试更改端口号，但仍然遇到此问题 windows错误提示告诉我： mysqld.exe已停止处理以下问题详细信息： Problem signature: Problem Event Name: APPCRASH Application Name: mysqld.exe Application Version: 5.6.16.0 Application Timestamp: 52d55
Problem signature:
Problem Event Name: APPCRASH
Application Name: mysqld.exe
Application Version: 5.6.16.0
Application Timestamp: 52d55dcc
Fault Module Name: mysqld.exe
Fault Module Version: 5.6.16.0
Fault Module Timestamp: 52d55dcc
Exception Code: c0000005
Exception Offset: 00b5957a
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
10:47:55 AM [main] Control Panel Ready
10:47:56 AM [mysql] Attempting to start MySQL app...
10:47:56 AM [mysql] Status change detected: running
10:47:59 AM [mysql] Status change detected: stopped
10:47:59 AM [mysql] Error: MySQL shutdown unexpectedly.
10:47:59 AM [mysql] This may be due to a blocked port, missing dependencies,
10:47:59 AM [mysql] improper privileges, a crash, or a shutdown by another method.
10:47:59 AM [mysql] Press the Logs button to view error logs and check
10:47:59 AM [mysql] the Windows Event Viewer for more clues
10:47:59 AM [mysql] If you need more help, copy and post this
10:47:59 AM [mysql] entire log window on the forums
2014-08-27 09:12:23 3296 [Note] Plugin 'FEDERATED' is disabled.
2014-08-27 09:12:23 ce4 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.
2014-08-27 09:12:23 3296 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-08-27 09:12:23 3296 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-27 09:12:23 3296 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-27 09:12:23 3296 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-27 09:12:23 3296 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-27 09:12:23 3296 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-08-27 09:12:23 3296 [Note] InnoDB: Completed initialization of buffer pool
2014-08-27 09:12:23 3296 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-27 09:12:23 3296 [Note] InnoDB: The log sequence numbers 1625987 and 1625987 in ibdata files do not match the log sequence number 3459249 in the ib_logfiles!
2014-08-27 09:12:23 3296 [Note] InnoDB: Database was not shutdown normally!
2014-08-27 09:12:23 3296 [Note] InnoDB: Starting crash recovery.
2014-08-27 09:12:23 3296 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-27 09:12:23 3296 [Note] InnoDB: Restoring possible half-written data pages
2014-08-27 09:12:23 3296 [Note] InnoDB: from the doublewrite buffer...
2014-08-27 09:12:25 3296 [Note] InnoDB: 128 rollback segment(s) are active.
2014-08-27 09:12:25 3296 [Note] InnoDB: Waiting for purge to start
2014-08-27 09:12:25 3296 [Note] InnoDB: 5.6.16 started; log sequence number 3459249
2014-08-27 09:12:25 3296 [Note] Server hostname (bind-address): '*'; port: 3306
2014-08-27 09:12:25 3296 [Note] IPv6 is available.
2014-08-27 09:12:25 3296 [Note] - '::' resolves to '::';
2014-08-27 09:12:25 3296 [Note] Server socket created on IP: '::'.
2014-08-27 09:12:26 3296 [Note] Event Scheduler: Loaded 0 events
2014-08-27 09:12:26 3296 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)
谢谢您的帮助。您自己的链接，以便页面有答案。从错误日志中： 2014-08-27 09:12:23 3296[注]InnoDB:ibdata文件中的日志序列号1625987和1625987与ibu日志文件中的日志序列号3459249不匹配 然后，从世界上评分最高的答案
- 退出Xampp服务器
- 转到您的C:\xampp\mysql\data目录
- 删除ibdata1文件
- 重新启动xampp服务器
如果我的错误没有在mysql中运行，那么尝试一下，你会发现它已经过时了。 InnoDB:警告：不推荐使用InnoDB_附加_mem_pool_大小。该选项可能会在将来的版本中与innodb_use_sys_malloc选项以及innodb的内部内存分配器一起删除。 2015-11-10 15:26:56 4348[注]InnoDB：使用互斥体引用缓冲池页面计数
解决方案：删除ibdata1，all（ib_日志文件）。。。然后重新启动xampp，我也遇到了同样的问题。不幸的是，上述解决方案对我并不适用。 我已经通过删除ib_logfile0，ib_logfile1解决了这个问题。。。所有日志文件和我的xampp现在工作正常！ 根据上述解决方案，如果我删除ibdata1文件，那么我的所有数据库都会丢失。 因此，我保留了ibdata1文件并删除了所有日志文件
多亏了stackoverflow.com我已经删除了ibdata1文件。仍然遇到相同的错误：（然后我会尝试关闭mysql，在mysql配置的[mysqld]部分中添加
innodb\u force\u recovery=1