Upgrade Failed: 5.4 to 6.2

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 升级失败 5.4 升级 6.2

| username: 谢斌1204

update connection contexts failed
Failed to start TiDB component

[2022/09/02 10:19:10.706 +08:00] [ERROR] [client.go:910] [“[pd] update connection contexts failed”] [dc=global] [error=“rpc error: code = Canceled desc = context canceled”]
[2022/09/02 10:19:10.706 +08:00] [INFO] [client.go:709] [“[pd] exit tso dispatcher”] [dc-location=global]
[2022/09/02 10:19:10.711 +08:00] [FATAL] [terror.go:298] [“unexpected error”] [error=“no pump found in pd”] [stack=“github.com/pingcap/tidb/parser/terror.MustNil
\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/parser/terror/terror.go:298
main.setupBinlogClient
\t/home/jenkins/agent/wo
rkspace/build-common/go/src/github.com/pingcap/tidb/tidb-server/main.go:337
main.main
\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/tidb-server/main.go:203
runtime.main
\t/usr/local/go/src/runtime/proc.go:250”] [stack=“github.com/pingcap/tidb/parser/terror.MustNil
\t/home/jenkins/
agent/workspace/build-common/go/src/github.com/pingcap/tidb/parser/terror/terror.go:298
main.setupBinlogClient
\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/tidb-server/main.go:337
main.main
\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/tidb-server/mai
n.go:203
runtime.main
\t/usr/local/go/src/runtime/proc.go:250”]
~
2022-09-02T10:17:05.971+0800 INFO Execute command finished {“code”: 1, “error”: “failed to start tidb: failed to start: 10.96.129.225 tidb-4000.service, please check the instance’s log(/data/tidb/tidb-deploy/tidb-4000/log) for more detail.: timed out waiting for port 4000 to be started after 2m0s”, "er

2022-09-02T10:36:29.801+0800 INFO CheckPoint {“host”: “10.96.129.223”, “port”: 22, “user”: “tidb”, “sudo”: false, “cmd”: “ss -ltn”, “stdout”: "State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 :111 :

LISTEN 0 128 :22 :
LISTEN 0 100 127.0.0.1:25 :
LISTEN 0 32768 [::]:2379 [::]:
LISTEN 0 32768 [::]:2380 [::]:

LISTEN 0 128 [::]:111 [::]:*
LISTEN 0 128 [::]:22 [::]:*
LISTEN 0 100 [::1]:25 [::]:*
", “stderr”: “”, “hash”: “e198ac54996fa5a29f1961a
460d6634ee9e75d26”, “func”: “github.com/pingcap/tiup/pkg/cluster/executor.(*CheckPointExecutor).Execute”, “hit”: false}

[TiDB Usage Environment] Testing, Research
[TiDB Version] 5.4 upgrade to 6.2
[Encountered Problem]

2
| username: xfworld | Original post link

Has the cluster installed the binlog component? Not TiCDC…

3
| username: 谢斌1204 | Original post link

I don’t quite remember, but it seems like there was. It has been deleted.

4
| username: xfworld | Original post link

Starting from version 5.X, binlog is supported. If you want to update to 6.2, you need to clean it up thoroughly…

5
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.