Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: 使用dumpling时报create dumper failed: sql: SELECT version();: tls: server selected unsupported protocol version 302
【TiDB Usage Environment】Testing/PoC
【TiDB Version】
【Reproduction Path】tiup dumpling -h 172.18.30.36 -P 3308 -u root -p *** -F 256MiB -B db -T ‘db.t1,db.t2’ -o /root/20240429/ --filetype csv
【Encountered Issue: Phenomenon and Impact】Starting component dumpling: /root/.tiup/components/dumpling/v8.0.0/dumpling -h 172.18.30.36 -P 3308 -u root -p *** -F 256MiB -B db -T db.t1,db.t2 -o /root/20240429/ --filetype csv
Release version: v8.0.0
Git commit hash: 8ba1fa452b1ccdbfb85879ea94b9254aabba2916
Git branch: HEAD
Build timestamp: 2024-03-28 02:22:15Z
Go version: go version go1.21.4 linux/amd64
[2024/04/29 15:07:25.374 +08:00] [INFO] [versions.go:54] [“Welcome to dumpling”] [“Release Version”=v8.0.0] [“Git Commit Hash”=8ba1fa452b1ccdbfb85879ea94b9254aabba2916] [“Git Branch”=HEAD] [“Build timestamp”=“2024-03-28 02:22:15”] [“Go Version”=“go version go1.21.4 linux/amd64”]
[2024/04/29 15:07:25.397 +08:00] [WARN] [version.go:333] [“select tidb_version() failed, will fallback to ‘select version();’”] [error=“tls: server selected unsupported protocol version 302”]
create dumper failed: sql: SELECT version();: tls: server selected unsupported protocol version 302
【Resource Configuration】
【Attachments: Screenshots/Logs/Monitoring】
It looks like there is a mismatch in the TLS versions between the client and server.
openssl ciphers -v | awk ‘{print $2}’ | sort | uniq
[root@EagleOS bin]# openssl ciphers -v | awk ‘{print $2}’ | sort | uniq
SSLv3
TLSv1
TLSv1.2
TLSv1.3
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1351737
Server version: 5.7.20-19-log Source distribution
Copyright (c) 2009-2017 Percona LLC and/or its affiliates
Copyright (c) 2000, 2017, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.
root@localhost:(none) 03:49:07> status
mysql Ver 14.14 Distrib 5.7.20-19, for Linux (x86_64) using 6.0
Connection id: 1351737
Current database:
Current user: root@localhost
SSL: Not in use
Current pager: stdout
Using outfile: ‘’
Using delimiter: ;
Server version: 5.7.20-19-log Source distribution
Protocol version: 10
Connection: Localhost via UNIX socket
Server characterset: utf8mb4
Db characterset: utf8mb4
Client characterset: utf8
Conn. characterset: utf8
UNIX socket: /data/mysql_data/mysql-3308/data/mysqld.sock
Uptime: 84 days 7 hours 10 min 23 sec
Threads: 89 Questions: 198242310 Slow queries: 71083 Opens: 1129360 Flush tables: 1 Open tables: 8192 Queries per second avg: 27.218
Is it possible that the TiDB and Dumping versions are incompatible?
Are you referring to the inconsistency between the TiDB client and server versions, or the inconsistency with the MySQL side?
How can I disable TLS in dumpling?
Is it possible that you have configured TLS in the client settings on your server?
After looking at the error, it seems to be a version mismatch.
Where is the default configuration path? I didn’t do any additional configuration after installing TiDB.
Which two versions are mismatched?
Don’t use Dumpling to back up MySQL.
Why? Didn’t the official say that it can be exported to MySQL?
|
username: chenxb
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: