XAMPP 关闭后,MySQL 也停止工作,我该如何解决?

Posted

技术标签:

【中文标题】XAMPP 关闭后,MySQL 也停止工作,我该如何解决?【英文标题】:After an XAMPP shutdown, MySQL stopped working too, how do I solve this? 【发布时间】:2018-10-18 18:46:38 【问题描述】:

我在使用 xampp 运行 mysql 时出错。 这是日志,一旦我启动 xampp,就会出现这个错误我在 xampp 中运行 ips 仅当我删除了 mysql 数据文件夹时,mysql 的端口也不会显示在控制面板中,我的意思是除了我的数据库之外的所有内容。 日志:

2018-05-08 19:14:50 450 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.
2018-05-08 19:14:50 1104 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-05-08 19:14:50 1104 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-05-08 19:14:50 1104 [Note] InnoDB: The InnoDB memory heap is disabled
2018-05-08 19:14:50 1104 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-05-08 19:14:50 1104 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-05-08 19:14:50 1104 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-05-08 19:14:50 1104 [Note] InnoDB: Using generic crc32 instructions
2018-05-08 19:14:50 1104 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-05-08 19:14:50 1104 [Note] InnoDB: Completed initialization of buffer pool
2018-05-08 19:14:50 1104 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2018-05-08 19:14:50 1104 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2018-05-08 19:14:50 1104 [Note] InnoDB: Database physically writes the file full: wait...
2018-05-08 19:14:51 1104 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2018-05-08 19:14:51 1104 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2018-05-08 19:14:51 1104 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2018-05-08 19:14:51 1104 [Warning] InnoDB: New log files created, LSN=45883
2018-05-08 19:14:51 1104 [Note] InnoDB: Doublewrite buffer not found: creating new
2018-05-08 19:14:52 1104 [Note] InnoDB: Doublewrite buffer created
2018-05-08 19:14:53 1104 [Note] InnoDB: 128 rollback segment(s) are active.
2018-05-08 19:14:53 1104 [Warning] InnoDB: Creating foreign key constraint system tables.
2018-05-08 19:14:53 1104 [Note] InnoDB: Foreign key constraint system tables created
2018-05-08 19:14:53 1104 [Note] InnoDB: Creating tablespace and datafile system tables.
2018-05-08 19:14:53 1104 [Note] InnoDB: Tablespace and datafile system tables created.
2018-05-08 19:14:53 1104 [Note] InnoDB: Waiting for purge to start
2018-05-08 19:14:54 1104 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 0
2018-05-08 19:14:54 1944 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-05-08 19:14:54 1104 [Note] Plugin 'FEEDBACK' is disabled.
2018-05-08 19:14:55 1104 [Note] Server socket created on IP: '::'.
2018-05-08 19:14:56 5308 [Warning] InnoDB: Cannot open table mysql/gtid_slave_pos from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2018-05-08 19:14:56 5308 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1932: Table 'mysql.gtid_slave_pos' doesn't exist in engine
2018-05-08 19:14:56 1104 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.21-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
2018-05-08 19:14:57 6036 [Warning] InnoDB: Cannot open table ips/core_cache from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2018-05-08 19:14:57 3784 [Warning] InnoDB: Cannot open table ips/core_cache from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2018-05-08 19:14:57 6036 [Warning] InnoDB: Cannot open table ips/core_sessions from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2018-05-08 19:14:57 3784 [Warning] InnoDB: Cannot open table ips/core_sessions from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2018-05-08 19:14:58 6036 [Warning] InnoDB: Cannot open table ips/core_cache from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2018-05-08 19:14:58 6036 [Warning] InnoDB: Cannot open table ips/core_sessions from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2018-05-08 19:14:59 6036 [Warning] InnoDB: Cannot open table ips/core_cache from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2018-05-08 19:14:59 6036 [Warning] InnoDB: Cannot open table ips/core_sessions from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2018-05-08 19:15:00 3784 [Warning] InnoDB: Cannot open table ips/core_cache from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2018-05-08 19:15:00 3784 [Warning] InnoDB: Cannot open table ips/core_sessions from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.

我正在托管和开发近 6 GB 的网站和论坛。 PS:我无法删除xampp并重新启动整个过程(我的意思是卸载xampp并将htdocs和数据库复制到新文件夹中)

提前致谢。

【问题讨论】:

【参考方案1】:

确切地说,您的帖子没有错误。只是警告和注释。

我的猜测是您的内存和/或硬盘空间不足。

【讨论】:

以上是关于XAMPP 关闭后,MySQL 也停止工作,我该如何解决?的主要内容,如果未能解决你的问题,请参考以下文章

XAMPP - 单击退出时停止服务的方法?

XAMPP - MySQL 意外关闭

XAMPP - MySQL 意外关闭

一旦您启动 phpmyadmin XAMPP,MySQL 就会停止

重启后 XAMPP MySQL 服务崩溃

如果连接关闭,我该如何处理连接并重新连接?