Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: tiup查看dm任务命令报错
【TiDB Environment】Production\Test Environment\POC
【TiDB Version】4.0.11
【Encountered Issue】Failed to start component dmctl
【Reproduction Path】What operations were performed to cause the issue
【Problem Phenomenon and Impact】
tiup dmctl --master-addr X.X.X.X:8261
Failed to start component dmctl
Error: fetch /832.dmctl.json from mirror(https://tiup-mirrors.pingcap.com) failed: url https://tiup-mirrors.pingcap.com/832.dmctl.json: not found
Executing the tiup cluster command works fine
tiup dm display xxxx
dmctl --master-addr X.X.X.X:8261
Two different commands
Such basic issues have definitely been ruled out. I’m also experiencing problems here. The entire cluster, including production, pre-production, testing, and both domestic and overseas environments, is all abnormal.
In my environment, after downloading the offline package, I set the local mirror using tiup mirror set, so there’s no need to access the public network to find PingCAP.
I tried it in the test environment, and it seems like there is an issue with the remote mirror source. Using the local mirror source works fine. You can download an offline package, upload it, and extract it. Then use tiup mirror set xxx to point to the extracted directory and try again.
Encountered resource issues while creating the offline package as well. 
Just download it directly from here: 分布式数据库 TiDB 社区版 | PingCAP
Thank you. We’ll handle the higher versions first. As for the few clusters that are still on version 2.0.x, we’ll wait for the official update.
Version 5.4 also reported an error… This is really frustrating. Why does it still rely on external resources?
There are some issues with tiup, and the engineers are already handling it.
There were network fluctuations from the mirror server to the vendor CDN, causing the component release to fail. The issue has been resolved, and the mirror has been restored. Please clean up and try again.
The issue with the mirror source has been fixed~
tiup mirror set --reset
Use an offline mirror. tiup mirror set
How to handle this error, tidb: 4.0.8, tiup: v1.2.5, dm: 2.0.1
Still getting this error:
Failed to start component dmctl
Error: timestamp manifest has a version number < the old manifest (34458, 34483)
Then after deleting manifests/*, it reports:
Failed to start component dmctl
Error: read manifest from mirror(https://tiup-mirrors.pingcap.com) failed: manifest timestamp.json has expired at: 2021-05-26T11:18:30+08:00
There is no reset command
~/tidb/dm/conf $ tiup mirror set --reset
Error: unknown flag: --reset
tiup mirror clone tidb-dm-v2.0.6-linux-amd64 --os=linux --arch=amd64 --dm-master=v2.0.6 --dm-worker=v2.0.6 --dmctl=v2.0.6
Error: read manifest from mirror(https://tiup-mirrors.pingcap.com) failed: manifest timestamp.json has expired at: 2021-05-26T11:18:30+08:00
This topic was automatically closed 1 minute after the last reply. No new replies are allowed.
|
username: wakaka
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: