【数据库-MySql】MySql连接错误1042:Can't get hostname for your address:

博客介绍了MySQL的配置操作,首先要在[mysqld]下进行添加,之后需重启MySQL服务,为MySQL的相关配置提供了简单步骤。

1、在[mysqld]下添加

skip-name-resolve

2、重启MySQL服务

version: '3.7' services: server1: image: base-server container_name: server1 command: ["sh", "-c", "/scripts/start_services.sh"] environment: - VT_HOSTNAME=server1 - VT_TOPOLOGY=etcd:http://server1:2379 ports: - "15000:15000" - "15306:3306" networks: vitess-network: ipv4_address: 172.16.0.101 volumes: - ./scripts:/scripts - etcd-data:/var/lib/etcd # 修改挂载路径 server2: image: mysql-server container_name: server2 command: ["sh", "-c", "while ! nc -z server1 2379; do sleep 1; done; /scripts/init_master.sh"] environment: - VT_HOSTNAME=server2 - VT_TOPOLOGY=etcd:http://server1:2379 - VTDATAROOT=/vt/vtdataroot # 显式指定数据目录 networks: vitess-network: ipv4_address: 172.16.0.102 volumes: - ./scripts:/scripts - mysql-master:/vt/vtdataroot depends_on: - server1 server3: image: mysql-server container_name: server3 command: ["sh", "-c", "while ! nc -z server1 2379; do sleep 1; done; /scripts/init_replica.sh"] environment: - VT_HOSTNAME=server3 - VT_TOPOLOGY=etcd:http://server1:2379 - VTDATAROOT=/vt/vtdataroot networks: vitess-network: ipv4_address: 172.16.0.103 volumes: - ./scripts:/scripts - mysql-replica:/vt/vtdataroot depends_on: - server1 volumes: etcd-data: mysql-master: mysql-replica: networks: vitess-network: driver: bridge ipam: config: - subnet: 172.16.0.0/24 Dockerfile.base: FROM vitess/base USER root RUN chmod 777 /var/lib/etcd USER vitess Dockerfile.server: FROM vitess/base USER root RUN apt-get update && apt-get install -y netcat || yum install -y nc || apk add --no-cache gnu-netcat # 安装 etcdctl 和网络检测工具 RUN apt-get update && \ apt-get install -y curl && \ rm -rf /var/lib/apt/lists/* USER vitess start_services.sh: #!/bin/bash RUN apt-get update && apt-get install -y netcat || yum install -y nc || apk add --no-cache gnu-netcat # 启动 etcd、vtctld、vtgate etcd --data-dir /etcd & sleep 5 vtctld --topo_implementation etcd2 --topo_global_server_address http://localhost:2379 & vtgate --topo_implementation etcd2 --topo_global_server_address http://localhost:2379 --mysql_server_port 3306 & init_master.sh 和 init_replica.sh : #!/bin/bash # 启动 MySQL 从实例和 vttablet vttablet \ --topo_implementation etcd2 \ --topo_global_server_address server1:2379 \ --tablet-path "zone1-101" \ --init_keyspace "test_keyspace" \ --init_shard "0" \ --init_tablet_type "replica" \ --port 15002 \ --grpc_port 16002 \ --db_port 3306 2025-05-21 15:41:10.240 | /scripts/start_services.sh: line 3: RUN: command not found 2025-05-21 15:41:10.244 | /scripts/start_services.sh: line 3: yum: command not found 2025-05-21 15:41:10.248 | /scripts/start_services.sh: line 3: apk: command not found 2025-05-21 15:41:11.117 | {"level":"info","ts":"2025-05-21T07:41:11.109Z","caller":"etcdmain/etcd.go:73","msg":"Running: ","args":["etcd","--data-dir","/etcd"]} 2025-05-21 15:41:11.119 | {"level":"info","ts":"2025-05-21T07:41:11.117Z","caller":"embed/etcd.go:124","msg":"configuring peer listeners","listen-peer-urls":["http://localhost:2380"]} 2025-05-21 15:41:11.124 | {"level":"info","ts":"2025-05-21T07:41:11.124Z","caller":"embed/etcd.go:132","msg":"configuring client listeners","listen-client-urls":["http://localhost:2379"]} 2025-05-21 15:41:11.125 | {"level":"info","ts":"2025-05-21T07:41:11.125Z","caller":"embed/etcd.go:306","msg":"starting an etcd server","etcd-version":"3.5.6","git-sha":"cecbe35ce","go-version":"go1.16.15","go-os":"linux","go-arch":"amd64","max-cpu-set":12,"max-cpu-available":12,"member-initialized":false,"name":"default","data-dir":"/etcd","wal-dir":"","wal-dir-dedicated":"","member-dir":"/etcd/member","force-new-cluster":false,"heartbeat-interval":"100ms","election-timeout":"1s","initial-election-tick-advance":true,"snapshot-count":100000,"max-wals":5,"max-snapshots":5,"snapshot-catchup-entries":5000,"initial-advertise-peer-urls":["http://localhost:2380"],"listen-peer-urls":["http://localhost:2380"],"advertise-client-urls":["http://localhost:2379"],"listen-client-urls":["http://localhost:2379"],"listen-metrics-urls":[],"cors":["*"],"host-whitelist":["*"],"initial-cluster":"default=http://localhost:2380","initial-cluster-state":"new","initial-cluster-token":"etcd-cluster","quota-backend-bytes":2147483648,"max-request-bytes":1572864,"max-concurrent-streams":4294967295,"pre-vote":true,"initial-corrupt-check":false,"corrupt-check-time-interval":"0s","compact-check-time-enabled":false,"compact-check-time-interval":"1m0s","auto-compaction-mode":"periodic","auto-compaction-retention":"0s","auto-compaction-interval":"0s","discovery-url":"","discovery-proxy":"","downgrade-check-interval":"5s"} 2025-05-21 15:41:11.125 | {"level":"info","ts":"2025-05-21T07:41:11.125Z","caller":"embed/etcd.go:373","msg":"closing etcd server","name":"default","data-dir":"/etcd","advertise-peer-urls":["http://localhost:2380"],"advertise-client-urls":["http://localhost:2379"]} 2025-05-21 15:41:11.125 | {"level":"info","ts":"2025-05-21T07:41:11.125Z","caller":"embed/etcd.go:375","msg":"closed etcd server","name":"default","data-dir":"/etcd","advertise-peer-urls":["http://localhost:2380"],"advertise-client-urls":["http://localhost:2379"]} 2025-05-21 15:41:11.125 | {"level":"warn","ts":"2025-05-21T07:41:11.125Z","caller":"etcdmain/etcd.go:146","msg":"failed to start etcd","error":"cannot access data directory: mkdir /etcd: permission denied"} 2025-05-21 15:41:11.126 | {"level":"fatal","ts":"2025-05-21T07:41:11.125Z","caller":"etcdmain/etcd.go:204","msg":"discovery failed","error":"cannot access data directory: mkdir /etcd: permission denied","stacktrace":"go.etcd.io/etcd/server/v3/etcdmain.startEtcdOrProxyV2\n\tgo.etcd.io/etcd/server/v3/etcdmain/etcd.go:204\ngo.etcd.io/etcd/server/v3/etcdmain.Main\n\tgo.etcd.io/etcd/server/v3/etcdmain/main.go:40\nmain.main\n\tgo.etcd.io/etcd/server/v3/main.go:32\nruntime.main\n\truntime/proc.go:225"} nc: getaddrinfo for host "server1" port 2379: No address associated with hostname nc: getaddrinfo for host "server1" port 2379: No address associated with hostname nc: getaddrinfo for host "server1" port 2379: No address associated with hostname nc: getaddrinfo for host "server1" port 2379: No address associated with hostname nc: getaddrinfo for host "server1" port 2379: No address associated with hostname 启动失败
05-22
2025-10-24T06:14:45.483589Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2025-10-24T06:14:45.487190Z 0 [Note] C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe (mysqld 5.7.43-log) starting as process 2792 ... 2025-10-24T06:14:45.499521Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2025-10-24T06:14:45.500924Z 0 [Note] InnoDB: Uses event mutexes 2025-10-24T06:14:45.501775Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier 2025-10-24T06:14:45.503093Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 2025-10-24T06:14:45.509869Z 0 [Note] InnoDB: Number of pools: 1 2025-10-24T06:14:45.510876Z 0 [Note] InnoDB: Not using CPU crc32 instructions 2025-10-24T06:14:45.516358Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M 2025-10-24T06:14:45.739511Z 0 [Note] InnoDB: Completed initialization of buffer pool 2025-10-24T06:14:45.866688Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 2025-10-24T06:14:45.917325Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1818072334033 2025-10-24T06:14:45.919665Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1818072343203 2025-10-24T06:14:46.501026Z 0 [Note] InnoDB: Database was not shutdown normally! 2025-10-24T06:14:46.502853Z 0 [Note] InnoDB: Starting crash recovery. 2025-10-24T06:14:53.325953Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2025-10-24T06:14:53.328050Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2025-10-24T06:14:53.331419Z 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2025-10-24T06:14:53.341449Z 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB. 2025-10-24T06:14:53.377635Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. 2025-10-24T06:14:53.379973Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active. 2025-10-24T06:14:53.382232Z 0 [Note] InnoDB: Waiting for purge to start 2025-10-24T06:14:53.434201Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 7651ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.) 2025-10-24T06:14:53.434424Z 0 [Note] InnoDB: 5.7.43 started; log sequence number 1818072343203 2025-10-24T06:14:53.440369Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=3] log sequence number 1818075015616 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.440496Z 0 [Note] InnoDB: Loading buffer pool(s) from D:\MySql\data\ib_buffer_pool 2025-10-24T06:14:53.444882Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.454213Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=2] log sequence number 1818075015133 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.457121Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.459265Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=13] log sequence number 1818075023156 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.459333Z 0 [Note] Plugin 'FEDERATED' is disabled. 2025-10-24T06:14:53.461391Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=4] log sequence number 1818074852082 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.464302Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.468966Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=8883] log sequence number 1818075644951 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.469327Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.478059Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.481293Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=5] log sequence number 1818074822726 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.488992Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.493841Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=8] log sequence number 1818073611600 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.496594Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.499300Z 0 [ERROR] InnoDB: Page [page id: space=488, page number=3] log sequence number 1818075769646 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.500195Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=22] log sequence number 1818074006086 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.503793Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.505862Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.513791Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=23] log sequence number 1818074993296 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.515785Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.524243Z 0 [ERROR] InnoDB: Page [page id: space=488, page number=527] log sequence number 1818080514186 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.528019Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.537996Z 0 [ERROR] InnoDB: Page [page id: space=540, page number=7] log sequence number 1818081166468 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.541042Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.543656Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=31] log sequence number 1818075024348 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.548712Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.554624Z 0 [ERROR] InnoDB: Page [page id: space=540, page number=4] log sequence number 1818081150547 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.558427Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.565031Z 0 [ERROR] InnoDB: Page [page id: space=539, page number=4] log sequence number 1818080173025 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.567157Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=31683] log sequence number 1818075654250 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.567489Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.571042Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.598497Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them. 2025-10-24T06:14:53.601463Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory. 2025-10-24T06:14:53.603981Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher. 2025-10-24T06:14:53.605450Z 0 [ERROR] InnoDB: Page [page id: space=743, page number=0] log sequence number 1818074641633 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.606048Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher. 2025-10-24T06:14:53.609638Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. InnoDB: Dump of the tablespace extent descriptor: len 40; hex 0000000000000000ffffffff0000ffffffff000000000002aaffffffffffffffffffffffffffffff; asc ;2025-10-24T06:14:53.618233Z 0 [ERROR] InnoDB: InnoDB is trying to free page [page id: space=743, page number=8] though it is already marked as free in the tablespace! The tablespace free space info is corrupt. You may need to dump your tables and recreate the whole database! 2025-10-24T06:14:53.622034Z 0 [ERROR] [FATAL] InnoDB: Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.624235Z 0 [Warning] CA certificate ca.pem is self signed. 2025-10-24 14:14:53 0x354c InnoDB: Assertion failure in thread 13644 in file ut0ut.cc line 921 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/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 2025-10-24T06:14:53.625645Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory. 2025-10-24T06:14:53.628676Z 0 [Note] Server hostname (bind-address): '*'; port: 3308 2025-10-24T06:14:53.629979Z 0 [Note] IPv6 is available. 2025-10-24T06:14:53.630668Z 0 [Note] - '::' resolves to '::'; 2025-10-24T06:14:53.632389Z 0 [Note] Server socket created on IP: '::'. 2025-10-24T06:14:53.747077Z 0 [ERROR] InnoDB: Page [page id: space=26, page number=16384] log sequence number 1818075741603 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:53.751073Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:53.924848Z 0 [Note] Failed to start slave threads for channel '' 2025-10-24T06:14:54.002381Z 0 [Note] Event Scheduler: Loaded 0 events 2025-10-24T06:14:54.003266Z 0 [Note] C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe: ready for connections. Version: '5.7.43-log' socket: '' port: 3308 MySQL Community Server (GPL) 2025-10-24T06:14:54.063857Z 0 [ERROR] InnoDB: Page [page id: space=28, page number=0] log sequence number 1818073721575 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:54.067646Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:54.073181Z 0 [ERROR] InnoDB: Page [page id: space=28, page number=4] log sequence number 1818073721575 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:54.076879Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:54.081031Z 0 [ERROR] InnoDB: Page [page id: space=28, page number=5] log sequence number 1818073639109 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:54.083439Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:54.087366Z 0 [ERROR] InnoDB: Page [page id: space=488, page number=0] log sequence number 1818074963526 is in the future! Current system log sequence number 1818072347793. 2025-10-24T06:14:54.089008Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-10-24T06:14:54.840960Z 0 [Note] InnoDB: Buffer pool(s) load completed at 251024 14:14:54
10-25
2025-12-19T05:34:37.849417Z 0 [Warning] '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. 2025-12-19T05:34:37.849496Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled 2025-12-19T05:34:37.849866Z 0 [Note] C:\BtSoft\mysql\MySQL5.7\bin\mysqld.exe (mysqld 5.7.38-log) starting as process 8348 ... 2025-12-19T05:34:37.868526Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2025-12-19T05:34:37.869014Z 0 [Note] InnoDB: Uses event mutexes 2025-12-19T05:34:37.869267Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier 2025-12-19T05:34:37.869618Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2025-12-19T05:34:37.870357Z 0 [Note] InnoDB: Number of pools: 1 2025-12-19T05:34:37.870807Z 0 [Note] InnoDB: Not using CPU crc32 instructions 2025-12-19T05:34:37.873342Z 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2025-12-19T05:34:37.890813Z 0 [Note] InnoDB: Completed initialization of buffer pool 2025-12-19T05:34:37.928888Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 2025-12-19T05:34:37.935781Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 47795629696 2025-12-19T05:34:37.936452Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 47795678803 2025-12-19T05:34:37.956276Z 0 [Note] InnoDB: Database was not shutdown normally! 2025-12-19T05:34:37.956614Z 0 [Note] InnoDB: Starting crash recovery. 2025-12-19T05:34:38.334975Z 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo 2025-12-19T05:34:38.335541Z 0 [Note] InnoDB: Trx id counter is 101645056 2025-12-19T05:34:38.336142Z 0 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2025-12-19T05:34:38.853689Z 0 [Note] InnoDB: Apply batch completed 2025-12-19T05:34:38.854109Z 0 [Note] InnoDB: Last MySQL binlog file position 0 55386, file name mysql-bin.000051 2025-12-19T05:34:38.961866Z 0 [Note] InnoDB: Cleaning up trx with id 101609997 2025-12-19T05:34:39.294080Z 0 [ERROR] InnoDB: In file '.\20251107_092631\auth.ibd', tablespace id and flags are 828 and 33, but in the InnoDB data dictionary they are 122 and 33. Have you moved InnoDB .ibd files around without using the commands DISCARD TABLESPACE and IMPORT TABLESPACE? Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 2025-12-19T05:34:39.295376Z 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2025-12-19T05:34:39.295740Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html 2025-12-19T05:34:39.296279Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `20251107_092631/auth`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 2025-12-19T05:34:39.296984Z 0 [Warning] InnoDB: Ignoring tablespace `20251107_092631/auth` because it could not be opened. 2025-12-19T05:34:39.379037Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2025-12-19T05:34:39.379567Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2025-12-19T05:34:39.380394Z 0 [Note] InnoDB: Setting file 'D:\MySQL\Data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2025-12-19T05:34:39.435030Z 0 [Note] InnoDB: File 'D:\MySQL\Data\ibtmp1' size is now 12 MB. 2025-12-19T05:34:39.455825Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. 2025-12-19T05:34:39.456485Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active. 2025-12-19T05:34:39.457305Z 0 [Note] InnoDB: Waiting for purge to start 2025-12-19T05:34:39.509818Z 0 [Note] InnoDB: 5.7.38 started; log sequence number 47795678803 2025-12-19T05:34:39.510836Z 0 [Note] Plugin 'FEDERATED' is disabled. 2025-12-19T05:34:39.514400Z 0 [Note] InnoDB: Loading buffer pool(s) from D:\MySQL\Data\ib_buffer_pool 2025-12-19T05:34:39.522762Z 0 [Note] Recovering after a crash using mysql-bin 2025-12-19T05:34:39.523590Z 0 [Note] Starting crash recovery... 2025-12-19T05:34:39.523929Z 0 [Note] Crash recovery finished. 2025-12-19T05:34:39.569369Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them. 2025-12-19T05:34:39.569953Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory. 2025-12-19T05:34:39.570390Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher. 2025-12-19T05:34:39.570890Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher. 2025-12-19T05:34:39.572758Z 0 [Warning] CA certificate ca.pem is self signed. 2025-12-19T05:34:39.573483Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory. 2025-12-19T05:34:39.574195Z 0 [Note] Server hostname (bind-address): '*'; port: 3306 2025-12-19T05:34:39.574741Z 0 [Note] IPv6 is available. 2025-12-19T05:34:39.575017Z 0 [Note] - '::' resolves to '::'; 2025-12-19T05:34:39.575349Z 0 [Note] Server socket created on IP: '::'. 2025-12-19T05:34:39.604561Z 0 [Note] Failed to start slave threads for channel '' 2025-12-19T05:34:39.619077Z 0 [ERROR] InnoDB: Page [page id: space=572, page number=3] log sequence number 47818895373 is in the future! Current system log sequence number 47795679298. 2025-12-19T05:34:39.619873Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery. 2025-12-19T05:34:39.633764Z 0 [Note] Event Scheduler: Loaded 0 events 2025-12-19T05:34:39.634297Z 0 [Note] C:\BtSoft\mysql\MySQL5.7\bin\mysqld.exe: ready for connections. Version: '5.7.38-log' socket: '' port: 3306 MySQL Community Server (GPL) 2025-12-19 13:34:42 0x5d18 InnoDB: Assertion failure in thread 23832 in file fsp0fsp.cc line 3880 InnoDB: Failing assertion: xdes_mtr_get_bit(descr, XDES_FREE_BIT, header_page % FSP_EXTENT_SIZE, mtr) == FALSE 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/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 05:34:42 UTC - mysqld got exception 0x80000003 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=4 max_threads=300 thread_count=4 connection_count=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 403530 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x23a27e14790 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... 7ff63abcb302 mysqld.exe!my_errno() 7ffc6838ee1d MSVCR120.dll!raise() 7ffc68394a14 MSVCR120.dll!abort() 7ff63ace7434 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ff63acfab30 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ff63ac64cdf mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ff63ac673e6 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ff63ac66f29 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ff63ac63e9a mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ff63ac2a36e mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ff63ac2e5ac mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ffc7f294cb0 KERNEL32.DLL!BaseThreadInitThunk() 7ffc8077edcb ntdll.dll!RtlUserThreadStart() Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0): Connection ID (thread ID): 0 Status: NOT_KILLED 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. 2025-12-19T05:34:42.715725Z 0 [Note] InnoDB: Buffer pool(s) load completed at 251219 13:34:42
最新发布
12-20
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值