高地网 - 我们的技术专家

 找回密码
 注册

QQ登录

只需一步,快速开始

搜索
查看: 502|回复: 3

mysql错误

[复制链接]
hotfox 发表于 2022-4-6 21:45:43 | 显示全部楼层 |阅读模式

马上注册,结交更多好友,享用更多功能,让你轻松玩转社区。

您需要 登录 才可以下载或查看,没有账号?注册

×
2022-04-06T13:42:50.830558Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2022-04-06T13:42:50.833047Z 0 [System] [MY-010116] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.28) starting as process 3984
2022-04-06T13:42:50.848341Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-04-06T13:42:53.586336Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-04-06T13:42:54.616563Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2022-04-06T13:42:54.626319Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2022-04-06T13:42:55.120476Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2022-04-06T13:42:55.120718Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2022-04-06T13:42:55.183543Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060
2022-04-06T13:42:55.183772Z 0 [System] [MY-010931] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe: ready for connections. Version: '8.0.28'  socket: ''  port: 3306  MySQL Community Server - GPL.
2022-04-06T13:43:12.642143Z 22 [Warning] [MY-010056] [Server] Host name 'ecs-121-36-226-95.compute.hwclouds-dns.com' could not be resolved: 不知道这样的主机。
2022-04-06T13:43:21.471224Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-04-06T13:43:21.471576Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
2022-04-06T13:43:21.581172Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 264
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
13:43:21 UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
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...
2022-04-06T13:43:21.581769Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-04-06T13:43:21.582029Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
7ff79652fd48    mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff79576004b    mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff79575fe13    mysqld.exe!?my_server_abort@@YAXXZ()
7ff79651643a    mysqld.exe!?my_abort@@YAXXZ()
7ff79674c579    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff79669bd51    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff79669d5da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff79669c7da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7966be3f4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff79670e091    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff79670b7b4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ffbd887f4a0    ucrtbase.DLL!_o__realloc_base()
7ffbe11f13f2    KERNEL32.DLL!BaseThreadInitThunk()
7ffbe1805504    ntdll.dll!RtlUserThreadStart()
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.
2022-04-06T13:43:21.690531Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 3916
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
2022-04-06T13:43:21.690395Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-04-06T13:43:21.740014Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
2022-04-06T13:43:21.847015Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 2920
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
2022-04-06T13:43:21.847363Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-04-06T13:43:21.847614Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
2022-04-06T13:43:21.956273Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 992
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
论坛发展靠大家,积极提供资源;请勿灌水
 楼主| hotfox 发表于 2022-4-6 21:48:44 | 显示全部楼层
ERROR 995: InnoDB: Operating system error number 995 in a file operation
Discussion
Windows Error number 995 (ERROR_OPERATION_ABORTED) indicates that an asynchronous I/O operation was cancelled.

Solution
There can be several causes for this, in most likely to least likely order:

Excessive RAM Allocation
One cause could be too much RAM allocated, so that threads are being terminated and abandoning their I/O operations. To confirm this, radically reduce RAM allocations and see whether the problem is resolved.

SAN Command Queue too Small
Another possible cause is the SAN storage system with a command queue that is too small to hold all of the requests generated by the load, causing it to discard some requests.

Killed thread
The final common cause may simply be a killed thread. Check the server's logs to confirm this and to determine the source of this action.
论坛发展靠大家,积极提供资源;请勿灌水
回复 支持 反对

使用道具 举报

 楼主| hotfox 发表于 2022-4-7 15:14:03 | 显示全部楼层
SYMPTOMS
Lots of errors like these in the error log:

InnoDB: Operating system error number 995 in a file operation.
InnoDB: The error means that the I/O operation has been aborted
InnoDB: because of either a thread exit or an application request.
InnoDB: Retry attempt is made.

There may also be other errors, like these:

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/ ... em-error-codes.html

InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file 'x.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/ ... oting-datadict.html
InnoDB: for how to resolve the issue.
论坛发展靠大家,积极提供资源;请勿灌水
回复 支持 反对

使用道具 举报

 楼主| hotfox 发表于 2022-4-16 23:58:02 | 显示全部楼层
