log显示信息
2023-01-29 21:01:04 ERROR: Could not connect to MySQL database at 127.0.0.1: Can't connect to MySQL server on '127.0.0.1' (10061)
2023-01-29 21:01:04 ERROR: DatabasePool world NOT opened. There were errors opening the MySQL connections. Check your SQLDriverLogFile for specific errors.
2023-01-29 21:01:04 ERROR: Cannot connect to world database 127.0.0.1;3306;root;ascent;world
继续测试结果，会不会是数据库问题呢？
2023-01-30 09:20:16 6208 [Note] Plugin 'FEDERATED' is disabled.
2023-01-30 09:20:16 2648 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.
2023-01-30 09:20:16 6208 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-01-30 09:20:16 6208 [Note] InnoDB: The InnoDB memory heap is disabled
2023-01-30 09:20:16 6208 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-01-30 09:20:16 6208 [Note] InnoDB: Memory barrier is not used
2023-01-30 09:20:16 6208 [Note] InnoDB: Compressed tables use zlib 1.2.3
2023-01-30 09:20:16 6208 [Note] InnoDB: Not using CPU crc32 instructions
2023-01-30 09:20:16 6208 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2023-01-30 09:20:17 6208 [Note] InnoDB: Completed initialization of buffer pool
2023-01-30 09:20:17 6208 [Note] InnoDB: Highest supported file format is Barracuda.
2023-01-30 09:20:17 6208 [Note] InnoDB: The log sequence numbers 251109400 and 251109400 in ibdata files do not match the log sequence number 2207285992 in the ib_logfiles!
2023-01-30 09:20:17 6208 [Note] InnoDB: Database was not shutdown normally!
2023-01-30 09:20:17 6208 [Note] InnoDB: Starting crash recovery.
2023-01-30 09:20:17 6208 [Note] InnoDB: Reading tablespace information from the .ibd files...
2023-01-30 09:20:17 2648 InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http:斜杠dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html[/url]
InnoDB: Error: could not open single-table tablespace file .\.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
楼主: netlinker
[复制链接]
发表于 2023-1-29 18:07:42
楼主
，
