【发布时间】：2018-05-03 07:08:50
【问题描述】：
Mysqld.exe 已停止在 xampp 窗口中工作。 我在 XAMPP 软件在后台运行时启动了我的计算机，MySQL 无法启动！
2017-11-20 11:05:36 14f4 InnoDB：警告：使用 innodb_additional_mem_pool_size 已弃用。这个选项可能是 在未来的版本中删除，连同选项 innodb_use_sys_malloc 和 InnoDB 的内部内存分配器。 2017-11-20 11:05:36 5364 [注意] InnoDB：innodb_empty_free_list_algorithm 已更改为 legacy，因为 小缓冲池大小。为了使用退避，增加缓冲池 至少高达 20MB。
2017-11-20 11:05:36 5364 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2017-11-20 11:05:36 5364 [Note] InnoDB: The InnoDB memory heap is disabled 2017-11-20 11:05:36 5364 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2017-11-20 11:05:36 5364 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier 2017-11-20 11:05:36 5364 [Note] InnoDB: Compressed tables use zlib 1.2.3 2017-11-20 11:05:36 5364 [Note] InnoDB: Using generic crc32 instructions 2017-11-20 11:05:36 5364 [Note] InnoDB: Initializing buffer pool, size = 16.0M 2017-11-20 11:05:36 5364 [Note] InnoDB: Completed initialization of buffer pool 2017-11-20 11:05:37 5364 [Note] InnoDB: Highest supported file format is Barracuda. 2017-11-20 11:05:37 5364 [Note] InnoDB: The log sequence number 1835037 in ibdata file do not match the log sequence numberib_logfiles 中的 11035100176！ 2017-11-20 11:05:37 14f4 InnoDB：文件操作中的操作系统错误号 38。 InnoDB：一些操作系统错误号在 InnoDB：http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html InnoDB：操作读取文件 D:\win32-packages\build\src\storage\xtradb\os\os0file.cc 并在行 3174 2017-11-20 11:05:37 5364 [错误] InnoDB：文件（未知）：“读取”返回操作系统错误 238。无法继续操作 171120 11:05:37 [错误] mysqld 出现异常 0x80000003 ； 这可能是因为您遇到了错误。这个二进制文件也有可能 或者它所链接的库之一已损坏，构建不当， 或配置错误。此错误也可能是由硬件故障引起的。
To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.1.25-MariaDB key_buffer_size=16777216 read_buffer_size=262144 max_used_connections=0 max_threads=1001 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787107 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... mysqld.exe!my_parameter_handler() mysqld.exe!strxnmov() mysqld.exe!?element_index@Item@@UAEPAV1@I@Z() mysqld.exe!?element_index@Item@@UAEPAV1@I@Z() mysqld.exe!?element_index@Item@@UAEPAV1@I@Z() mysqld.exe!?element_index@Item@@UAEPAV1@I@Z() mysqld.exe!?element_index@Item@@UAEPAV1@I@Z() mysqld.exe!?element_index@Item@@UAEPAV1@I@Z() mysqld.exe!?element_index@Item@@UAEPAV1@I@Z() mysqld.exe!?element_index@Item@@UAEPAV1@I@Z() mysqld.exe!?element_index@Item@@UAEPAV1@I@Z() mysqld.exe!?fix_length_and_dec@subselect_partial_match_engine@@UAEXPAPAVItem_cache@@@Z() mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z() mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z() mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z() mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z() mysqld.exe!?win_main@@YAHHPAPAD@Z() mysqld.exe!?mysql_service@@YAHPAX@Z() mysqld.exe!strxnmov() kernel32.dll!BaseThreadInitThunk() ntdll.dll!RtlInitializeExceptionChain() ntdll.dll!RtlInitializeExceptionChain() The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash.
【问题讨论】：