2022-04-09T02:46:57.351614Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2022-04-09T02:46:57.353556Z 0 [System] [MY-010116] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.28) starting as process 1300
2022-04-09T02:46:57.369549Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-04-09T02:46:59.585808Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-04-09T02:47:02.466478Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2022-04-09T02:47:02.467016Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2022-04-09T02:47:02.542319Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060
2022-04-09T02:47:02.542634Z 0 [System] [MY-010931] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe: ready for connections. Version: '8.0.28'  socket: ''  port: 3306  MySQL Community Server - GPL.
2022-04-16T15:55:13.139011Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-04-16T15:55:13.147533Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
2022-04-16T15:55:13.249549Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-04-16T15:55:13.249828Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
2022-04-16T15:55:13.263146Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 2856
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
15:55:13 UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
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...
2022-04-16T15:55:13.358879Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-04-16T15:55:13.359163Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
2022-04-16T15:55:13.359482Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 2968
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
2022-04-16T15:55:13.468215Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-04-16T15:55:13.468420Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 308
2022-04-16T15:55:13.468694Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
2022-04-16T15:55:13.577637Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 3736
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
7ff7a94dfd48    mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff7a871004b    mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff7a870fe13    mysqld.exe!?my_server_abort@@YAXXZ()
7ff7a94c643a    mysqld.exe!?my_abort@@YAXXZ()
7ff7a96fc579    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff7a964bd51    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7a964d5da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7a964c7da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7a966e3f4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff7a96be091    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff7a96bb7b4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ffcb7caf4a0    ucrtbase.DLL!_o__realloc_base()
7ffcc04c13f2    KERNEL32.DLL!BaseThreadInitThunk()
7ffcc0885504    ntdll.dll!RtlUserThreadStart()
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.
15:55:14 UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
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...
7ff7a94dfd48    mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff7a871004b    mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff7a870fe13    mysqld.exe!?my_server_abort@@YAXXZ()
7ff7a94c643a    mysqld.exe!?my_abort@@YAXXZ()
7ff7a96fc579    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff7a964bd51    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7a964d5da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7a964c7da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7a966e3f4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff7a96be091    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff7a96bb7b4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ffcb7caf4a0    ucrtbase.DLL!_o__realloc_base()
7ffcc04c13f2    KERNEL32.DLL!BaseThreadInitThunk()
7ffcc0885504    ntdll.dll!RtlUserThreadStart()
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.
15:55:14 UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
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...
7ff7a94dfd48    mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff7a871004b    mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff7a870fe13    mysqld.exe!?my_server_abort@@YAXXZ()
7ff7a94c643a    mysqld.exe!?my_abort@@YAXXZ()
7ff7a96fc579    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff7a964bd51    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7a964d5da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7a964c7da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7a966e3f4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff7a96be091    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff7a96bb7b4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ffcb7caf4a0    ucrtbase.DLL!_o__realloc_base()
7ffcc04c13f2    KERNEL32.DLL!BaseThreadInitThunk()
7ffcc0885504    ntdll.dll!RtlUserThreadStart()
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.
15:55:14 UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
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...
7ff7a94dfd48    mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff7a871004b    mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff7a870fe13    mysqld.exe!?my_server_abort@@YAXXZ()
7ff7a94c643a    mysqld.exe!?my_abort@@YAXXZ()
7ff7a96fc579    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff7a964bd51    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7a964d5da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7a964c7da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7a966e3f4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff7a96be091    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff7a96bb7b4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ffcb7caf4a0    ucrtbase.DLL!_o__realloc_base()
7ffcc04c13f2    KERNEL32.DLL!BaseThreadInitThunk()
7ffcc0885504    ntdll.dll!RtlUserThreadStart()
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.
论坛发展靠大家,积极提供资源;请勿灌水
回复 支持 反对

使用道具 举报

您需要登录后才可以回帖 登录 | 注册

本版积分规则

QQ|手机版|小黑屋|存档|高地网 ( 沪ICP备19008575号 )

GMT+8, 2022-9-26 13:27 , Processed in 0.052471 second(s), 18 queries .

Powered by Discuz! X3.5

Copyright © 2001-2022 Tencent Cloud.

快速回复 返回顶部 返回列表