【已解决】服务器重启一下然后mysql数据库重启不了

服务器重启一下然后mysql数据库重启不了，有没有大佬有思路处理啊

您好，您复制下面的命令到终端中执行，该命令是用来查看mysql的error日志信息的，执行后把执行结果截图发出来

1. cat /www/server/data/*.err|grep -i -C 10 error

复制代码

堡塔运维小林 发表于 2023-7-19 21:46
您好，您复制下面的命令到终端中执行，该命令是用来查看mysql的error日志信息的，执行后把执行结果截图发出 ...

命令输入没有反应啊

命令输不了

[root@izm5eb8f6yfdzquzas6bzez ~]# cat /www/server/data/*.err|grep -i -C 10 error
2024-10-08 21:01:53 5835 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-10-08 21:01:53 5835 [Note] InnoDB: Using Linux native AIO
2024-10-08 21:01:53 5835 [Note] InnoDB: Using CPU crc32 instructions
2024-10-08 21:01:53 5835 [Note] InnoDB: Initializing buffer pool, size = 384.0M
2024-10-08 21:01:53 5835 [Note] InnoDB: Completed initialization of buffer pool
2024-10-08 21:01:53 5835 [Note] InnoDB: Highest supported file format is Barracuda.
2024-10-08 21:01:53 5835 [Note] InnoDB: Log scan progressed past the checkpoint lsn 67527865373
2024-10-08 21:01:53 5835 [Note] InnoDB: Database was not shutdown normally!
2024-10-08 21:01:53 5835 [Note] InnoDB: Starting crash recovery.
2024-10-08 21:01:53 5835 [Note] InnoDB: Reading tablespace information from the .ibd files...
2024-10-08 21:01:54 5835 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace www_c0317_com/ims_longbing_card_copy_count uses space ID: 2542 at filepath: ./www_c0317_com/ims_longbing_card_copy_count.ibd. Cannot open tablespace www_c0317/ims_tech_shopm_ptlist which uses space ID: 2542 at filepath: ./www_c0317/ims_tech_shopm_ptlist.ibd
2024-10-08 21:01:54 7f43b87b0880  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./www_c0317/ims_tech_shopm_ptlist.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
--
2024-10-08 21:01:55 6791 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-10-08 21:01:55 6791 [Note] InnoDB: Using Linux native AIO
2024-10-08 21:01:55 6791 [Note] InnoDB: Using CPU crc32 instructions
2024-10-08 21:01:55 6791 [Note] InnoDB: Initializing buffer pool, size = 384.0M
2024-10-08 21:01:55 6791 [Note] InnoDB: Completed initialization of buffer pool
2024-10-08 21:01:55 6791 [Note] InnoDB: Highest supported file format is Barracuda.
2024-10-08 21:01:55 6791 [Note] InnoDB: Log scan progressed past the checkpoint lsn 67527865373
2024-10-08 21:01:55 6791 [Note] InnoDB: Database was not shutdown normally!
2024-10-08 21:01:55 6791 [Note] InnoDB: Starting crash recovery.
2024-10-08 21:01:55 6791 [Note] InnoDB: Reading tablespace information from the .ibd files...
2024-10-08 21:01:56 6791 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace www_c0317_com/ims_longbing_card_copy_count uses space ID: 2542 at filepath: ./www_c0317_com/ims_longbing_card_copy_count.ibd. Cannot open tablespace www_c0317/ims_tech_shopm_ptlist which uses space ID: 2542 at filepath: ./www_c0317/ims_tech_shopm_ptlist.ibd
2024-10-08 21:01:56 7fad07d67880  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./www_c0317/ims_tech_shopm_ptlist.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
--
2024-10-08 21:01:58 7811 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-10-08 21:01:58 7811 [Note] InnoDB: Using Linux native AIO
2024-10-08 21:01:58 7811 [Note] InnoDB: Using CPU crc32 instructions
2024-10-08 21:01:58 7811 [Note] InnoDB: Initializing buffer pool, size = 384.0M
2024-10-08 21:01:58 7811 [Note] InnoDB: Completed initialization of buffer pool
2024-10-08 21:01:58 7811 [Note] InnoDB: Highest supported file format is Barracuda.
2024-10-08 21:01:58 7811 [Note] InnoDB: Log scan progressed past the checkpoint lsn 67527865373
2024-10-08 21:01:58 7811 [Note] InnoDB: Database was not shutdown normally!
2024-10-08 21:01:58 7811 [Note] InnoDB: Starting crash recovery.
2024-10-08 21:01:58 7811 [Note] InnoDB: Reading tablespace information from the .ibd files...
2024-10-08 21:01:58 7811 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace www_c0317_com/ims_longbing_card_copy_count uses space ID: 2542 at filepath: ./www_c0317_com/ims_longbing_card_copy_count.ibd. Cannot open tablespace www_c0317/ims_tech_shopm_ptlist which uses space ID: 2542 at filepath: ./www_c0317/ims_tech_shopm_ptlist.ibd
2024-10-08 21:01:58 7f145d8be880  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./www_c0317/ims_tech_shopm_ptlist.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
--
2024-10-08 21:02:01 8796 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-10-08 21:02:01 8796 [Note] InnoDB: Using Linux native AIO
2024-10-08 21:02:01 8796 [Note] InnoDB: Using CPU crc32 instructions
2024-10-08 21:02:01 8796 [Note] InnoDB: Initializing buffer pool, size = 384.0M
2024-10-08 21:02:01 8796 [Note] InnoDB: Completed initialization of buffer pool
2024-10-08 21:02:01 8796 [Note] InnoDB: Highest supported file format is Barracuda.
2024-10-08 21:02:01 8796 [Note] InnoDB: Log scan progressed past the checkpoint lsn 67527865373
2024-10-08 21:02:01 8796 [Note] InnoDB: Database was not shutdown normally!
2024-10-08 21:02:01 8796 [Note] InnoDB: Starting crash recovery.
2024-10-08 21:02:01 8796 [Note] InnoDB: Reading tablespace information from the .ibd files...
2024-10-08 21:02:01 8796 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace www_c0317_com/ims_longbing_card_copy_count uses space ID: 2542 at filepath: ./www_c0317_com/ims_longbing_card_copy_count.ibd. Cannot open tablespace www_c0317/ims_tech_shopm_ptlist which uses space ID: 2542 at filepath: ./www_c0317/ims_tech_shopm_ptlist.ibd
2024-10-08 21:02:01 7f5ee5ec6880  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./www_c0317/ims_tech_shopm_ptlist.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
--
2024-10-08 21:02:03 9785 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-10-08 21:02:03 9785 [Note] InnoDB: Using Linux native AIO
2024-10-08 21:02:03 9785 [Note] InnoDB: Using CPU crc32 instructions
2024-10-08 21:02:03 9785 [Note] InnoDB: Initializing buffer pool, size = 384.0M
2024-10-08 21:02:03 9785 [Note] InnoDB: Completed initialization of buffer pool
2024-10-08 21:02:03 9785 [Note] InnoDB: Highest supported file format is Barracuda.
2024-10-08 21:02:03 9785 [Note] InnoDB: Log scan progressed past the checkpoint lsn 67527865373
2024-10-08 21:02:03 9785 [Note] InnoDB: Database was not shutdown normally!
2024-10-08 21:02:03 9785 [Note] InnoDB: Starting crash recovery.
2024-10-08 21:02:03 9785 [Note] InnoDB: Reading tablespace information from the .ibd files...
2024-10-08 21:02:04 9785 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace www_c0317_com/ims_longbing_card_copy_count uses space ID: 2542 at filepath: ./www_c0317_com/ims_longbing_card_copy_count.ibd. Cannot open tablespace www_c0317/ims_tech_shopm_ptlist which uses space ID: 2542 at filepath: ./www_c0317/ims_tech_shopm_ptlist.ibd
2024-10-08 21:02:04 7f00efd78880  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./www_c0317/ims_tech_shopm_ptlist.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
--
2024-10-08 21:02:06 10791 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-10-08 21:02:06 10791 [Note] InnoDB: Using Linux native AIO
2024-10-08 21:02:06 10791 [Note] InnoDB: Using CPU crc32 instructions
2024-10-08 21:02:06 10791 [Note] InnoDB: Initializing buffer pool, size = 384.0M
2024-10-08 21:02:06 10791 [Note] InnoDB: Completed initialization of buffer pool
2024-10-08 21:02:06 10791 [Note] InnoDB: Highest supported file format is Barracuda.
2024-10-08 21:02:06 10791 [Note] InnoDB: Log scan progressed past the checkpoint lsn 67527865373
2024-10-08 21:02:06 10791 [Note] InnoDB: Database was not shutdown normally!
2024-10-08 21:02:06 10791 [Note] InnoDB: Starting crash recovery.
2024-10-08 21:02:06 10791 [Note] InnoDB: Reading tablespace information from the .ibd files...
2024-10-08 21:02:06 10791 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace www_c0317_com/ims_longbing_card_copy_count uses space ID: 2542 at filepath: ./www_c0317_com/ims_longbing_card_copy_count.ibd. Cannot open tablespace www_c0317/ims_tech_shopm_ptlist which uses space ID: 2542 at filepath: ./www_c0317/ims_tech_shopm_ptlist.ibd
2024-10-08 21:02:06 7f755f774880  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./www_c0317/ims_tech_shopm_ptlist.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
--
2024-10-08 21:02:08 11793 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-10-08 21:02:08 11793 [Note] InnoDB: Using Linux native AIO
2024-10-08 21:02:08 11793 [Note] InnoDB: Using CPU crc32 instructions
2024-10-08 21:02:08 11793 [Note] InnoDB: Initializing buffer pool, size = 384.0M
2024-10-08 21:02:08 11793 [Note] InnoDB: Completed initialization of buffer pool
2024-10-08 21:02:08 11793 [Note] InnoDB: Highest supported file format is Barracuda.
2024-10-08 21:02:08 11793 [Note] InnoDB: Log scan progressed past the checkpoint lsn 67527865373
2024-10-08 21:02:08 11793 [Note] InnoDB: Database was not shutdown normally!
2024-10-08 21:02:08 11793 [Note] InnoDB: Starting crash recovery.
2024-10-08 21:02:08 11793 [Note] InnoDB: Reading tablespace information from the .ibd files...
2024-10-08 21:02:09 11793 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace www_c0317_com/ims_longbing_card_copy_count uses space ID: 2542 at filepath: ./www_c0317_com/ims_longbing_card_copy_count.ibd. Cannot open tablespace www_c0317/ims_tech_shopm_ptlist which uses space ID: 2542 at filepath: ./www_c0317/ims_tech_shopm_ptlist.ibd
2024-10-08 21:02:09 7f7ebf442880  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./www_c0317/ims_tech_shopm_ptlist.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
--
2024-10-08 21:02:11 12787 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-10-08 21:02:11 12787 [Note] InnoDB: Using Linux native AIO
2024-10-08 21:02:11 12787 [Note] InnoDB: Using CPU crc32 instructions
2024-10-08 21:02:11 12787 [Note] InnoDB: Initializing buffer pool, size = 384.0M
2024-10-08 21:02:11 12787 [Note] InnoDB: Completed initialization of buffer pool
2024-10-08 21:02:11 12787 [Note] InnoDB: Highest supported file format is Barracuda.
2024-10-08 21:02:11 12787 [Note] InnoDB: Log scan progressed past the checkpoint lsn 67527865373
2024-10-08 21:02:11 12787 [Note] InnoDB: Database was not shutdown normally!
2024-10-08 21:02:11 12787 [Note] InnoDB: Starting crash recovery.
2024-10-08 21:02:11 12787 [Note] InnoDB: Reading tablespace information from the .ibd files...
2024-10-08 21:02:11 12787 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace www_c0317_com/ims_longbing_card_copy_count uses space ID: 2542 at filepath: ./www_c0317_com/ims_longbing_card_copy_count.ibd. Cannot open tablespace www_c0317/ims_tech_shopm_ptlist which uses space ID: 2542 at filepath: ./www_c0317/ims_tech_shopm_ptlist.ibd
2024-10-08 21:02:11 7f2016e7b880  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./www_c0317/ims_tech_shopm_ptlist.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
[root@izm5eb8f6yfdzquzas6bzez ~]#